When a lowcar device is flashed using the runtime flash script, there is an option to set a test UID instead of a random UID. The test UID is 0x0123456789ABCDEF. However, it seems that when connecting to dev_handler or printing on net_handler_cli shows the UID to be 0x23456789ABCDEF0D. There could be an error on how the UID is being flashed or the way dev_handler could be processing the acknowledgment from the device.
Steps to reproduce:
1) Flash a lowcar device using "runtime flash -t KoalaBear"
2) Start up shared memory and dev_handler
3) Connect flashed lowcar device to dev_handler and observe UID of connected device
4) Print in shared memory to also observe the UID
When a lowcar device is flashed using the runtime flash script, there is an option to set a test UID instead of a random UID. The test UID is 0x0123456789ABCDEF. However, it seems that when connecting to dev_handler or printing on net_handler_cli shows the UID to be 0x23456789ABCDEF0D. There could be an error on how the UID is being flashed or the way dev_handler could be processing the acknowledgment from the device.
Steps to reproduce: 1) Flash a lowcar device using "runtime flash -t KoalaBear" 2) Start up shared memory and dev_handler 3) Connect flashed lowcar device to dev_handler and observe UID of connected device 4) Print in shared memory to also observe the UID