Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W Wiki
  • Project information
    • Project information
    • Activity
    • Members
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Wiki
    • Wiki
  • Activity
Collapse sidebar

To receive notifications about scheduled maintenance, please subscribe to the mailing-list gitlab-operations@sympa.ethz.ch. You can subscribe to the mailing-list at https://sympa.ethz.ch

  • TECTEC
  • Public
  • FlockLabFlockLab
  • Wiki
  • Wiki
  • Man
  • FAQ

FAQ · Changes

Page history
Update FAQ authored Feb 21, 2022 by Reto Da Forno's avatar Reto Da Forno
Show whitespace changes
Inline Side-by-side
Man/FAQ.md
View page @ ca50253c
......@@ -10,7 +10,12 @@ There are two possible reasons why this could happen:
<br />
## 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.
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 and/or 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.
<br />
## Why does the binary patching fail for the platform nRF5?
Make sure to closely follow the instructions in the [HowTo guide](https://gitlab.ethz.ch/tec/public/flocklab/wiki/-/wikis/Man/HowTo#how-to-assign-node-ids). Binary patching most likely fails because you are using a compiler that does not add content to the `.data` section in the ELF file (e.g. SEGGER compiler). You can either place the `FLOCKLAB_NODE_ID` symbol into the read-only section or try a different compiler (e.g. gcc).
<br />
......
Clone repository
  • Man
    • CoojaPlugin
    • Description
    • Examples
    • FAQ
    • GpioAssignmentTargetAdapter
    • HowTo
    • QuickStart
    • Services
    • ServicesOld
    • SetupGuide
    • Targets
    • Tutorials
      • Tutorial1
      • Tutorial2
      • Tutorial3
View All Pages