terekgabor said  

Now it’s time to learn how to compile picomite files.
Is there any instructions somewhere how to do it?

Follow the details of the RPi folks for the SDK, including checking you can build their examples, then grab Picomite files from github and it'll be obvious.

Quite an exercise if you've not done such things before.

John

Huh...  I've never found compiling *anything* to be "obvious". lol

  terekgabor said  

Now it’s time to learn how to compile picomite files.
Is there any instructions somewhere how to do it?

Thx,
G@bor

Here are instructions for Linux (I use the Linux subsystem in Windows)

INSTALL PICO SDK



SETUP PICOCALC FIRMWARE


EDIT ~/picocalc/PicoMiteAllVersions/CMakeLists.txt TO CHOOSE TARGET


BUILD PICOCALC FIRMWARE

Edited 2026-04-06 01:51 by toml_12953

@Peter, Geoff,

Since V6.02.02 is dropping the CAMERA support for the OV7670 in RP2040/WEB builds, I wanted to upgrade my camera to the latest V6.02.01 that supports CAMERA.

But in V6.02.01 the camera does not work.
- the LCD picture is square (not 160x120 or 320x240 as in versions starting V5.08.00), and full of noise. As if the timing is completely wrong.

Pico was run at 252MHz in 5.08.00 and 6.02.01.

I hope this can be repaired, alternatively remove the command form the manual.

Volhout
Edited 2026-04-09 21:13 by Volhout

Thanks Tomi! I will try!

Volhout. Please try setting OPTION SYSTEM I2C sdpin,sclpin,SLOW. There are no obvious differences in the camera code between 5.08.00 and 6.02.01 other than an I2C timeout setting.

Hi Peter,

Changing system I2C speed has no impact.

Measured on  V6.02.01
XCLK = 12MHz
PCLK = 3MHz
VSYNC = 15Hz ... ?
HSYNC = 1.9kHz

Volhout
Edited 2026-04-09 22:16 by Volhout

Are you using exactly the same H/W for both versions and does the change happen each time you swap firmware back and forward?

Peter,

Yes, same hardware. Connect USB, FIRMWARE UPDATE, program the same options (manual).
I do not move a wire. All happens behind the console. Below is test 60201rc8 (is fastest 60201)



On 5.08.00 I used BITBANG CAMERA.

Volhout

P.S. is the camera code using memory that is not completely in heap ? Memory map has changed I recall.
Edited 2026-04-09 22:27 by Volhout

There are no relevant changes to the memory handling. Can you try with a RP2350 just out of interest?

Peter,

I can try tonight, when I get access to a Game*Mite with 2350. At work atm.
Not sure if dupont wires will cause problems.

Volhout

Hi Peter,

The RP2350 CAMERA works correct.
It is only the RP2040 that behaves weird.

In the RP2040 it looks as if only 240 or 255 of the 320 pixels are shown (square picture), and there is noise. Lot of noise. But when you use SCALE 1 (should be 160x120) also a small square picture is shown, same noise level. It is not "truncating" the picture as if horizontal is a byte in stead of a 16 bit value.

The camera signals (XCLK,PCLK,HS,VS) look the same on the 2350, so it is not in the signals to/from the pico (I guess pico only outputs XCLK, camera generates the rest).

Regards,

Volhout
Edited 2026-04-10 04:49 by Volhout

So the code is correct and the RP2040 is now somehow too slow in some part of the processing. This is all about this issue of cache hit rates and how tiny code changes affect specific routines depending on their exact location in memory relative to 4 or 16K boundaries

Peter,

Yes, that must be it. When I run the 2350 at 150MHz, I get the same behaviour.
At 200MHz it is correct. I don't have the 2040 wit me at home, so I can't confirm, but I estimate your are correct.

What should Geoff do ? Remove CAMERA from the 2040 manual ? Or (I still have to test that) indicate you need at least 300MHz CPU speed ?

Volhout
Edited 2026-04-10 04:59 by Volhout

Try the RP2040 at 378MHz - be interested to know the result

Peter,

Will do so tomorrow.

RP2350 in Game*Mite
CPUSPEED      LCD
150000       1/2 picture + noise
160000       2/3 picture + noise
180000       full picture with lines
190000       full picture with some lines
200000       full picture OK

Volhout
Edited 2026-04-10 05:04 by Volhout

oops, wrong thread  
Edited 2026-04-10 13:41 by mozzie

Peter,

RP2040 V6.02.01 CAMERA command.

CPUSPEED       PICTURE
252000       3/4 screen noisy picture
272000       5/6'th screen, noisy picture
280000       Camera configuration error (*)
288000       OK
290000       invalid clock frequency
300000       OK
315000       OK
350000       invalid clock frequency
360000       OK
372000       OK
378000       Camera configuration error (*)

The invalid clock frequency is an error message from the MMBasic core. You simply can't set these clock frequencies.
The "Camera configuration error" shows (repeatable) when opening the camera. Maybe the 12MHz cannot be generated ?  It is not I2C related since it is not an I2C error.

Anyway... 378MHz does not work, but 372MHz works.


EDIT: At frequencies where the picture is okay (i.e. 288/300MHz) the pico shows a white screen on LCD after few minutes. This can only be fixed by a restart. At 252MHz (where the picture is corrupted) the system still runs after 20 minutes. I will investigate a bit further.

EDIT2: I checked the original camera configuration (before I tried converting it to V6.02.01) and confirm this morning again. The old config (V5.08.00) ran at 133MHz flawless. This is just to confirm the white screen is not a result of my setup.

Volhout
Edited 2026-04-10 17:40 by Volhout

Volhout
Please try the attached and let me know if it works

PicoMite.zip

Hi Peter,

Has been running for 15 minutes now. Stable picture at 2040 252MHz

200MHz is 2/3 screen
230MHz has lines in the picture.
252MHz is fine

Will leave this running (at 252) for the rest of the afternoon.

What has changed ?

Volhout