Kickstart works on Console60K but df0.adf is not read

[vanbako]

Hardware

• Anker 736 Charger (Nano II 100W)
• Benfei USB-C 5-in-1 Multifunctional Hub, 000360grey
• Tang Mega 60K Retro Console
• SanDisk Extreme PRO 32GB microSD 32GB
• Kingston DataTraveler c10 8GB
• USB keyboard
• USB mouse

FPGA-Companion 1.4.7

• flash_console60k.ini
• bl616_fpga_partner_console60k.bin
• fpga_companion_console60k.bin

Bouffalo Lab Flash Cube 1.1.0

1. Press console boot button during usb insert in console MCU USB-C port
2. config file: flash_console60k.ini
3. choose correct COM port
4. press 'Open Uart' button
5. press 'Download' button

NanoMig 0.7

• nanomig_tc60k.fs

Kickstart 1.3 34.5

• Checked my Cloanto 1.3 ROM, checksum is ok
• Renamed the rom to ks_1-3_34-5.bin

Gowin Programmer V1.9.12

• Series: GW5AT
• Device: GW5AT-60B

1. exFlash Bulk Erase Arora V
2. exFlash C Bin Erase,Program Arora V

• X:/ks_1-3_34-5.bin
• start address: 0x0400000

3. exFlash C Bin Erase,Program Arora V

• X:/ks_1-3_34-5.bin
• start address: 0x0440000

4. exFlash Erase,Program thry GAO-Bridge Arora V

• X:/nanomig_tc60k.fs
• start address: 0x0000000

Workbench 1.3 34.20

• FAT32 format of both microSD & USB datatraveler
• df0.adf copied to both

Issue

• I get HDMI output with the kickstart 1.3 image, hand and floppy
• F12 does not bring up OSD
• I tried with microSD in slot on Console mainboard and USB datatraveler on the USB-C Hub, but nothing
• What could be wrong / how can I debug?

[harbaum]

If the F12 key does not open the OSD then nothing else will work as this is nowadays needed to select the floppy disk image. The info about the default df0.adf is outdated.

[darius600]

@harbaum Is it possible to get debug messages from FPGA companion on the console?

I have pretty much the same configuration as mentioned above by @vanbako :
Console 60k (PCB version C), NanoMig v0.7, FPGA-Compagnion 1.4.7, Kickstart 1.3, SD Card in the console

OSD does not come up.
BUT: when I use a SD card previously used in the TN20k it boots the last ADF image I ran on the TN20k!
USB keyboard and controller however do not work.

[harbaum]

Ok ... that's really helpful information as that means that the bl616 is fully working and is able to assist the core in accessing the SD card.

Are the hw buttons wired up? Does the console even have FPGA accessible buttons? Then one of them might open the OSD. Which won't help much without keyboard. I actually just had a similar case and I think I'll try to make the OSD "one button controllable" if no keyboard is detected. That would allow for gaming setups without keyboard.

So it's really only USB that is not working and the bl616 itself does work. Do your USB devices actually get power from the console?

I never debugged the bl616 on the console. @vossstef may be able to help here.

[vossstef]

@darius600 can't recall anymore did i wired up bl616 console to pins. Will have next week a look into that. I often use Button to open osd and then press on other button(long press in very latest companion) to reset bl616 and in turn core. Also F12 button to open / close as very basic usb test.

[vanbako]

Tried another keyboard and mouse and now the OSD works!

[vossstef]

Tried another keyboard and mouse and now the OSD works!

can you pls let me know what brand txpe did not work ?

[vanbako]

Tried another keyboard and mouse and now the OSD works!

can you pls let me know what brand txpe did not work ?

The non-working keyboard is an old Razer Tarantula RZ03-0007
I've got a non-working monitor as well: Samsung P2270 LS22EFHKFU/EN

[harbaum]

While USB devices can potentially be fixed and thus are worth listing, the non-working displays simply don't cope with the retro video signals. There's not much we can do about this and thus it's probably better to list the ones that do work. Also the displays are a pre-order thing and certain displays only work with certain cores while the keyboard and mice are "global" and either work with all cores or with none.

[xReppa]

#If the F12 key does not open the OSD then nothing else will work as this is nowadays needed to select the floppy disk image. The info about the default df0.adf is outdated.

You solve my issue so fast, i'm trying to get this working for days xD, i was expecting the auto boot, go win wasn't able to flash my tang, I use a virtual machine to get openfpgaloader :D , then buffalo to flash the m0s and the companion onto the BL616. Having a nice sd card ready with hdf and adf file. And then i was stuck here.

Finally by watching short on youtube for the nanomig, the 2nd short showing the diagnostic use with a keyboard, i realize the usb C port of the m0s act has an usb port to plug my keyboard and mouse ... and now still stuck, i have tried for once the issue tab in github, and your comment solve everything !

Bravo to everyone for this amazing work ! i'm trully amazed, the Amiga 600 is 3 years of my childhood, and being able to enjoy it like that is incredible, i wonder if i can fit the tank into a real brand new amiga shell xD

anyway sorry for the long post but thank you so much !!! and happy new year everyone !