New target board w/ nRF Connect

RE: New target board w/ nRF Connect

Edvin — Wed, 01 Feb 2023 13:20:01 GMT

Hello,

I am not sure exactly what that build error refers to. Would you mind sending me the current project that you are using, so that I can have a look? (I see that you uploaded a version in a previous reply, but I understand from this reply that you made some progress since then.

Best regards,

Edvin

RE: New target board w/ nRF Connect

Bret Foreman — Fri, 27 Jan 2023 22:16:47 GMT

It turns out that the failure in main.c for api->callback_set was due to the following flag being undefined: CONFIG_UART_ASYNC_API.

I can get that flag to be defined by setting the "Asynchronous UART API" in kconfig. Again, I think this is a bug in the template, since it should have been copied over.

The next error I see is this:

c:\ncs\v2.2.0-rc1\zephyr\soc\arm\nordic_nrf\common\soc_nrf_common.h:218:9: error: static assertion failed: "/soc/uart@40002000 defined without required pin configuration"
  218 |         BUILD_ASSERT((IS_ENABLED(CONFIG_PINCTRL) &&

Which looks like a problem with pin assignments. But this should have been taken care of by the SoC dts file, since the UART pins are in a fixed location.

It looks like the "nRF pin controller driver" is associated with the CONFIG_PINCTRL flag so I enabled that in Kconfig under the nRF UART nrfx drivers section. That didn't change the error.

While looking at the UART0 stuff, I see that there are many other flags that I think should have been copied over from the template - parity, ram buffer size, etc. This looks like another bug in the template copy process.

RE: New target board w/ nRF Connect

Bret Foreman — Fri, 27 Jan 2023 21:21:10 GMT

I'm continuing to play with the app.overlay file to get the project to build. I added the following to app.overlay to turn on uart0:

&uart0 {
	status = "ok";
};

Then I see that uart0 is enabled in the output file zephyr.dts

		uart0: uart@40002000 {
			compatible = "nordic,nrf-uarte";
			reg = < 0x40002000 0x1000 >;
			interrupts = < 0x2 0x1 >;
			status = "ok";
		};

So I'm successfully changing the status to "ok". But I think this is a bug in the UART Bridge template, since it should have been copied over from the template project correctly.

I'm still getting the following warning messages from cmake and I'm not sure if they are important.

CMake Warning at C:/ncs/v2.2.0-rc1/zephyr/CMakeLists.txt:824 (message):
  No SOURCES given to Zephyr library: drivers__console

  Excluding target from build.


CMake Warning at C:/ncs/v2.2.0-rc1/zephyr/CMakeLists.txt:824 (message):
  No SOURCES given to Zephyr library: drivers__gpio

  Excluding target from build.


CMake Warning at C:/ncs/v2.2.0-rc1/zephyr/CMakeLists.txt:1833 (message):
  __ASSERT() statements are globally ENABLED

And now I'm seeing an error in main.c:

c:\Nordic\VS_Code\CM_serial\src\main.c:230:20: error: 'const struct uart_driver_api' has no member named 'callback_set'
  230 |         return (api->callback_set != NULL);

RE: New target board w/ nRF Connect

Bret Foreman — Thu, 26 Jan 2023 18:16:49 GMT

I do have the app.overlay file in my project and it's contents are identical to the one in the samples folder. My project files are attached here:

devzone.nordicsemi.com/.../CM_5F00_serial.zip

When you say "board files", which specific file(s) do you mean and what should I look for? I'm looking at chargmate1.dts (created by the new-board wizard) and I see it includes <nordic/nrf52810_qfaa.dtsi>. That file, in turn includes <nordic/nrf52810.dtsi> which contains this code:

		uart0: uart@40002000 {
			/* uart can be either UART or UARTE, for the user to pick */
			/* compatible = "nordic,nrf-uarte" or "nordic,nrf-uart"; */
			compatible = "nordic,nrf-uarte";
			reg = <0x40002000 0x1000>;
			interrupts = <2 NRF_DEFAULT_IRQ_PRIORITY>;
			status = "disabled";
		};

I see the status is set to "disabled". When I use kconfig to view the uart0 settings, I see this:

Is my build problem because I have not defined the RX, TX, CTS, and RTS pins for the chip? Those pins are defined by the hardware so I'm surprised they don't come pre-set by default. Or do I need to set something else?

RE: New target board w/ nRF Connect

Edvin — Thu, 26 Jan 2023 12:36:40 GMT

Hello,

Could you please look at the sample ncs\nrf\samples\bluetooth\peripheral_uart, and look at the app.overlay file. Do you have that in your application folder?

If you do, I am not sure exactly what is missing, but it is something with your nus uart that isn't configured correctly. Perhaps you are missing the uart0 in your board files. If you are stuck, can you please try to upload the project that you are working on (or at least one that will replicate the issue), and your board file, and I can have a look.

Best regards,

Edvin