RE: Unable to build blinky sample for custom nRF52805 board, missed steps?

Dazai — Wed, 27 Nov 2024 22:05:31 GMT

To answer my own questions, since I was able to get this working.

Question 1: are these files named correctly for Zephyr's Hardware Model v2?

Yes, although the filenames do not have the <qualifiers> after the board name, e.g. bc805m.dts instead of bc805m_nrf52805.dts, as outlined in the hardware model transition guide, but that only seems necessary if the board supports more than one SoC. For example, the Nordic nRF52 DK supports the nrf52805, nrf52810, and nrf52832 SoCs.

Question 2: Are the defconfig options listed in Exercise 1 still valid? If not, where can I find the currently supported config options to add to bc805m_defconfig?

I don't know if the options in Exercise 1 are still valid, but I did not have to change anything in bc805m_defconfig to get the blinky sample (without UART!) working.

Question 3: Is there a tutorial for custom boards with Zephyr Hardware Model 2?

I couldn't find an all-in-one tutorial, but I followed the Board Porting Guide, Transition to the current hardware model guide and used zephyr/boards/nordic/nrf52dk/nrf52dk_nrf52805.dts as a reference.

This was the .dts for Fanstel's BC805M module that I used to build the blinky project, in case it helps anyone in the future. Please note that I have a 32.768 kHz oscillator connected to pins 13 and 14 of the BC805M.

/dts-v1/;
#include <nordic/nrf52805_caaa.dtsi>
#include "bc805m-pinctrl.dtsi"

/ {
	model = "Custom Board auto generated by nRF Connect for VS Code";
	compatible = "fanstel,bc805m";

	chosen {
		zephyr,sram = &sram0;
		zephyr,flash = &flash0;
		zephyr,code-partition = &slot0_partition;
	};

	leds {
		compatible = "gpio-leds";
		led0: led_0 {
			gpios = <&gpio0 20 GPIO_ACTIVE_LOW>;
			label = "Red LED";
		};	
	};

	aliases {
		led0 = &led0;
	};
};

&uicr {
	gpio-as-nreset;
};

&gpio0 {
	status = "okay";
};

&gpiote {
	status = "okay";
};

&flash0 {
	partitions {
		compatible = "fixed-partitions";
		#address-cells = <1>;
		#size-cells = <1>;

		boot_partition: partition@0 {
			label = "mcuboot";
			reg = <0x00000000 DT_SIZE_K(48)>;
		};

		slot0_partition: partition@c000 {
			label = "image-0";
			reg = <0x0000c000 DT_SIZE_K(56)>;
		};

		slot1_partition: partition@1a000 {
			label = "image-1";
			reg = <0x0001a000 DT_SIZE_K(56)>;
		};

		storage_partition: partition@28000 {
			label = "storage";
			reg = <0x00028000 DT_SIZE_K(32)>;
		};

	};
};

RE: Unable to build blinky sample for custom nRF52805 board, missed steps?

Dazai — Wed, 27 Nov 2024 18:09:42 GMT

Thank you. I might just need to use SDK < 2.7.0 if I want to follow the intermediate SDK course.

With SDK v2.8.0, do you know if the current nRF Connect Extension in VSCode, specifically adding a custom board, generates the correct files for the Zephyr Hardware Model V2, or should I copy and modify one of the other boards provided by the SDK for my custom board?

RE: Unable to build blinky sample for custom nRF52805 board, missed steps?

Kazi Afroza Sultana — Fri, 22 Nov 2024 14:07:14 GMT

Hello,

The intermidate course doesn't yet support v2.7.0 or above. as outlined here: https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/. So that's probably why the user sees different result. Support for v2.7.0 ( Inc. HWMV2) and above is in progress but not yet ready.

Thanks.

kazi