@iwahdan My fipy has version 1.0r printed on the bottom. Can that one be upgraded to support band 8 to connect to T-Mobile Netherlands NB-IoT? "RRC:showcaps" says " board : 3/4/12/13/20/28". I have sent an RMA request and sent multiple emails to support but never got any response. PYCSD-815. That was three monts ago.
@protean Pymakr is indeed using the zlib.decompress() micropython function for this feature. Normal upload also still works of course, but this way is faster for large files. Let me give you some pointers on how to code it:
The zlib function on the micropython side is documented here. Pymakr is compressing the files before uploading (here using this python file), writing the compressed file to the board with os.write() like always, and then decompressing them right after that (here). It'll definitely make uploading bigger files faster. Just realise that for files under 4k, it's actually slower because the overhead of compressing/decompressing is bigger than the savings of compressing the file.
Great news @Paul-Thornton! Congratulations
I looked at the lora-alliance website put couldn't find the certification reports -- have you made them available? Obviously we would like to use your certification but need:
the certification reports
the git hashes or release number of the code which was actually certified
Also are you planning on getting AU-915 certified, as it's a supported region in your software?
The fixes to the stack and radio drivers that you mention sound great! I had an issue with the LBT in the radio (lack of filtering so that all channels could look busy) and am interested if that was addressed.
Looking forward to the certificates and associated code!
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.
@rskoniec said in New Firmware release v1.18.1.r1:
@mfa2214 xPy module f/w and GPy/Fipy modem f/w are separate, so GPy/Fipy module f/w doesn't contain modem f/w.
Here http://stiny.webd.pl/PYCOM/ on my VPS you have collection of CATM1/NB1 *.dup files.
Many thanks @rskoniec for sharing the files :)
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).