What options to comminucate between multiple Arm Cortex chipsets

Hello!

For a concept I need to figure out the best way to handle communication between different Arm Cortex Modules.

The 'host' will be a nRF9160 with the M33, this will be the 'master' device.

It should be able to connect muiltiple M3 chipsets to the master as slaves.

I could use different protocols, but most protocols require fixed addresses and have limited unique addresses.

By using two DIP Rotary coding switches, a user could set the unique ID, in this case I could use i2c.

However it would be easier if each slave device already has a uniquie address, and the master can simply scan the bus to see which slaves are connected.

1-Wire would be an options, as you have 'unlimited' amount of unique addresses avaliable, but 1-wire seems not very supported and outdated?\

To better explain why we cannot set the address of each module fixed to 0,1,2,3... is because I do not know at production/sales which modules will be connected together to a host.

In terms of data transfer, modules should be able to exchange information such as configuration, version, types, command ect.

What would be a good option for this use case?

Thank you,

Roel.

Parents Reply Children
Related