New version 1.49.2 to test before final release

[cicciocb]

No, you are right, the bin 1.49.22 are with FFAT; you can check the message at the boot of the module in the serial console (should print FFAT or LITTLEFS)

[RonS]

Hello to all
I am using the Toolkit 1.1 beta and trying to flash an ordinary ESP32pico D4 ATOM lite with the yellow button "Firmware + OTA + Data".
Although I set the correct SSID and password in the form that then follows (and I can see it set that way in config.ini), the WIFI settings seem to be ignored. It does not attempt to log in as a WIFI client, and the module immediately boots in AP mode.

I don't recall anyone mentioning this before. Can anyone confirm this?

I also noticed something like that, but I'm not sure if I didn't do something wrong somewhere - filling in the "station" parameters is also ignored or nothing works anymore - or I have entered something wrong.. you never know )
to prevent insights into the then unprotected network part I have activated the "Protection Mode" which works - with the cams I have not noticed this yet but with my ES32-NodeMcu with connected display

happy Easter
Ron

[PeterN]

I also noticed something like that, but I'm not sure if I didn't do something wrong somewhere - filling in the "station" parameters is also ignored or nothing works anymore - or I have entered something wrong.. you never know )
to prevent insights into the then unprotected network part I have activated the "Protection Mode" which works - with the cams I have not noticed this yet but with my ES32-NodeMcu with connected display
happy Easter
Ron

Hi Ron,
I used station mode for a test with no problems. In my experience, the subnet_mask is a mystery to many people and a very likely failure point (255.255.255.0 fits most 192.168.x.y home networks)

[PeterN]

Hello Francesco,
a question about PIN MAPPING under /config/advanced:
Does the remapping of the SPI pins also affect the MAX7219 dot matrix display commands?
On a M5Stack ATOM lite or Stamp Pico I did not manage to remap the pins for the MAXSCROLL.XXXX commands.
I haven't investigated this very deeply - could also be a pullup resistor issue (?)

[cicciocb]

Hello Francesco,
a question about PIN MAPPING under /config/advanced:
Does the remapping of the SPI pins also affect the MAX7219 dot matrix display commands?
On a M5Stack ATOM lite or Stamp Pico I did not manage to remap the pins for the MAXSCROLL.XXXX commands.
I haven't investigated this very deeply - could also be a pullup resistor issue (?)

Yes, this should be the case.

[PeterN]

...
Yes, this should be the case.

Thanks, I will now try again with a different focus.

[tiff]

Hi, i'm new to annex and i'm mostly interested in ESP32-Cam so there is the question, is somewhere the cam XClock exposed?

[cicciocb]

Hi, i'm new to annex and i'm mostly interested in ESP32-Cam so there is the question, is somewhere the cam XClock exposed?

No,the value is fixed internally and cannot be changed.
If I remember well I experienced very little impact into changing the value

[tiff]

Hi, i'm new to annex and i'm mostly interested in ESP32-Cam so there is the question, is somewhere the cam XClock exposed?

No,the value is fixed internally and cannot be changed.
If I remember well I experienced very little impact into changing the value

Hmm, that depends on what you expect.

Fast XClock is neccessary if you want high frame rates in bright environment. In low light conditions you want lower XClock because the longer the time the more photons can hit the sensor and no need turning amplification to high and earning more noise from that but with the draw back of less frames per second.

That does not work well on all boards i have but on some i can go up to 24MHz.

[cicciocb]

Interesting, I never explored in that domain.
Thanks for the tip, I'll try to implement the feature