EclaireXL

we have sync...
zpu is running, tested with a display of toggling background
sdram is failing with 180 degrees

sdram test passes with 270 degrees! Still no boot though, will resume testing tomorrow.

Fiddled with sd card... blue screen and cassette boot beep. Hmmm.

Seems I need to remove/re-insert the sdcard to boot. PS2 doesn't seem to work, so no menu. Perhaps that is why I get the beep (consol stuck??)

consol is stuck because of the c64 keys supplied by chameleon 2 io. Tracking down why that is stuck, it has 3 sources: ir, docking or c64 itself

Stuck keys were because the remote is not part of chameleon io, I hadn't removed the external signals and they were defaulting to the wrong state. Removed them now and typing in basic.

Adding the chameleon_2 shiftreg component fixed up the ps2 keyboard sometimes not working. Also plumbed the sio tx to the red led.

Main things to fix:
i) Joystick resetting system!
ii) sd card fiddling needed on first boot

Fixed issue (i)

Running NUMEN as a little test ;-)

Different sd card worked, think its a card re-initialization issue...

Haha, this was a known issue on the old version of the chameleon (in many cores) and this one too...

Trying to get the ir remote working, should 'just work' since its enabled in chameleon io2 but ... it doesn't

Weird thing in chameleon_cdtv_remote, the timer counts when ena_1mhz is high AND halfway between. So is running at 2x the expected rate. Its not clear why.

Still don't understand what the logic analyzer tells me, I'm guessing its an optimization since the hdl is pretty high level.

In any case solved the actual issue by adding a synchronizer on ir_data. Working just fine now.

Added back the 'return to menu'

Now trying to plumb in eclaire firmware 'properly'. e.g. settings/os load/save, video settings, 800 mode etc. Got it running as far as menus/drive emulation. Had a bit of difficulty at first because I was doing some binary editing to add version, and removing some characters from the binary by mistake!!

Testing video mode setting (only basic stuff, rgb/vga, no pll reprogramming) and looking ok.
Tested 3rd/4th joysticks in atari800 mode. Got them working but had to change/fix a few small things.
Want to try out flash chip next...

I have a 1MB slot. The core itself takes about 350KB compressed. So lets say we have 1/2 MB conservatively to store roms etc. The standard eclaire settings saving takes 192KB.
I guess I can also allow the rpd flashing support.

So... need to plumb in correct slot address, wire up flash pins and re-enable code in firmware (+update commands?).

+ 3 byte header with binary length (when flashing rpd)

I can't see which flash chip is used, guess I'll just wire it up and try reading the id!

I should be passed the slot by the microcontroller, but since I'm using sof at the moment that clearly isn't working. The firmware is currently hardcoded to 0x200000. Which is slot 2 (but wrong half of it!). Will just give that a spin to test.

OK, that works

Picked up the slot from the micro. Computed the location of the rom. I added 256kb of blank space first to aligned to a block (this board has 64kb but some might be 256kb...). Now loading and saving is working well.

Docs on the chameleon structure of the rom are here:
https://svn.icomp.de/svn/chaco/doc/Chameleon_USB.pdf
Its a bit misleading on the core info location, since it says it starts at 3+N, while really 3+N is the end+1 of coreinfo. It describes it right after though but I didn't read that well!

So now its running pretty well. I'd like to get hotkeys working and I took a shortcut on eclaire and used the usb ones directly. So I need to plumb the ps2 keys into that logic. After which I think its 'ready'.

Of course one more important step: try it in a C64!

Did the keyboard plumbing. Seems to work - okish. Though can save some bytes by doing this part in vhdl I think, so might do that.

Tried it in the c64. Keyboard works, but only sometimes! Need to work out why.

Getting some weird behaviour tonight - cores not starting etc. Unclear what the issue is...

Now behaving again, think Chaco had got confused and was doing weird stuff.

Re c64 keyboard, the state machine reading it appears to get stuck and just reads DC01 repeatedly??

Got a state capture when its working, goes through states as normal.

When it stops, no states are active!

I wonder if ba needs a synchronizer or something like that?

Well added a synchronizer on ba and also added a when others clause to put it back into a proper state.

Should probably discuss with Peter to see if there is a better fix.