Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tam
miegapele wrote:So it works without EasyFlash, which is not very useful
#if CONF_BL602_USE_1M_FLASH
XIP_SFlash_Read_Need_Lock_Ext(
&g_flash_cfg,
addr,
dst,
len
);
#else
XIP_SFlash_Opt_Enter(&isAesEnable);
RomDriver_XIP_SFlash_Read_Need_Lock(
&g_flash_cfg,
addr,
dst,
len
);
XIP_SFlash_Opt_Exit(isAesEnable);
#endif
TL;DR: For people flashing OpenBL602 on 1MB BL602L10 modules, the breakthrough was a 1MB flash define plus a custom partition layout; one tester confirmed standard releases now work on 1MB, and another key finding was: "the release for 2mb now works on 1mb too." This solves the classic freeze at EasyFlash init and makes XT-BL12/DT-BL12 practical OpenBeken targets. [#21798426]
Why it matters: This thread turns 1MB BL602L10 devices from borderline unsupported hardware into flashable, usable OpenBL602 targets with known limits.
| Option | Flash size | Status in thread | Main limitation |
|---|---|---|---|
| Early stock 1MB BL602L10 | 1MB | Boot freeze / EasyFlash failure | Stuck at ENV init without 1MB support [#21431575] |
| 1MB build + custom TOML | 1MB | Boots and saves settings | Tight space, LFS/media/OTA trade-offs [#21438533] |
| Standard 2MB release | 2MB | Works normally | None specific to flash size in thread [#21609804] |
| Later standard release on 1MB | 1MB | Reported working | Still flash-layout dependent for advanced features [#21798426] |
Key insight: The decisive fix was not firmware size alone. The real blocker was BL602 flash access on 1MB parts, solved by enabling
CONFIG_BL602_USE_1M_FLASHand pairing it with a partition layout that gives PSM enough space to save config. [#21438533]
CONFIG_BL602_USE_1M_FLASH := 1 with a build based on BL IoT SDK 1.6.39, built on February 13, 2025. [#21438533]ENV start address is 0x00000000, even when partition addresses looked correct. The fix was enabling CONFIG_BL602_USE_1M_FLASH := 1, then doing a clean rebuild so the new code path was actually compiled. After that, testers reported normal EasyFlash startup, sector formatting, and successful boot on 1MB parts. An expert summary from the thread was: "CONFIG_BL602_USE_1M_FLASH is what we where after." [#21438533]CONFIG_BL602_USE_1M_FLASH switches the SDK to 1MB-compatible flash read logic instead of the default ROM-driver path used on larger parts. The thread found a conditional in the SDK where 1MB builds call a different XIP_SFlash_Read...Ext path. That mattered because standard reads froze during PSM and EasyFlash access on BL602L10. Once enabled, the same firmware could boot on 1MB parts and still worked on at least one 2MB module, so the flag became the practical compatibility switch for BL602L10 support. [#21438486]Alloc an ENV failed errors during config writes. [#21440834]/api/pins requests caused timeouts and memory drops in the thread. 3. Test from a clean AP setup, short wiring, and a light web session before enabling more features. One user watched free memory fall from about 113,856 bytes to 18,336 bytes, followed by Memory Allocate Failed and a dead web UI. That points to resource exhaustion under load, not a simple flash problem. [#21441931]error when get FW partition followed by a dead loop warning. Free memory then fell from about 102,080 bytes to 15,576 bytes, followed by Memory Allocate Failed. The thread conclusion was simple: OTA code needs a partition-existence check before starting the update path on 1MB layouts that do not reserve a real OTA slot. [#21620849]