FPGAconf does not support .bin files.

[sbagneris]

FPGAconf explicitly wants .bit files to flash firmware onto a Pluto II board. This is no longer provided with the 3.0 release.

It is possible to rename the .bin file file to .bit file and FPGAconf will happily (foolishly?) flash the file onto the board but when booting the picture is now black and white and the following message is displayed:

"!!! Updater hardware ID is invalid !!!"
"--> YOU must choose the correct ID <--"
"Main firmware is missing"

A rotating cursor is displayed bellow and when pressing the z-button a hex dump of the ROM is displayed that can be navigated up and down the memory addresses.

Long live GCVideo!

[ikorb]

It seems that FPGAconf is trying to remove a header from the "bitstream" file to get to the actual contents and the part it removed it small enough that the FPGA still boots. However, the flasher that starts first thinks that the main firmware is bad and starts its recovery mode instead of booting the main firmware.

Good thing I added that memory hex viewer for diagnosing problems like this. =) Run it, hit the X button (should jump to address 30000), take a picture, hit left on the D-Pad once (shoudl jump to 2ff80) and take another picture. With a bit of luck that should be enough to figure out how to build a pseudo .bit file that can be flashed with FPGAconf.

[sbagneris]

You bet!

Note to anyone else reading that the Pluto board is not bricked when doing this. One can easily revert to 2.4d without harm.

Thanks for your prompt response and of course the super killer gcvideo!

[ikorb]

Thanks!

Unfortunately FPGAconf did something completely against my expectations - instead of dropping the (nonexistant) .bit header, it added something, which shifts everything backwards instead of forwards. Could you take another screenshot from address 0?

[sbagneris]

No problem.

I included the first two pages.

[ikorb]

Thanks. The file below might work with FPGAconf. If it doesn't, I'll probably need a few days to dig out my own hardware to figure out a workaround.

(removed, please use the file from the 3.0a release)

[sbagneris]

Success!

[ikorb]

Nice! Thanks for helping figure this out, I'll add a link to the release notes.

P2XH Wii fake bitstream in case someone actually uses it:
(removed, please use the file from the 3.0a release)

[sbagneris]

Thank you very much. I would have given you two thumbs up but I can’t quite levitate my camera yet. Most thing at first glance seems to function just fine. I’m excited for the built in firmware upgrade.

[ikorb]

Actually the system is resilient enought that you could have used the 3.0 updater to install a working main firmware by manually selecting the correct board ID - but since you appeared to be a willing victim, I preferred to work out the problem so others can avoid it completely.

[sbagneris]

By all means!

[Tazberry]

@sbagneris what are you using to update ur pluto?

[sbagneris]

I'm using the basic TXDI header from KNJN along with FPGAconf software that should have come along your purchase of the Pluto board. A judicious search online should net you a downloadable package for FPGAconf if you have lost the files. (it is not available on the KNJN website for some reason) or email KNJN for a link.

[Tazberry]

@sbagneris Is it possible I can get a link to all this. Doing this for the first time.

[GizmoTheGreen]

what are you using to connect to the TXDI header if you don't mind me asking? I've got a Sparkfun FTDI basic. put the TX in invert and been emailing KNJN. checking voltages on the TX RX lines etc but can't for the love of me program the thing.
it just times out! (still on 2.4c)

[sbagneris]

I use a bog standard USB to serial adapter and I plug the TXDI header right into it.
This looks pretty identical to what I have:
https://www.amazon.com/dp/B0000VYJRY/ref=cm_sw_em_r_mt_dp_U_C1GhEb3Q1G029

The specific TXDI header I use is the plain jane one without the RS232 chip built in ($6.95)
https://www.knjn.com/ShopAdapterBoardsTXDI.html

Additionally, the following may be of further help:
https://www.knjn.com/docs/Re-programing%20Pluto-IIx%20HDMI%20with%20the%20latest%20gcvideo%20release.pdf

[GizmoTheGreen]

I use a bog standard USB to serial adapter and I plug the TXDI header right into it.
This looks pretty identical to what I have:
https://www.amazon.com/dp/B0000VYJRY/ref=cm_sw_em_r_mt_dp_U_C1GhEb3Q1G029

The specific TXDI header I use is the plain jane one without the RS232 chip built in ($6.95)
https://www.knjn.com/ShopAdapterBoardsTXDI.html

Additionally, the following may be of further help:
https://www.knjn.com/docs/Re-programing%20Pluto-IIx%20HDMI%20with%20the%20latest%20gcvideo%20release.pdf

thanks for your input. I've read that PDF and referenced it when I hooked up the FTDI.
as I mentioned I've been emailing KNJN and they say it looks correct but have no idea why I can't program the board.

I should probably make a new "issue" to try and get help with this here but for now I'll just share the pictures.