💬 FOTA (Wireless Programming)

cdr

For some reason I can't set the extended fuse to 0x06, it always reverts to 0xFE;

avrdude.exe: verifying ...
avrdude.exe: WARNING: invalid value for unused bits in fuse "efuse", should be set to 1 according to datasheet
This behaviour is deprecated and will result in an error in future version
You probably want to use 0xfe instead of 0x06 (double check with your datasheet first).
avrdude.exe: 1 bytes of efuse verified

Anyone knows why?

scalz

@cdr
The Extended fuse handle the bod level. Only the 3 least significant bits are meaningful. Others are not used.
Be careful: This is true for this fuse, not for all fuses, check datasheet or fuses calculator!
That's why :

0x06 = 00000110
0xFE = 11111110

are doing the same job for the extended fuse. It depends of the tool you use for burning this fuse. Simply, if you get this warning, use the "equivalent".

cdr

Thanks for the explanation, first try didn't work so I suspected the fuses, but turned out to be a voltage issue. :)

starfish133

Is it possible to do OTA over RS485 connections?

hek

Yes, it should be possible. The node doesn't really care which transport that was used.

skywatch

Does OTA work with the NRF24L01+ modules?

Thanks.

mfalkvidd

@skywatch yes.

skywatch

@mfalkvidd

Thanks for the (very) fast reply!

I have arduino in my greenhouse and in winter when it can be constantly wet and cold it is a real pain to take the laptop out to make any changes. This would be a good solution that would allow me and my laptop to stay warm and dry! - - - But how do I stop any one else programming it remotely? Is there some security to stop random programs being installed (it is controlling mains electricity and I need to be sure it is a safe option.

tbowmo

@skywatch

You can use signing to authenticate a firmware upload. Then the attacker first need to get your pre shared keys to reprogram via ota

Anduril

@skywatch just to be complete: using signing as @tbowmo suggested only works with dualoptiboot bootloader.
When using MYSBootloader it will, as far as I know, accept any firmware when booting. To attack the node the attacker would have to reboot your node (power cycle,...) and then send his own firmware. So this is possible, but needs quite a good amount of control of your systems.

tbowmo

@Anduril

@tekka have been looking at making a secure Ota boot loader, if I remember right. I thought that it was released already.

But if an intruder is able to get yo your node to do a reset in order to have the mysbootloader kick in, he could just as well put a new firmware in by attaching a programmer directly to the node.

b0rmann

Is it possible OTA from linux without MYSController?

skywatch

Thank you all for the responses. If someone gets physical access then the game is over anyway. I just want to protect from some bored malicious person getting remote access and causing problems or even a fire.
If it is secure from 'others' hacking it remotely I might give it a try.

Anduril

When initiating a ota firmware update MYSController sends a reboot message to the node. Does anyone knows if that is protected by signing (if enabled)? If so, it would be quite safe excluding the physical access.

chrille

Same question as @b0rmann - is it possible to do OTA from a non-Windows environment (Mac OSX or Linux)? A simple implementation in python or perl, that could talk to the gateway, and do OTA from the command line, would be a really nice to have. I would prefer the dualoptiboot solution, since it'll work with RFM69 nodes as well (at least that's my understanding)

emc2

It may be a silly question, but what is the point of setting the fuses before burning the bootloader (using Dualoptiboot)?

After burning the bootloader fuses are changed to E:06, H:D2, L:E2 anyway as set in board.txt

MysensorsMicro.bootloader.unlock_bits=0x3F
MysensorsMicro.bootloader.lock_bits=0x0F
MysensorsMicro.bootloader.low_fuses=0xE2
MysensorsMicro.bootloader.high_fuses=0xD2
MysensorsMicro.bootloader.extended_fuses=0x06

Should we burn them after to revert to E:06, H:DA, L:E2 ? (and loosing EESAVE which seems bad)

tonnerre33

hello all,

i have installed MYSBootloaderV13pre on my arduino mini pro 3.3V and this work fine.

But i encountered some issues with my jeedom version (the node.js crash) that why i want to replace this bootloader (temporarily) but i can't.

Do you know why when i burn a different bootloader, MYSBootloaderV13pre is still present ?

Thx in advance for your answers

Cliff Karlsson

This might be a stupid question but would it be possible to add a AT25DF512C-SSHN-B to a regular Pro mini by connecting it to a custom PCB like a jModule with a AT25DF512C-SSHN-B ?

scalz

i don't see any problem if you connect correctly the spi bus. it depends what's a jmodule??
in case i did this, perhaps smaller..
https://www.openhardware.io/view/18/OTA-and-Authentication-Evaluation-Board

tlustoch

There is an ambiguity in documetation of MYSBootloader:

On https://www.mysensors.org/download/sensor_api_20#configuration there is a Note: "You can still have OTA FW updates without external flash but it requires the MYSBootloader and disabled MY_OTA_FIRMWARE_FEATURE"
Above on https://www.mysensors.org/about/ota#enabling-ota-in-your-sketch there is written: "To enable OTA in your sketch, you need to add #define MY_OTA_FIRMWARE_FEATURE"
So, in the case of MYSBootloader (no external flash), what is correct (I suppose 2)?

Two additional questions:
Where is located MYSBootloader for MySensors 2.0?
Is it usable with 8MHz internal clock config?

Thanks for answer(s)

💬 FOTA (Wireless Programming)

8

11.7k

11.2k

113.0k