New development firmware release v1.19.0.b1

[iwahdan]

Re: New firmware release v1.19.0.b1
Hi all,
In this development releases we also added light sleep funtionality, it is more graceful sleep mode than deep sleep where digital peripherals, most of the RAM, and CPUs are clock-gated, and supply voltage is reduced. Upon exit from light sleep, peripherals and CPUs resume operation, their internal state is preserved. you can read more about Sleep modes in esp32 here .

To Enter light sleep mode you can use API:
machine.sleep(time in ms) if no arguments given module will sleep till next reset unless a wakeup source is configured before going to sleep.

Please Note that:
1- API machine_pin_deepsleep_wakeup was renamed machine_pin_sleep_wakeup as now you can use it for configuring wakeup source for both light and deep sleep.

2- when Light sleep mode Wifi, bluetooth and LoRa are disabled and currently connection is not restored after wakeup (you have to restore it manually with scripting), we are currently working on automatically restoring Connection after light sleep wakeup.

Thanks, waiting for your feedback :)

[iwahdan]

Also the following Pull requests has been incorporated in this Dev release:

PR #165
PR #146
PR #145

Still working on other Pull requests, to be merged in coming releases.

Thanks for your support

[soulsurfer]

Further to this thread:

https://forum.pycom.io/topic/3207/uasyncio-support

does the the new dev release include uasyncio support?

[bmarkus]

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

[Xykon]

@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.

[timh]

@soulsurfer Truly hope this has made it in.

[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.