New firmware release 1.3.0.b1

[daniel]

@iotoz we have made previous releases available, but 1.1.0 is not there. We'll make that one available on Monday. I'll let you know once that's done.

Cheers,
Daniel

[Feiko]

Thanks I'm looking forward to the fix. Until then 1.1.0 will probably do the job.

[rcolistete]

@iotoz said in New firmware release 1.3.0.b1:

@daniel Thanks for that, I had checked there. I can still only find pycom_update_1.0.0.b3.tar.gz for linux, or any other platform.
Any chance that you can post a direct link to the linux firmware 1.3.0.b1 ?
Would be ideal to see a Git rep with the firmware versions to choose.

See this post :
"The "file" attribute shows the direct link to the firmware binary files. You can then download the file with wget "https://software.pycom.io/downloads/1.0.0.b2-LoPy_868.tar.gz" and use bin/updater.py -t 1.0.0.b2-LoPy_868.tar.gz -p /dev/ttyUSB0"

So for 1.3.0.b1 with 915MHz, download the file :
https://software.pycom.io/downloads/1.3.0.b1-LoPy_915.tar.gz

[crankshaft]

@daniel - Thanks for the update, but I am struggling with the 100 - 120ma power consumption of the wipy2 and need to reduce power by using the machine.sleep modes and RTC.wakeup()

Any idea when this will be added ?

[rcolistete]

@crankshaft said in New firmware release 1.3.0.b1:

@daniel - Thanks for the update, but I am struggling with the 100 - 120ma power consumption of the wipy2 and need to reduce power by using the machine.sleep modes and RTC.wakeup()

Any idea when this will be added ?

Loot at this topic.

[leelive]

Thanks for this update! I have a question about RTC. Our application requires very low power. The RTC doc says, "The RTC counter ticks at 5 MHz.", but the LoPy (OEM) spec sheet says RTC uses 32KHz, Will a future release give us the option of specifying the 32KHz clock?

Thanks!

[toribios_people]

@daniel Version 1.1.0 is still not available in the downloads section, when will it be available? Thanks.

[zmrzli]

Program below switches led colors every minute or so if Bluetooth() is called.
Without it runs as expected.
Is that a bug?

import pycom
from network import Bluetooth

bluetooth = Bluetooth()
pycom.heartbeat(False) # disable the heartbeat LED

while True:
pycom.rgbled(0xff0000) # make the LED light up in RED color
pycom.rgbled(0x00ff00) # make the LED light up in GREEN color
pycom.rgbled(0x0000ff) # make the LED light up in BLUE color

[crankshaft]

@zmrzli - I think you need a short sleep in your loop otherwise it will consume 100% processor time and there won't be time to do anything else ?!

[mohpor]

@zmrzli you are clogging the main thread in that sample code and the CPU never gets to do anything else because of that while True, if you want to change the LED color this fast, try putting it in a thread. And please add some delay between those LED color sets.

import pycom
import time
import _thread
from network import Bluetooth

bluetooth = Bluetooth()
pycom.heartbeat(False) # disable the heartbeat LED

def led_totary(id):
    while True:
        pycom.rgbled(0xff0000) # make the LED light up in RED color
        time.sleep_ms(50)
        pycom.rgbled(0x00ff00) # make the LED light up in GREEN color
        time.sleep_ms(50)
        pycom.rgbled(0x0000ff) # make the LED light up in BLUE color
        time.sleep_ms(50)


_thread.start_new_thread(led_totary, (0)) 

[jmarcelino]

@zmrzli
It's not such a bad question because the ESP32 is dual core. I remember reading the original plan was one core would handle all networking while the other would be totally free for the user to use, not sure if that's still the case. Now I'm curious to find out :)

That said for sure there's all sorts of locks involved even with two cores so could be the reason

[daniel]

Hi everyone,

At the moment we are only using one of the 2 cores, but we plan to enable multi-core support soon. MicroPython will run on core #1 and the network stacks (BT, WiFi, LoRa, Sigfox) will run on core #0. We have chosen to stay on 1 core for a while to wait for the ESP IDF to become stable enough around dual core support.'

Cheers,
Daniel

[zmrzli]

If bluetooth was not working, than that could be blamed on tight loop without opportunity to release processor (sleep), but that is not the case. Following code takes few minutes to get to green light:

import pycom

from network import Bluetooth

bluetooth = Bluetooth()
pycom.heartbeat(False) # disable the heartbeat LED

pycom.rgbled(0xff0000)
pycom.rgbled(0x00ff00)
pycom.rgbled(0x0000ff)

It seems that same resource (line?) driving BLE is used for bit banging LED in 1.3...
There is change about it in 1.4.0, so maybe this will be fixed.