To enable more flexbility in the arena layout, userspace names (e.g. casu-003) should be decoupled from physical hardware (e.g. tcp://bbg-001:3555 i2c pin 3). However, because the firmware needs to know both the userspace name and the physical hardware address, .fbc files need to be generated for particular deployment scenarios and deployed together with user code.
To enable more flexbility in the arena layout, userspace names (e.g. casu-003) should be decoupled from physical hardware (e.g. tcp://bbg-001:3555 i2c pin 3). However, because the firmware needs to know both the userspace name and the physical hardware address, .fbc files need to be generated for particular deployment scenarios and deployed together with user code.
This will require: