Why is BL602 LFS (LittleFS) missing in the current build and can it be implemented?

Question

Hey @divadiow and @insmod I am back testing something for 5 minutes and I already ran into a problem 😊 there is no BL602 LFS present in the current build, any particular reason for that or can we implement it? Saw this from @divadiow But wanted to ask first if there was any problems with it??

insmod · Accepted Answer

>>21583316 It can't really be solved on the module itself. But i found a potential fix, will need to add *_OTA.bin file size to ota_header. First in bl_mfg_ota_header, then in rest_interface struct ota_header.

insmod · Accepted Answer

>>21583480 I don't see if they are used, but i think it's better to insert file size after sha256. That way compatibility is guaranteed. Added after 1 [hours] 45 [minutes]: Pushed an update for BL602, needs testing. Additionally added heap_5 for W600. + enabled LTO + fixed building with newer gcc versions (gcc 8 +3kb size, gcc 11 +6kb). Replaced tls_get_netif in WiFI_GetMacAddress with tls_get_mac_addr. Now MAC address is not zeroed at first boot, leading to normal full name. Last release W600 is 545212 bytes, pull with LFS is 548712 bytes. With LFS without LTO is 564952 bytes.

insmod · Accepted Answer

LFS will work on any toml that has media partition. The best toml for the future is To test if firmware check works try to ota to berry on default toml.

divadiow · Answer

welcome back. better LFS support for various partition layouts in unmerged PR from here onwards Added after 1 [minutes]: but you should get LFS now with old 1.4.8 type partition layout toml?

p.kaczmarek2 · Answer

This is the PR that is waiting for BL602 bricked when OTA file after decompression is too large? @insmod

p.kaczmarek2 · Answer

Maybe it could be done in Javascript in Web App? Regarding OTA header - are those bytes checked anywhere? Code: PythonLog in, to see the code Maybe use them to keep uncompressed len and in firmware check for default value (older OTA files) - then pass, otherwise check the lenght.

DeDaMrAz · Answer

@insmod is it in 1629?

insmod · Answer

>>21583601 Yes

DeDaMrAz · Answer

Next question would be to use the toml @max4elektroda provided or stick with the original? LFS present and working, tested with both toml files. Mind you I have no idea what chip is inside WB2-12F module 🙂 Parsing of LFS backup import looks a bit strange thou 😁

DeDaMrAz · Answer

>>21583616 Info:MAIN:Time 288, idle 0/s, free 112400, MQTT 0(18), bWifi 1, secondsWithNoPing 218, socks 2/21 Info:MAIN:Time 292, idle 0/s, free 112400, MQTT 0(18), bWifi 1, secondsWithNoPing 222, socks 2/21 Info:MAIN:Time 293, idle 0/s, free 112408, MQTT 0(18), bWifi 1, secondsWithNoPing 223, socks 2/21 Error:OTA:Unpacked OTA image size (922368) is bigger than running partition size (884736) Info:MAIN:Time 299, idle 0/s, free 111552, MQTT 0(18), bWifi 1, secondsWithNoPing 229, socks 3/21

insmod · Answer

Looks like it works. Just to be sure flash with new toml and try to ota to berry again. Finally merge-ready?

DeDaMrAz · Answer

Let me attach DS18B20 to it first as I think I saw somewhere it can break that sensor (still catching up to all your guys work).

insmod · Answer

Pushed an update for delay_us on BL602. Now uses bl_timer_delay_us instead of nops. Untested.

DeDaMrAz · Answer

>>21583671 oh c'mon! 😁 hold up let me test something first DS18B20 works... Added after 13 [minutes]: >>21583624 OTA to berry passes with the latest build LSF present/preserved and working Final version of the DevCube with corect 2M toml file can be found here - P.S. I know there is a newer version of devcube but haven'g got to it to test it. Added after 9 [minutes]: Will try to find W800 module and test that as well and we can call it a day on this PR, correct? @insmod there is still an issue on importing LFS from backup thought! @divadiow do you have W800 devboard and know where it is maybe? 🙂

insmod · Answer

There is no real difference in devcube versions, the most important thing is correct toml. W800 is already tested and confirmed working. Added after 2 [minutes]:I suppose W600 can be tested, but when i flashed it and did ota everything was ok.

DeDaMrAz · Answer

>>21583704 Does LFS backup import work on W600/800?

insmod · Answer

I don't know, but LFS itself works fine.

DeDaMrAz · Answer

LFS does work fine and is preserved after OTA, but backup import is broken, at least on BL602. Same file just downloaded and reimported as if tar parsing is now being done. Ok, that seems to be the problem in the webapp it self, I'll give it a check soon and report back.

divadiow · Answer

Heyyy. Will reread what's going on shortly. Not sure what needs testing still, if anything.

p.kaczmarek2 · Answer

It seems very good to merge now. Variants improvement is also acceptable. I just need a final confirmation. I saw DS18B20 was tested, but was DHT11 tested as well?

DeDaMrAz · Answer

DHT11 is working on BL602. Added after 35 [minutes]: @insmod Is internal temperature on BL602 now refreshed every second or maybe tied to CH1 somehow?? I got these reading within seconds if DS was set on CH1 If I move DS to ch2 it normalizes.

insmod · Answer

>>21584294 I did nothing to temperature sensor, and even then, there should be no correlation between channels and sensor. It's likely the same in release version.

divadiow · Answer

I've definitely seen the behaviour @DeDaMrAz describes. I'd made the connection with the new SDK rather than any PR, but may be misremembering. I can check unless @DeDaMrAz does first.

p.kaczmarek2 · Answer

I've decided to merge it now. Good job, guys! Now, the next thing I would like to have merged ASAP (so I can also start testing on my side) are BK7251 builds, as long as they just boot into OBK, that's ok. Can you open PRs @insmod ? I would also like go through @max4elektroda PRs, some of them seem interesting, but they need testing really before merge... especially multiple DS18B20s

insmod · Answer

>>21584443 Don't forget to merge XR and W600/W800 pulls.

p.kaczmarek2 · Answer

I see you also ported our old MQTT.c lwip fixes for xr872, nice...

divadiow · Answer

I was about to say maybe the BL602 zip should include the revised toml, but I guess most users would get the individual files from the releases page. How can it be made clear which toml should be used now? Added after 8 [minutes]:Ooh. Could OpenBL602 list partition addresses/sizes so when a user has x issue that info may help with knowing which toml was used for original flash? Might also be useful for mhflasher OTA situations.

p.kaczmarek2 · Answer

maybe add invididual zips to release page instead of just bins? Zip with bin, toml and... a readme.

Why is BL602 LFS (LittleFS) missing in the current build and can it be implemented?

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Post #13

Post #14

Post #15

Post #16

Post #17

Post #18

Post #19

Post #20

Post #21

Post #22

Post #23

Post #24

Post #25

Post #26

Post #27

Post #28

Post #29

Topic summary