nRF Connect Custom Board address range collision warnings

I'm following the tutorial Exercise 1 – Custom board for single-core SoC using ncs v2.9.0 with one slight difference in that I'm using a nRF52DK with nRF52832 because that's what I physically have here. Once I get familiar with the process I'll repeat the exercise with my actual custom board.

The Hello World and BLE UART examples build and work, but I get a bunch of "address range collides" errors (the actual values are identical, so it looks like there is something duplicated)

There is also an problem reported in nrf52832.dtsi

Can you advise?

Parents Reply Children
  • Have you perhaps added multiple board files with the same name (nRF52832 DK) in your environment which results in these collisions?

    Not at all - it's a new custom board, then a new application as per the tutorial. There is just one board in my BOARDROOT directory, which is the custom board I'm creating now.

    I have just the 2 applications - hello_world and peripheral_uart in my application folders, anything else has been deleted.

    Of course there have been previous attempts at creating a board. Maybe some cache files need clearing?

    Oh, there is one other problem reported in myboard_defconfig

    CONFIG_ARM_MPU=y
    The active build context "build" does not use this file

    I've attached the board files

    5305.board.zip

  • If you're having any issues with the procedure I'd recommend referring to the solution to the exercise here and read the comments for each step in code there. https://github.com/NordicDeveloperAcademy/ncs-inter/tree/main/v2.9.0-v2.7.0/l3/l3_e1_sol/boards/nordic/devacademyl3e1 

    By the way that *is* what I have been following. I gave up on the video though as it was recorded using an earlier version of the toolkit and both the code & UI have changed.

    Edit: Ah well... A new day so I deleted all my builds and apps and started again, but used the content of the files from the exercise as a template and it builds now with just minor problems (xxx defined more than once) so there must have been a typo or something I missed or duplicated.

Related