@reidfo said in New Firmware Development release v1.19.0.b4:
On both mac and linux I'm getting unexpected sha1 checksum when I try to install the latest development release on FiPy.
Are you using the beta firmware updater?
There are some eDRX-related commands as well:
eDRX Read Dynamic Parameters: +CEDRXRDP
eDRX Setting: +CEDRXS
Specific eDRX Settings: +SQNEDRX
I have no idea if PSM/eDRX commands are implemented and working as expected because I did not test them yet.
In my opinion Pycom should provide statement regarding readiness of PSM/eDRX features implemented in the modem's firmware because without these features it is not possible to develop battery-powered solutions with reasonable long battery life-time which is the main purpose of NB-IoT.
There should also be tutorial available in the documentation because of importance of these features.
The issue is that socket.connect() and SSL handshake will not timeout also in case the socket timeout is set and hang the application forever.
More than 1 way to skin a cat! Renamed upgdiff_33080-to-39529.dup to upgdiff_33080-to-39529.py, uploaded it via the upload button in atom, used Filezilla to change the extension back to .dup in the gpy flash then upgraded the modem.
Your modem has been successfully updated.
Here is the current firmware version:
@rskoniec we have decided not to publish that procedure. It is unsafe (module can be easily permanently damaged) and may not work in every case. We are still working on an internal procedure as well. I'd recommend opening an RMA request and sending it back instead of trying to repair it yourself.
More simple procedure on Linux :
start from the Linux menu "Pycom Firmware tool", quote "include dev releases"
then just choice /dev/ttyACM0 in High transfert mode
the firmware is flashed in 1.18.1.r1
Wrote 1.19 MiB from sipy.bin in 1 minute and 13.88 seconds
@xykon said in New Firmware Updater version 1.15.1:
@bmarkus Win32:Evo-gen [Susp] is a broad classification used by the Avast Behavior Monitor feature for software that exhibits suspicious behavior categorized as potentially malicious. The Behavior Monitoring feature observes the behavior of processes as they run programs.
The firmware updater connects to the Internet. That is considered "suspicious" for some anti-virus applications.
Thanks for the details. However it is a bit strange,a s I'm frequently installing programs connecting to the net during installation and have never seen such message from my AVAST.
Anyhow, I will ad it as an exception.
We could change the default sort order but I'm not sure this would affect existing users. I admit it throws me off too if I'm on the forum but not logged into my account. I'll see if our system admin can do some internal tests.
Hi @mongkol, so you have this error every time you try to update? Or just once in a while? I would suspect the PC USB port to be the problem, you could:
change the USB-microUSB cable
use the PC direct USB port, not thru a USB hub;
remove other USB peripherals from PC
The firmware update packages are sent over DFU protocol, which runs over USB bulk transfer channel, it might happen that the CRC of a package was wrong (or delayed).
I have upgraded device (WIPY2.0) from 1.7.2.b1 to 1.9.2.b2 and have problems:
ntp_sync most of the time not wrok (hang and never ending)
i use for it old method
def getNTPTime(host = "pool.ntp.org"):
port = 123
buf = 1024
address = socket.getaddrinfo(host, port)[-1]
msg = '\x1b' + 47 * '\0'
msg = msg.encode()
TIME1970 = 2208988800 # 1970-01-01 00:00:00
# connect to server
client = socket.socket(AF_INET, SOCK_DGRAM)
msg, address = client.recvfrom(buf)
t = struct.unpack("!12I", msg)
t -= TIME1970
tuple_time = time.localtime(t)
but also tested if rtc.ntp_sync could help but same result :(
i2c not work - i2c buss error
i init it with id=0 (i do not remember if in 1.7.2 it was hardware or software based)
bus=I2C(0, I2C.MASTER, baudrate=100000, pins=("P19", "P20"))
to test it what is going on i have updated board 3 times (all times sucessfully)
but with the same result
i have downgraded firmware back to 1.7.2.b1
all work without any problems - any hint?
when i press download into new folder (pymakr VS configured on COM port)
all files are downloaded but 3 of them cannot be downloaded
tried many times with reset, disconnect ...
Downloading 3 files...
[1/3] Reading lib/sensor.py
Failed to download lib/sensor.py
[2/3] Reading lib/konfig.py
Failed to download lib/konfig.py
[3/3] Reading lib/GPS2.py
Failed to download lib/GPS2.py
this is how it looks like in Filezilla:
Do you have any concept what can be wrong? - because e.g. file sensory.py is quite small
name is also in lower letters without numbers - nothing special.
konfig.py is really small file 696 bytes...
I can of course do this by Filezilla but..