Hardcode unicast address?

[JVKran]

Hi there!

Let's start by explaining why this is necessary. Every device will contain an RFID tag and the RFID tag number has to be equal to the address of the device it's connected to. Hence, every device has to have a pre-programmed unicast address.

I've been looking around in the DevZone and found that it is far from recommended to self provision the nodes. Nevertheless I tried it out. I soon came to the conclusion that this would be practically impossible to do for production.

Then I found the MeshFWPatch tool which can be used for pre-provisioning the devices based on the firmware of one manually provisioned device. Is better doable then doing so in code but still, the security drawbacks make me uncomfortable.

This made me think of alternatives to RFID; NFC. This would solve the problem entirely. Just let a provisioner run and assign addresses and keys to devices and let the provisionee broadcast the address through NFC.

But first, I'd like to know if there are alternatives. Maybe a way to overwrite the received address? Other ideas?

Thanks in advance,

Jochem

[Mttrinh]

Hi,

When a device is added to a network, it is assigned a range of unicast addresses that represents it. This is done by the provisioner. A device's unicast addresses cannot be changed.

Every device will contain an RFID tag and the RFID tag number has to be equal to the address of the device it's connected to.

Could you give me more details/explain to me why you want to do this? 

Just let a provisioner run and assign addresses and keys to devices and let the provisionee broadcast the address through NFC.

Yes, as you say this alternative should solve the problem.

[JVKran]

Hi Mttrinh,

Well, let's say RFID tag 5 broadcasts 0x0005. Then the device that's physically connected to RFID tag 5 should have unicast address 0x0005.

I hope that clears thing up a bit.