MYSBootloader 1.3.0-beta.3

[rvweert]

Hey all,

I've compiled the bootloader and was able to install it with Arduino as ISP to a Nano. I couldn't find the lines necessary for the Nano in boards.txt so I created this:

##############################################################

nanomysbootloader.name=Arduino Nano MYSBootloader

nanomysbootloader.upload.tool=avrdude
nanomysbootloader.upload.protocol=arduino

nanomysbootloader.bootloader.tool=avrdude
nanomysbootloader.bootloader.unlock_bits=0x3F
nanomysbootloader.bootloader.lock_bits=0x0F

nanomysbootloader.build.f_cpu=16000000L
nanomysbootloader.build.board=AVR_NANO
nanomysbootloader.build.core=arduino
nanomysbootloader.build.variant=eightanaloginputs

## Arduino Nano w/ ATmega328
## -------------------------
nanomysbootloader.menu.cpu.atmega328=ATmega328

nanomysbootloader.menu.cpu.atmega328.upload.maximum_size=30720
nanomysbootloader.menu.cpu.atmega328.upload.maximum_data_size=2048
nanomysbootloader.menu.cpu.atmega328.upload.speed=115200

nanomysbootloader.menu.cpu.atmega328.bootloader.low_fuses=0xFF
nanomysbootloader.menu.cpu.atmega328.bootloader.high_fuses=0xDA
nanomysbootloader.menu.cpu.atmega328.bootloader.extended_fuses=0xFD
nanomysbootloader.menu.cpu.atmega328.bootloader.file=MySensors/MYSBootloader.hex
nanomysbootloader.menu.cpu.atmega328.build.mcu=atmega328p

Is this correct? Besides, on some devices I cannot program over serial anymore now, only through another ISP. Could that be caused by incorrect settings? Is it possible to recover from that?
The error I'm getting is this one:
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x32

Thanks and happy easter!
Rene

[AffordableTech]

Hi All,

I'm currently upgrading to MySensors 2.0.0 and it would make sense to change over to the MYSBootloader as I upgrade each node. (I'd like to be able to use the remote re-boot command from MYSController).

I have been reading about the MYSBootloader and have some questions . . .

Q1 - My nodes are a mixture of Pro-Micro's, Leonardo's, Mega 2560's and the odd UNO. From what I can see, the MYSbootloader.hex file is for the Mega328p, is this correct, or can the same bootloader be adjusted (fuse settings etc) for others like the Leonardo processor?

Q2 - One post I read seemed to imply that to use the remote reboot feature you needed 'either' the MYSBootloader OR OptiBoot. In the OptiBoot readme, it doesn't mention reboot as a feature, so I am wondering if it really does support reboot - can anyone please confirm?

Many thanks,

Paul

[hek]

Q1) Yes, correct.
Q2) The reboot is handled automatically when new firmware has been downloaded by the library. Note: When using DualOptiboot you must also enable the MY_OTA_FIRMWARE_FEATURE when compiling the sketch to allow updates.

[studzin]

Hi,
Is it possible to add support for rs485 network? In my opinion bootloader which exists need only de-pin management. I'm using hardware serial (rx tx) in nod's.

[slt1]

Can someone please tell me how long it is supposed to take to upload a hex file with MYSBootloader. I am trying out OTA Updates with the latest dev branch of MYSBootloader and it takes almost 2 hours to upload a 64k hex file. Is this normal or should it be a lot quicker?

[gohan]

How far is the node from gateway? It should take much less time actually

[slt1]

@gohan I have tried 2 different nodes in 2 different locations. The one node is about 8m away from the gateway. The other node is around 12m away.

[gohan]

Ok, if you put it like 2 meters away do you notice any difference?

[slt1]

@gohan Seems to be taking the same time at 2 meters apart. Can you tell me how long it should take to do an OTA update? You say "much less time" .. what should it take for a 64k update?

[gohan]

I don't have direct experience (I am waiting for my mini pro to be delivered) but I read other sending in around 10 minutes but I don't know what was the hex file size.
I asked for the distance just to make sure it wasn't related to range issues.

[slt1]

I am getting good range here. I have a repeater node (not using MYSBootloader yet) that is 100m away and works fine and another node 200 to 300m away (hence the repeater at 100m). The far node was dropping some messages but that is not too critical as its only a water tank level sensor. I plan to put in a long range PA+SMA type nrf24L01 on that one. The gateway and repeater already have the long range nrf's. I am now testing OTA to a weather station node that is just outside - around 10m from gateway. And I have a test node on my desk around 8m from the gateway. Both the weather station and the test node on my desk give same results for OTA - around 30min or so for every 20k of hex file.

[gohan]

how long is the sleep time of your nodes?

[slt1]

@gohan The weather station does not sleep - it uses wait() and does so for 5 seconds every loop. The test node first waits for 5 seconds then sleeps for 55 seconds. Both these node seem to update at the same rate. However, it also seems MYSBootloader does the firmware update then launches the sketch code, so the wait / sleep cycle is irrelevant as it first updates the bootloader then runs the sketch

[gohan]

it is relevant because if it is long, the node will start the ota update only when it exits the sleep, so I was just making sure you didn't overlooked that :)

[slt1]

@gohan not overlooked :) All seems to be working - range is good, MYSBootloader and OTA updates work. It just incredibly slow. It seems to do some message updates then pause for maybe 5 seconds or so, then carry on going. So when there are 1000 messages - these 5 sec pauses probably add up to what is making it take hours instead of minutes

[jkandasa]

@slt1 If you are using wait() to repeat some function. I recommend using http://playground.arduino.cc/Code/SimpleTimer, to avoid complete blocking when executing wait().

[slt1]

@jkandasa Thanks for the help, but the problem I am having cannot be in the sketch. The firmware update does gets started after a reboot. So that part is all working fine. Once the firmware is updating then no sketch code runs until it completes. The firmware updating is what is very very slow

[jkandasa]

@slt1 I hope you are also facing this kind of issue: https://github.com/mysensors/MySensorsBootloaderRF24/issues/12

[slt1]

@jkandasa I added some basic shielding around NRF's and now getting the 60Kb hex file transferred in around 15 minutes (was 2 hours!), and a 30Kb hex file transferred in about 7 minutes (prev was about 1 hour). So its a lot better, but still rather slow ! I am not sure if that is a good transfer rate for OTA and if what I am now getting can still be improved. I cannot find any information on what transfer speeds one should expect with OTA updates.
I am also using MyController, but using the 5V / 16Mhz MySBootloader file in development branch. So I am not sure if my issue is same as yours.

[jkandasa]

@slt1 Thanks for the detailed information. If you have enough time would you mind to give a try to https://forum.mysensors.org/topic/4991/mysbootloader-1-3pre2-testing ?

Bootloader link: https://forum.mysensors.org/uploads/files/1475275020003-mysbootloader_v13pre2.zip