Connect cross power-domain to UART00 on P2 of nRF54L15 DK

[Archiet]

Hi there!

May I know how to have UART00 on P2 like what is shown below as I wanted to have higher speed.

Is it the same as other UART assignments on P0 and P1?

Thanks!

[Edvin]

Hello,

Please see the cross power-domain section of the pin assignment documentation for the nRF54L15.

What pins specifically are you trying to use? Have you used a logic analyzer to see if any of the pins are doing anything? 

Best regards,

Edvin

[Archiet]

Hi there!

I have read the link you shared before. I know it mentions dedicated pins in pin assignment table but I still want to know if I can use any P2 pins for UARTE00. For example, is it possible to use P2.06 to P2.09 for UART with flow control? I understand UART is not mentioned under description and dedicated function of P2.06 but I wanted to know if I can use it by configuration of certain registers.

[Archiet]

Hi there!

My computer is not with at the moment but I will do it.

Meanwhile, you can also build it by copying the sample in the link below but with UARTE00 assigned to P2.06(Rx) and P2.08(Tx) with baud rate 115200. It could be an faster alternative for your debugging. Thanks.

github.com/.../l5_e1_sol

[Archiet]

1581.UART_TEST.zip

Hi there!

Here is the zip folder of my application.

I am using P2.08 and P2.07 as Tx and Rx of UARTE00 with pre set baud rate 115200. In this application, you should be able to use UARTE00 without problem except the actual baud rate is 921600.

Based on this application , you will find Rx is not working if you change Rx from P2.07 to P2.06.

[Edvin]

Thank you for uploading!

Hmm... Yes, I see that it uses 921600 baudrate. 

I also noticed that it says in the top row from here:

https://docs.nordicsemi.com/bundle/ps_nrf54L15/page/uarte.html#d1900e814

That the core frequency scales with the CPU frequency, which happens to be 8 times faster than the frequency of the other UART instance. So there is probably the reason. This however, in my opinion, should be compensated for when setting the baud rate in DeviceTree (your DTS file). 

I will ask our developers if this is the intended behavior. 

By the way, I see that you modified the .dts file directly. While it works, it is not the intended way to change something in devicetree. The intended way is to copy whatever you want to change from the .dts or .dtsi files, create your own file called <board_name>.overlay, and place it in your application folder. (in this case, that would be nrf54l15dk_nrf54l15_cpuapp.overlay), and paste whatever you want to modify into that file. Then, in the overlay file, you can change whatever you want to. I'll attach your modified project, including the .overlay file, for reference. 

8270.UART_TEST.zip

Best regards,

Edvin

[Archiet]

Hi there!

Thanks for the hint regarding overlay file.

On the other hand, are you able to use P2.06 as Rx? If yes, could you share what you have made with me so I could follow? Thanks!

[Edvin]

Sorry. I missed that part.

You can't use P2.06 for UARTE00. You can look in the pin Assignment (Table 3) on this site what pins you can use for UARTE00. On P2, you can use:

P2.00
P2.02
P2.04
P2.05
P2.07
P2.08
P2.09
P2.10

I tested just now, and it worked only replacing this line:

psels = <NRF_PSEL(UART_TX, 2, 8)>, <NRF_PSEL(UART_RX, 2, 6)>;

with e.g.

psels = <NRF_PSEL(UART_TX, 2, 8)>, <NRF_PSEL(UART_RX, 2, 7)>;

Best regards,

Edvin

[Archiet]

Hi there! 

Thanks for the reply.

Is there any chance to use P2.06 on UARTE00? I understand this pin is not dedicated pin on P2 but P1.04 and P1.05 are also not dedicated ones on P1 which they can still be used as UARTE20 in UART sample code. My point is all mentioned  pins are not dedicated ones based on the pin assignment table but why there is freedom on P1 but P2? 

Regarding the baud rate problem, please kindly update to me when there is feedback from the developer

Thanks a lot!

[Edvin]

Archiet said:

Is there any chance to use P2.06 on UARTE00?

That doesn't seem to work.

I will update you when I know more about the baudrate issue.

BR,

Edvin

[Edvin]

The baudrate issue is fixed, and the fix will be included in future versions of NCS.

Best regards,

Edvin

[Archiet]

Nice!

May I know when will the next NCS be available?

[Edvin]

I don't know. If you want roadmap details, you should contact our Regional Sales Manager (RSM) for your area. If you don't have their contact details, please send me a DM here on DevZone, and link to this ticket. 

Best regards,

Edvin