RBCP GET FLASH SLOT INFO FAILED (C64)

[FrankenLab]

I thought I had understood how to do this, but I keep banging my head against the wall. I have OneROM in the kernel slot and the original physical BASIC and Character ROMs. I want to be able to switch kernels from the boot menu. I tried using the JSON method and then the CLI, but both give me the same error, RBCP GET FLASH SLOT INFO FAILED, with no menu.

.\onerom-cli.exe program `
   --plugin usb `
   --plugin host-control `
   --slot "file=https://images.onerom.org/roms/host-control/v0.1.0/c64_bootloader.bin,type=2364,cs1=0" `
   --slot "file=JiffyDOS_C64_6.01.bin,type=2364,cs1=0" `
   --slot "file=deadtest.BIN,type=2364,cs1=0" `
   --slot "file=destest-kernal.bin,type=2364,cs1=0" `
   --slot "file=2_dead_test_kinzi_006.bin,type=2364,cs1=0"
Programming device - DO NOT DISCONNECT
Programming complete

I've got a Fire24e with v0.6.14 firmware.

[piersfinlayson]

The CLI command looks right to me.

It may be there's something about your hardware that makes timing not work. Can you give some details of your C64 - type, PCB revision, whether you have a replacement PLA (what sort), etc?

[FrankenLab]

The motherboard is a model 250407. It's all stock except an RF modulator replacement and the SID which is a SIDkick Pico with a 2040 Pi Pico. It would make sense that might cause issues, but I just tried pulling that out and got the same error.

[piersfinlayson]

Try:

c64_boot.bin

Instead of

c64_bootloader.bin

c64_boot.bin is the version I wrote - it's not as good as c64_bootloader.bin, but was designed to work with replacing just kernal.bin.

c64_bootloader.bin was written by someone else, and intended to replace all of the kernal, BASIC and char ROMs.

[FrankenLab]

[FrankenLab]

I just pulled the PAL chip and used a modern replacement version, but I got the same error. It's bed time here, so I'll check back tomorrow evening. Thanks Piers!

[piersfinlayson]

I'll be testing this area in the next day or two, so I'll reverify this myself.

[piersfinlayson]

I just tested 0.6.14 with fire-24-f on my C64 (250425) and it works fine.

Ah, I just noticed your ceramic and gold VIC-II chip. I suspect that's doing something a bit weird on the bus - I've had problems with those before. Do you have a different video chip you can try?

[FrankenLab]

I do have another VIC-II, I just swapped them but got the same error. What's the difference between the 24-e and 24-f?
The ceramic VIC-II is a 6567R9 and the one I just swapped is a 6567R8, the system is NTSC. I've run a full diag with harnesses on this board and it's passed everything. I'm happy to try anything you suggest. I have a scope, but no logic analyzer.

[piersfinlayson]

fire-24-e an fire-24-f - really the only difference is the RGB LED.

I just tried fire-24-e and did see one instance of GET FLASH SLOT INFO failed.

I also tried with firmware v0.7.1 (which I am working on) and a later version of the host-control plugin, and didn't see any failures. This isn't conclusive, but it's possible one of the fixes in v0.7.1 and/or the host control plugin have fixed whatever this edge case is/was.

v0.7.1 isn't far from being released now I've successfully tested this - should be out this week.