Firmware

[thbreidenbach]

Hey, could you elaborate on the firmware release? The Binaries include several test u2f but I'm asking myself which is the exact firmware. I just finished my build an hopefully it'll work.

[mlorenzati]

Sure, there package has different test for the submodules, the one you want for RGB2HDMI is the integrationtest.uf2 Please start validating HDMI works (check the Resistor array is are not tied to each other or to ground), then check AFE. If youc can validate with microscope the pins on the AFE and clean througfully solder flux since it affects the capture.

[thbreidenbach]

Great, Thank! I upladed the integrationtest firmware and can successfully see the menu. Colors are washed out greatly which might be an issue with the used WM8214. Will start working on a db23 adapter and test on!! Maybe you could collect the different sources of information (PCBWay, Google, etc.) here? I will assemble information for a1k.org and will give some assembled boards to testers there. Is there something to keep in mind regarding the WM8214 whilest troubleshooting?

[mlorenzati]

I do need to complete what I started in https://github.com/mlorenzati/pico-rgb2hdmi/tree/gain_offset_options to allow offset and gain per RGB to manage the color differences due to timing between WM8213 and WM8214. Also could be possible to tweak the timing on the pio capture program but that would be an overkill IMO. If colors are shifted that's the wm8412 timing, if washed is more related to flux messing with an unwanted rc profile

[thbreidenbach]

Hi, I get really bad sync and colors are way off which will be an issue of the wm8214. At first the picture is extremely dim ´. With gain and offset this can be partially solved but blue seems to be mostly missing. Would it be possible to output a dedicated test image on the host computer and let the pi calculate offset and gain per rgb?

[mlorenzati]

Bad sync can be multiple things, please check videos on yt about how it looks like as for today, since video has some glitches that has to be managed on firmware but not extreme. To validate you have a clean WM8214, (as I said clean with iso and toothbrush and clean with hot air on 200-240 degrees.

Finally, set video capture on 320x240 to see how it looks, if better you have pending dirt. I still need to complete manual per RGB gain and offset, no time to complete it yet.

[ottifant011]

I have built myself a Pico RGB2HDMI. How can I programme it under windows? Is there a manual for beginners?

[thbreidenbach]

Usually one just connects the RPi Pico to the windows computer and drags the fw file in the newly added drive (which represents the pi) which firmware you need can be seen in this thread. (integrationtest.uf2) Which Chip do you use? WM8213 or WM8214?

[ottifant011]

hm i have already done that but nothing is happening, no image output no flashing led nothing. I only got the WM8214

[ottifant011]

if i de-energise the pico it seems to be empty again u2f file no longer there

[charlysan]

@ottifant011, you can first try out with hdmiTest.uf2. That should send some stuff through the hdmi port. And remember that the Pico MUST be in Mass Storage Mode in order to transfer a UF2 file onto it. To do this, press and hold the BOOTSEL button and then plug the Pico; then release the BOOTSEL button.

[Silveriomrs]

if i de-energise the pico it seems to be empty again u2f file no longer there

Every time you hold push the button the RPi Pico reset and clear the memory. So that's why you see it again empty.

[ottifant011]

@ottifant011, können Sie zunächst einmal ausprobieren hdmiTest.uf2. Das sollte einiges über den HDMI-Anschluss senden. Und denken Sie daran, dass sich der Pico im Massenspeichermodus befinden MUSS, um eine UF2-Datei darauf übertragen zu können. Halten Sie dazu die BOOTSEL-Taste gedrückt und schließen Sie dann den Pico an. Lassen Sie dann die BOOTSEL-Taste los.

I have already tried that, but unfortunately nothing works or there is no HDMI signal

[ottifant011]

what i don't understand it is immediately recognised as a drive without me having to press a button

[thbreidenbach]

Why wouldn’t it? That’s how it’s built.

[mlorenzati]

@ottifant011, to burn the firmware into the device

• press RESET
• press BOOT
• release RESET That should show the pen drive option on the computer

Start with the simple HDMI demo, test it in monitors with DVI back compatibility, TVs is more likely not to work with that firm.

HDMI support has to be integrated from what I built in https://github.com/mlorenzati/PicoDVI

[ottifant011]

i just can't get a picture output, a monitor says outside the working area

[charlysan]

@ottifant011, have you tried using a different monitor? My monitor experiences issues at certain resolutions, however, hdmiTest.uf2 has always worked. What about your Pico? Have you checked to ensure it's working well?

[charlysan]

I've just checked using hdmiTest.uf2 from pico-rgb2hdmi-0.6.3.zip and it works as expected. I followed the instructions from Marcelo.

And BTW, this also works for me:

1. press BOOT and hold
2. press RESET
3. release BOOT

[ottifant011]

tomorrow i will build a new one piece by piece, for HDMI test picture you don't need an input circuit with ic's. I'm building the Beta3 but that shouldn't matter, maybe the chinese have delivered with it. Do all HDMI sockets have the same pinout? not that's where the fault lies

[ottifant011]

I've just checked using hdmiTest.uf2 from pico-rgb2hdmi-0.6.3.zip and it works as expected. I followed the instructions from Marcelo.

And BTW, this also works for me:

1. press BOOT and hold

2. press RESET

3. release BOOT

I did it exactly the same way and no test image appears even when rebuilding

[charlysan]

I've just checked using hdmiTest.uf2 from pico-rgb2hdmi-0.6.3.zip and it works as expected. I followed the instructions from Marcelo. And BTW, this also works for me:

1. press BOOT and hold

2. press RESET

3. release BOOT

I did it exactly the same way and no test image appears even when rebuilding

@ottifant011, I recommend opening a new issue titled 'No HDMI Output' for a detailed discussion on this problem, since the current thread is specifically for clarifying aspects of the firmware release.

And considering that the main question in this discussion has been resolved, I am now closing this issue.

cc: @mlorenzati