New development firmware release v1.19.0.b1

[bmarkus]

@xykon said in New development firmware release v1.19.0.b1:

@bmarkus said in New development firmware release v1.19.0.b1:

Which file system used? Is it readable on WINDOWS/LINUX?

We're now using LittleFS for the internal flash file system in the development firmware rather than FatFS. SD cards keep using FatFS. There is a Fuse wrapper available.

Thanks, I will try it. LittleFS looks good, however lack of timestamp can be an issue in certain applications, even if in many cases it is not important and device is not time synced.

[Xykon]

@bmarkus said in New development firmware release v1.19.0.b1:

Thanks, I will try it. LittleFS looks good, however lack of timestamp can be an issue in certain applications, even if in many cases it is not important and device is not time synced.

We are more concerned about users loosing all their code on the device because the file system got corrupted and reformatted during boot. If you need an fs with timestamps, you can connect an external SD card which still uses FatFS (so you can update the content on a PC).

[rcolistete]

@iwahdan
Any eletric current measurement already made on this light sleep mode ?

[iwahdan]

Hi @rcolistete , yes in light sleep mode the current consumption on a Lopy is 3.5 mA with RTC peripherals ON

[Sympatron]

@xykon I looked into LittleFS and it supports custom attributes per file/folder. So I think timestamps can be implemented. Is there any plan to do so?

[Xykon]

@sympatron said in New development firmware release v1.19.0.b1:

@xykon I looked into LittleFS and it supports custom attributes per file/folder. So I think timestamps can be implemented. Is there any plan to do so?

I will ask the developer who implemented LittleFS to look into that. It would help if you could provide a use case where this is relevant.

[Sympatron]

@xykon I don't have a specific use case. I just wanted to point out that it would not be too hard to implement, because @bmarkus said it might be an issue for some people.

For us it is a lot more important when this version will be available on GitHub. Since we use a custom firmware we cannot really use the new features until I can merge them with our fork.

[gregcope]

@iwahdan what is the assumed current category consumption in light sleep mode?

[iwahdan]

Hi @gregcope for light sleep current consumption is 3.5 mA

[robert-hh]

@iwahdan machine.sleep(time): the time seem to be ms, not us.

[iwahdan]

@robert-hh yes it is a mistake in my post, I’ve corrected it
Thanks

[Sympatron]

This post is deleted!

[Colateral]

Do you push it in github for make build? There is still 1.18.0.

[Sympatron]

@colateral It's in the development branch.