Error in configuring UART pins in SDK2.3.0

Hi there,

I have recently switched my complete "Bluetooth Peripheral" Project from the SDK version 1.9.1 to 2.3.0 

I have been facing some of the pin control issue for the UART, as I have observe you have change the way the UART is working and added the pinctrl functionality.

Previously on the 1.9.1, I was using the UART pins shown under.

&uart0 {
	rts-pin = < 0xff >;
	cts-pin = < 0xff >;
};

&uart2 {
	current-speed = <9600>;
	status = "okay";
	tx-pin = <4>;  
	rx-pin = <5>;
	rts-pin = < 0xff >;
	cts-pin = < 0xff >;
	rx-pull-up;
};

I am using this UART2 for communicating with the BMS(Battery management system), but now in the new SDK when using the same pin configuration, I am getting the error 

"d:\v2.3.0\zephyr\include\zephyr\toolchain\gcc.h:78:36: error: static assertion failed: "/soc/peripheral@50000000/uart@b000 defined without required pin configuration""

"d:\v2.3.0\zephyr\include\zephyr\toolchain\gcc.h:78:36: error: static assertion failed: "/soc/peripheral@50000000/uart@b000 has legacy *-pin properties defined although PINCTRL is enabled"

I am using SDK 2.3.0, and my board is the Nordic Thingy53.

Could you please advise on how to resolve this error and properly configure the UART on my SoC?

Regards 
Sachin

Parents
  • Hi Sachin,

    I only started with NCS 2.2.0, so really don't know enough to help you on migrating from NCS 1.9.1. I'd imagine given it's major version change (1.x to 2.x) that there are incompatibilities requiring source code changes (more than just pinctrl). Maybe there is a migration or revision information document somewhere on Nordic's website which highlights the key changes to consider. Searching this forum I see you're not the first to be doing such a migration.

    If you are unable to find an answer to the problem you are currently experiencing, then perhaps best to wait for a Nordic Semi engineer (I'm just a customer like you) to review this post.

    Good luck!

    /Ross

Reply
  • Hi Sachin,

    I only started with NCS 2.2.0, so really don't know enough to help you on migrating from NCS 1.9.1. I'd imagine given it's major version change (1.x to 2.x) that there are incompatibilities requiring source code changes (more than just pinctrl). Maybe there is a migration or revision information document somewhere on Nordic's website which highlights the key changes to consider. Searching this forum I see you're not the first to be doing such a migration.

    If you are unable to find an answer to the problem you are currently experiencing, then perhaps best to wait for a Nordic Semi engineer (I'm just a customer like you) to review this post.

    Good luck!

    /Ross

Children
No Data
Related