Tang Console with Mega 138k module

[vanbako]

I have the Tang Console v1.1 with the 138k module and would like to add it to the project.
Can you tell me how to do this?

[vossstef]

I will try over the next days try to add support for Console 138k with integrated onboard BL616 MCU. Is it that what you are looking for? Likely i didn't catched fully your message.

[vanbako]

Yes, that's what I meant. Thanks.
I tried myself but got many errors building the project in gowin designer.

[harbaum]

As already stated per PM, we don't have these devices.

Also, you suggested asking nand2mario do the port. Did you contact him?

I'd really like to avoid doing things twice, and it seems you have now been asking many people to do the port for you.

[vossstef]

@harbaum i will do the port for 138k Pro initially so that we both can test it. As it stands now there is a dedicated variant needed for integrated onboard bl616. i will not attempt any further root cause analysis why the int spi/ext spi autodetect is for AST138k FPGA not working (gave up on that)

[harbaum]

Did you read the hint about this enable pin that was supposed to be related to your problem?

If that won't help then support for the internal bl616 of the console138k would not be possible at all, right?

[vossstef]

@harbaum, Apple2 is working fine both Mega 138K Pro and Console 138k using onboard BL616.

After all it seems that many single issues:

• FPGA-companion timeout for detecting a core was too short for the almost 37 mbyte bitstream in gw5ast138k
• PLL is still a mess. likely it is not the PLL IP block rather than ide sw function to create the code.
• latest 1.9.12 ide likely helped. maybe there had been corrections done. who knows
• i steer the jtag to gpio switchover now under core control
• increased the bitstream flash load rate from 35mhz to 70mhz
• dedicated bl616 variant as auto switch ( ext spi / int bl616) does not work. root cause unknown. Maybe FPGA type specific. As we don't have errata sheet likely we will never find out.

[harbaum]

My Mega138k does not run any of the latest cores in a usable manner. Sometimes the Atari ST seems to work for a few seconds, the NanoMig won't boot at all. I don't know if it's the cores or if I e.g. damaged the board as I bend it quite a lot when plugging the memory module which I only have one which is shared between the primer25k and the mega138k ...

[vossstef]

@harbaum feeling that there are problems with the IDE PLL creation starting from 1.9.11 onwards including the 1.9.12 especially for the AST138k devices.
I got the NanoMig working on a 138k Pro integrated onboard BL616. Some tcl / project attributes i had to adjust to compile it under 1.9.10.03. No way so far in 1.9.11 and 1.9.12... It simply does not work. Will push soon as extra variant

[harbaum]

Yeah ... strange things happen. While the main atari st system sometimes does work, the sd card often completely fails or hdmi would not work. Both could be explained by clock/pll problems. But these are by no means typical problems to see. Especially the sd card is a small isolated component that basically never exposes issues.

[ellisgl]

@vossstef When I try to flash the kick start:
$ openFPGALoader --external-flash -o 0xc00000 ~/Desktop/Kickstart\ v3.1\ r40.063\ ShapeShifter.rom
empty
write to flash
No cable or board specified: using direct ft2232 interface
Jtag frequency : requested 6.00MHz -> real 6.00MHz
Parse file DONE
Jtag frequency : requested 2.50MHz -> real 2.00MHz
after program flash: displayReadReg 00004000
[14] Security Final
[24:23] CPU Bus Width: no BWD pattern is detected
Erase SRAM DONE
Jtag probe limited to %d MHz6000000
Jtag frequency : requested 10.00MHz -> real 6.00MHz
JEDEC ID: 0xef4017
Detected: Winbond W25Q64 128 sectors size: 64Mb
JEDEC ID: 0xef4017
Detected: Winbond W25Q64 128 sectors size: 64Mb
RDSR : 0x00
WIP : 0
WEL : 0
BP : 0
TB : 0
SRWD : 0
flash overflow
Error: write to flash failed
Error: Failed to program FPGA: Error: write to flash failed

Trying anything at 0xC00000 fails. I found a super small 1000 kick start (8K) and same thing.
0x400000 ends up nuking the main ROM.

Info: Cable found: USB Debugger A/0/13153/null (USB location:13153)
Info: Cable found: USB Debugger A/1/13154/null (USB location:13154)
Info: Cost 1.53 second(s)
:
Info: Target Cable: USB Debugger A/0/13153/null@2MHz
Info: Target Device: GW5AST-138C(0x0001081B)
Info: Operation "exFlash Erase,Program,Verify thru GAO-Bridge 5A" for device#1...
Info: Loading GAO-Bridge...
Info: Gao-Bridge User Code is: 0x00000BEC
Info: Status Code is: 0x00026230
Info: Try to program spi flash: 0xEF4017!
Info: Erasing 1130 sectors from address 0x000000 to 0x46a000...
Info: Program and Verify flash successfully.
Info: Finished.
Info: Cost 161.25 second(s)
:

Seeing that it's up to 46A000 on the main rom, Trying 0x4C0000 did nothing, still a blue screen

[harbaum]

What's a shape shifter Rom? Are you sure that's a kickstart ROM? What size is that file? A valid kickstart should be 256k or 512k.

[ellisgl]

Full name: Kickstart v3.1 r40.063 (1993-07)(Commodore)(A500-A600-A2000)[h ShapeShifter].rom
Size: 512K