• State Verified Answer
  • Replies 10 replies
  • Subscribers 69 subscribers
  • Views 144 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 336091
Options

NCS 2.7 Create new board wizard

Jason

I want to make a board that's compliant with the new hardware model definitions.  (HWMv2)

When I make a new board with 2.7 using the "create new board" wizard. 

it doesnt appear in the list when I want to add it as a build configuration.

Its not in this dropdown 

also the files generated for the board look a bit strange. See zip attached

For example, the compatible in the dts file isn't the board name, it's "custom-board-name"

when I look at the files, I cannot see what's different to make it HWMv2 compliant
Avilon840.zip 

Parents
  • +1

    Hi Jason,

    Thanks for checking with us. Let me comment on your questions one by one.

    it doesnt appear in the list when I want to add it as a build configuration.

    Its not in this dropdown 

    It is a bit confusing, your second picture does show your custom board "avionv4" on the dropdown list and chosen as default board. Do I missunderstand your problem?

    also the files generated for the board look a bit strange. See zip attached

    For example, the compatible in the dts file isn't the board name, it's "custom-board-name"

    when I look at the files, I cannot see what's different to make it HWMv2 compliant

    The "custom-board-name" in the compatible field sounds likely a placeholder and it should be replaced with your actual board name. I will report to our developer to see if this is intented.

    The main differences for HWMv2 compliance are in the file structure and naming conventions. According to the Board Porting Guide, HWMv2 introduces support for multi-core, multi-arch AMP SoCs, multi-SoC boards, and removes arbitrary uses of Kconfig and folder names.For nRF52840 customer board, which is singal-core, single SoC on board, this is proberly not easy to see dramatic change. You can refer to Migrating to the current hardware model and Zephyr borads folder to learn more about it.

    Best regards,

    Charlie

Reply
  • +1

    Hi Jason,

    Thanks for checking with us. Let me comment on your questions one by one.

    it doesnt appear in the list when I want to add it as a build configuration.

    Its not in this dropdown 

    It is a bit confusing, your second picture does show your custom board "avionv4" on the dropdown list and chosen as default board. Do I missunderstand your problem?

    also the files generated for the board look a bit strange. See zip attached

    For example, the compatible in the dts file isn't the board name, it's "custom-board-name"

    when I look at the files, I cannot see what's different to make it HWMv2 compliant

    The "custom-board-name" in the compatible field sounds likely a placeholder and it should be replaced with your actual board name. I will report to our developer to see if this is intented.

    The main differences for HWMv2 compliance are in the file structure and naming conventions. According to the Board Porting Guide, HWMv2 introduces support for multi-core, multi-arch AMP SoCs, multi-SoC boards, and removes arbitrary uses of Kconfig and folder names.For nRF52840 customer board, which is singal-core, single SoC on board, this is proberly not easy to see dramatic change. You can refer to Migrating to the current hardware model and Zephyr borads folder to learn more about it.

    Best regards,

    Charlie

Children
  • 0 in reply to Charlie

    Hi Charlie, thanks for your reply.

    The screenshot software wouldn't take the snapshot with the dropdown. But I tried to make a board called avilon840 and it didn't appear in the dropdown.

    The boards I've made in the past are all listed. I think it's a bug.

    I will wait for the next NCS version and try again when it's released. I tried to look on devzone for other people having the same issue, but I didn't find any, so I wanted to report what I found in case it was a bug that wasn't logged. (or I had misunderstood!)

    Thanks again.

    Kind regards,

    -Jason

Related