@@ -7,6 +7,10 @@ There are two possible reasons why this could happen:
- Binary patching failed for some reason, e.g. because the uploaded execute is not an elf file or the symbol `FLOCKLAB_NODE_ID` does not exist in the binary.
- You are trying to read the node ID from the EEPROM on the Tmote. The ID stored in the EEPROM can be overwritten by the users and is therefore not reliable. If you still want to use this method, you need to do the mapping by yourself. You could first run a test to read the current IDs, do the mapping and then run another test to write the desired node IDs (e.g. [Contiki](http://contiki.sourceforge.net/docs/2.6/a01425_source.html) provides a function to write the EEPROM).
## Why do I not get any serial output on the platform nRF5?
First, make sure that the GPIO configuration in your code matches the [FlockLab specifiction](https://gitlab.ethz.ch/tec/public/flocklab/wiki/-/wikis/Man/GpioAssignmentTargetAdapter). If the GPIO mapping is correct, then you need to verify that your code is properly flashed to the target device by running a simple blinky test application (check the output of the GPIO tracing). This ensures that there was no issue with the binary file conversion / upload to the target. Also, most users forget to include a bootloader / MBR in their image files. Note that FlockLab programs the nRF5 via SWD and a mass erase is performed before your code is flashed. This means you either need to make sure your code starts at address 0x0 or include the bootloader that would normally (= when you flash the dongle via USB) jump to the application code.