UART Configuration on Ezurio DVK

[MontanaEE]

I'm working with a DVK that has an nrF52840 with a Sierra Wireless HL7800 modem.  The modem is connected physically to UART1 while the UART0 is used for the following as shown in the dts:

zephyr,console = &uart0;

zephyr,shell-uart = &uart0;

zephyr,uart-mcumgr = &uart0;

zephyr,bt-mon-uart = &uart0;

I need to repurpose UART0 to send and receive hex commands on an HMI.  It was suggested by Ezurio tech support that I push the shell and console to the nrf USB to free up UART0. Is it just changing these lines in the dts file?  How do I do that?

 

[Edvin]

So the only difference is that you want to disable the flow control? Try something like this:

	&uart0 {
		compatible = "nordic,nrf-uarte";
		status = "okay";
		baudrate = <115200>;
		pinctrl-0 = <&uart0_default>;
		pinctrl-1 = <&uart0_sleep>;
		pinctrl-names = "default", "sleep";
		/delete-property/ hw-flow-control;
		
	};
};

Best regards,

Edvin

[MontanaEE]

When I've tried that before I get the warning "Unknown property" as you can see from the screen shot. I thought that meant I was using the wrong statement.  I went through the yaml files to see what RTS and CTS were being called, but that didn't seem to help.  Is that warning of "Unknown property" a problem?

Also, in regards to creating a custom node for my HMI, is there a tutorial on that? How do I get that to appear in the overlay?  Right now it does not have a node assigned.  There is an option to add a node, but I still would have to create a node for my HMI right?  It just gives me a list of predefined nodes for other devices.

[Edvin]

MontanaEE said:

Is that warning of "Unknown property" a problem?

I tend to ignore this "Problems" tab, because it gives a lot of false warnings. Does the build log say anything about being an unknown property if you use the /delete-property/ line?

MontanaEE said:

Also, in regards to creating a custom node for my HMI, is there a tutorial on that?

That may be possible, but it is not something I have tested before. I suspect it is part of writing your own zephyr driver for the HMI device. You can try to follow the DevAcademy nRF Connect SDK Intermediate course, and the lesson on writing your own drivers:

Best regards,

Edvin