Firmware release 1.0.1.b1

[livius]

It looks very promising
all my code work stable in this version - i know not long test but work ok

connected WiPy to computer and send sensor data
[2016-12-22 23:50:12] Recived: [Button1 is Off]
[2016-12-22 23:50:00] Recived: [Button1 is On]
[2016-12-22 23:45:22] Connect: 192.168.1.110[6933]
[2016-12-22 23:44:43] Server started

really simple to accomplish

[rcolistete]

The download link (https://www.pycom.io/support/supportdownloads/, Firmware update) for Linux points to v1.0.0.b2, for Windows points to v1.0.0.b1.

[livius]

@rcolistete
but updater tool download data online

@daniel
When AP+STA - i need it to create "Sensor Gateway"
Now i simulate it and change mode after recived some portion of data
and connect as STA.
After data sended back to AP mode.

what is this?
OSError: [Errno 9] EBADF

[jasonriedy]

The bluetooth.start_scan(x > 0) interface may prove to be an issue for eventual deep sleep support... Not sure if there's a "better" way or not. The example under resolve_adv_data somewhat shows an issue. There's no way to break out of the loop once the scan finishes.

How many advertisements are cached? That should at least be documented.

I'll try to think of a more deterministic API, but I'm overloaded.

[daniel]

@rcolistete it doesn't matter. What's important is that just before flashing the board the updeter tool reports the correct version of the firmware that it's going to program.

[daniel]

@jasonriedy it caches 8 adv messages. I'll add that to the docs. In the future the API will also support registering callbacks.

[jasonriedy]

@daniel Thank you! Unfortunately, some environments see MANY BLE advertisements, so a call-back (possibly filtering by an array of addresses) would be great.

[daniel]

@livius AP+STA is planned for early january after getting the BLE API complete.

That OSError means that you are trying to perform a socket operation on an invalid socket (one that is already closed). Probably you are trying to re-use a socket that was active before you switched between AP and STA mode or viceversa. Close your sockets before switching modes and open them again afterwards.

Cheers,
Daniel

[TravisT]

It also seems the Mac version points to 1.0.0.b1

[sakis]

@TravisT

Most likely the download link was not updated. The only way to be sure is by checking the output of os.uname()

[TravisT]

@sakis

Thanks but I unfortunately I am currently in the land of poor internet (Philippines) and that could be a 45min experiment.

It would be nice to know for sure and resolve any confusion for others as well.

[sakis]

@TravisT

I see. I'll try the macOS update myself and let you know for sure here

[TravisT]

@sakis
Sorry, I was hoping this was a quick link check, not a download and actual test. I appreciate the time.

[sakis]

@TravisT

No problem. I just tested it and it is the right version:

(sysname='LoPy', nodename='LoPy', release='1.0.1.b1', version='v1.8.6-264-gadacebe on 2016-12-22', machine='LoPy with ESP32')

[TravisT]

@sakis
Thank you sir!

[livius]

@daniel
can you add to updater tool option to use files from dir not from internet?
e.g.

1. i can transfer all files to pendrive and go to computer without internet connection and update my board
2. i can change something in source code and do custom make
   and need to flash it to the board
   previously i do this simple by replace files in "updater" folder and run updater tool

[DongYin]

@daniel
I set my Lopy to WLAN.STA mode and connect it with the router, then i ping it's IP address on my computer successfully.
But if there is a way i can ping the IP address of my computer on the Lopy.
If and how i can save any data to the flash?

[livius]

@DongYin said in Firmware release 1.0.1.b1:

If and how i can save any data to the flash?

you can write files to the `\flash' folder without any problem

[Ralph]

@livius, before Daniel replies, let me add that (if you didn't know this already,) you can still update your board manually by placing the bin file in the /sys directory on the board itself using FTP, then rebooting the board. Your idea of making it an option in the updater would probably be better, but until that happens, you can do it this way.

Edit: This works even nicer:
make BOARD=LOPY ESPPORT=/dev/ttyUSB0 flash

[livius]

@Ralph said in Firmware release 1.0.1.b1:

make BOARD=LOPY ESPPORT=/dev/ttyUSB0 flash

what this command flash do?
write e.g. appimg.bin or also partition.bin, bootloader.bin some other things like erase mem...

EDIT

placing the bin file in the /sys directory on the board itself using FTP, then rebooting the board

this does not work for me - but i tested this tommorow only once at night
then maybe i do something wrong
when i do this and restart the board it do not run

i then reflash it with the updater tool once again
and flash board with command line to put my custom source code make
updater.py -f ......
but i must change script of updater.py and remove erase_sytem_mem steap
from some reason this steap time out
a little hint here 'erase_sytem_mem' have one letter typing error should be 'erase_system_mem' ;-)