In a Bootloadable project, I need to access CyResetStatus but it always says CY_RESET_SW, regardless of how the chip reset. This is caused by the the bootloader running on startup, which exits with CySoftwareReset(). This overwrites whatever was in CyResetStatus previously. Is ...Read more
If you are using ESP32CAM AI Thinker, the embedded camera is an OV2640 so only part of the code will be compiled/executed, see below. The bottom line is you could leave code as-is, it should be ok Note that frame size can take following values : frame size QQVGA(160x120),HQVGA(240x176),QVGA(320x240)Read more
If you are using ESP32CAM AI Thinker, the embedded camera is an OV2640 so only part of the code will be compiled/executed, see below.
The bottom line is you could leave code as-is, it should be ok
Note that frame size can take following values :
frame size QQVGA(160×120),HQVGA(240×176),QVGA(320×240),CIF(400×296),VGA(640×480),SVGA(800×600),XGA(1024×768),SXGA(1280×1024),UXGA(1600×1200)
A global in both projects: CY_SECTION(".reset_info") volatile struct t_reset_info reset_info; Then in the linker script of each project: MEMORY { rom (rx) : ORIGIN = 0x0, LENGTH = 262144 ram (rwx) : ORIGIN = 0x20000000 - (65536 / 2), LENGTH = 65536 - 128 nld (rw) : ORIGIN = 0x20000000Read more
A global in both projects:
Then in the linker script of each project:
That way, it’s certain that the two programs will both have access to the same NOLOAD memory, and neither will corrupt it by having the memory used for anything else.
See less