pegasos2: rom reconstruction

@kas1e
I probably did not have to implement anything for this so it's handled by QEMU in some way that I don't know. If the VT8231 has some bits to disable PS2 ports those are likely not emulated but if you add -device usb-kbd then QEMU will direct keyboard input to that so it should work with USB as well. I don't know if the default PS2 keyboard also gets keyboard input with -device usb-kbd but could be that both keep working. Maybe on real machine also both should work but SmartFirmware has only one input source so you can either use PS2 or USB keyboard? In any case you can test with original firmware with -device usb-kbd and if that works with your version too then maybe it's OK.

@balaton
Quote:

On real pegasos2 if you have attached both usb-keyboard and ps/2 keyboard, the usb-keyboard is one which smartfirmware take as the input, and ps/2 is unusable and didn't work.

Quote:

With -device usb-kbd , while i can see with both my and original firmware that i do have:



But then who can say what keyboard works now when i type, ps/2 or usb one from smartfirmware in qemu?:) that why i were in hope to disable ps/2 to see if it will works.

But that anyway not so matter now, because issue was that keyboard was hardcoded to isa, so now i add "set it to isa only after there wasn't usb one found" , to act like original firmware, and then it works.

Now fighting with usb-mass sticks, because simple os4_stick.img, formatted in fat16 works for qemu now (i just go scsi route), but have issues with real sticks on real pegasos2.

Maybe i need to do passthrough for this exactly usb-sticks, so to try real ones on qemu where it all more easy to debug.

@all
Were able to add UHCI support to original OF, so now my firmware can detect usb keyabord, and can detect usb-sticks, and put them to OF as scsi/block devices, and so i can list files on them, etc.

So far all sounds good, if not one moment : i have 3 usb sticks. 2 of them , detects fine, no problem:

Phison Electronics Corp. 16gb (13FE:4300)
Kingston 256gb (0951:1666)


But one which is JetFlash 8GB (8564:1000), while surely works fine and detects fine on windows or on same pegasos2 just via amigaos4, simple fail for me to detects from within firmware: UHCI controller executes the very first address-0 SETUP packet, but the device never gives a valid USB response, so enumeration cannot even read the descriptor. Does not matter what i tried. I compared from amigaos4's usbinfo/ranger the differences: nothing which can explain it. I compare with lspci -vvv from linux : nothing can explain it. In the datasheet on VIA's VT8231 i see nothing about USB quirks or whatever ..

Maybe anyone have any clue or experience with to where a look at ?

The difference is only that i have this stick formatted FFS, and others two (working) are Fat32 and NTFS, but that just about FS, which is not matter until enumeration take place..

@kas1e
I think you should not worry about that too much. Just release the sources and let others help find it out. Rather than spending time with this one USB stick, do the missing parts of the bootstrap for which you can likely use the code from U-Boot for the Marvell Discovery development board that was once upstream and then clean up the sources to be able to put them in a repo so others can help you out with finding issues and further improve it.

@Balaton
Deal with this stick, was some small issue about wrong order initialisation. As for releasing anything: sure, but it firstly should work at all :) Currently i only deal with smartfirmware itself, to be able to boots correctly with original bootstrap , and it still acts in one or another way which need to deal with. Once it will works, i can simple release just a smartfirmware part with a python script which build a new rom from original (extracting bootstrap, combine with our smartfirmware, and create new rom). This way ppls already can use it, while i will worry about bootstrap replacement, which, IMHO, will be harder part.

Currently fighting with another strange issue : when i run original firmware, then soft reset, then i can run my own fine too till workbench boot (both uses same bootstrap from bplan). If i run my firmware after cold boot : Then once i run amigaboot.of it stops/hangs after returning to its own code. No next OF call, and no exception so far. And this can be anything : CPU/cache/MSR/exception/vector state, stack/runtime convention, timer/interrupt state, or some device/platform state original firmware leaves initialized (but only after graphics boot!). And to note that bootstrap is the same bPlan's one..