Read Thread MAC address

RE: Read Thread MAC address

Charlie — Thu, 26 Aug 2021 10:40:18 GMT

Hi Rohit,

The guidance you mentioned is too old for nRF5_SDK_for_Thread_and_Zigbee_v4.1.0. You can follow the following steps to disable the OT CLI library and use UART0 for your application:

Delete "libopenthread-cli-ftd.a" and replace "libopenthread-nrf52840-transport.a" with "libopenthread-nrf52840-transport-none.a"
Modify sdk_config.h to enable UART0, see the simple_coap_client_uart0 sample.
Add Drivers and Libraries to the project, you need to add:
nRF_Drivers:
integration\nrfx\legacy\nrf_drv_uart.c
modules\nrfx\drivers\src\nrfx_uart.c
nRF_Libraries
components\libraries\fifo\app_fifo.c
components\libraries\uart\app_uart_fifo.c
components\libraries\uart\retarget.c
Add header files path:

Delete "UART_ENABLED=0" in Preprocessor Definitions, add more include directories to User Include Directories:
../../../../../../components/libraries/fifo
../../../../../../components/libraries/uart
../../../../../../integration/nrfx/legacy
../../../../../../modules/nrfx/drivers/include
Use UART0 in your application code, the simple_coap_client_uart0 sample print "Hello World!" at the beginning of main.c.

devzone.nordicsemi.com/.../simple_5F00_coap_5F00_client_5F00_uart0.zip

Best regards,

Charlie

RE: Read Thread MAC address

Rohit Rajapure — Thu, 26 Aug 2021 09:10:36 GMT

Hi Charlie,

Update from my side.

With reference to above steps. I found makefile and removed the cli lib,

$(SDK_ROOT)/external/openthread/lib/gcc/libopenthread-cli-mtd.a \

but I am still getting multiple definitions of UART.

error -

../../../../../../../../external/openthread/lib/nrf52840/gcc/libopenthread-nrf52840-transport.a(uart.c.o): in function `UARTE0_UART0_IRQHandler':multiple definition of `UARTE0_UART0_IRQHandler'; Output/thread_cli_mtd_uart_pca10056 Release/Obj/nrfx_uart.o:D:\Project\Eurotronics\Thread_Radiator\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\modules\nrfx\drivers\src/nrfx_uart.c:649: first defined here

can you please help me how to make UART0 free for my custom requirement.

Thanks and Regards

Rohit R

RE: Read Thread MAC address

Rohit Rajapure — Thu, 26 Aug 2021 04:16:17 GMT

Hi Charlie,

Thank you so much for the feedback,

In above link I saw that we can disable the CLI library and use UART0 for custom. But I am not understanding his steps and unable to find Make file in segger.

Can you please help me to identify the Makefile in segger and understand his steps.

Below is steps suggested by engineer,

If you do not want to use CLI, simply do not initialize it. I cannot post files via comment section, but the steps are pretty simple, so you can reproduce them. I have modified the OpenThread CLI form Thread SDK, as it's the simplest, but you can apply these steps to any Thread example:

Add OT UART header : #include <openthread/platform/uart.h>
Replace otCliUartInit(p_instance); with otPlatUartEnable(); to enable UART0 (CLI does it by itself).
Create receive handler, for example:

void otPlatUartReceived(const uint8_t *aBuf, uint16_t aBufLength)
{
    (void)aBuf;
    (void)aBufLength;
    bsp_board_led_invert(BSP_BOARD_LED_3);
}

In a Makefile, remove the line that linked CLI library: $(SDK_ROOT)/external/openthread/lib/gcc/libopenthread-cli-ftd.a \

After reproducing these steps you will be able to control UART0 manually from the application.

Thanks and Regards

Rohit R

RE: Read Thread MAC address

Charlie — Tue, 24 Aug 2021 21:04:25 GMT

Hi Rohit,

There is no better solution for your current situation. As discussed on this ticket: Adding UARTE1 to CLI OpenThread Example - Nordic Q&A - Nordic DevZone - Nordic DevZone (nordicsemi.com).

You need to use UARTE1 and assign non-conflict pins for your custom UART communication.

Best regards,

Charlie

RE: Read Thread MAC address

Rohit Rajapure — Tue, 24 Aug 2021 03:47:20 GMT

Hi Charlie,

[quote userid="93921" url="~/f/nordic-q-a/78426/read-thread-mac-address/326216#326216"]Sorry for the late reply, I just come back from vacation.[/quote]

- Okay, not a problem.

[quote userid="93921" url="~/f/nordic-q-a/78426/read-thread-mac-address/326216#326216"] It would be better if you can create a new ticket for your new question next time so that my colleague can give you a timely reply.[/quote]

- It was urgent so asked here only. Next time if any other problem I will make new ticket.

[quote userid="93921" url="~/f/nordic-q-a/78426/read-thread-mac-address/326216#326216"]The Thread examples use prebuild OT library for certification and compatibility reasons, uart0 is used by default. You need to set up UARTE1 for your own usage. You can find many discussions on how to UARTE1 by searching Devzone.-[/quote]

- Yes, I know the libraries are prebuild. But as my hardware is ready with uart pin as P0.6 and P0.8. My all UART functions are written using UART0 and are proven. So i don't want to switch to UARTE1. I want to use as it is with UART0. So it must to disable this library and use my custom requirement.

I request kindly guide me to disable this uart library and use for custom requirement.

Thanks and Regards

Rohit R

RE: Read Thread MAC address

Charlie — Mon, 23 Aug 2021 13:57:36 GMT

Hi Rohit,

Sorry for the late reply, I just come back from vacation. It would be better if you can create a new ticket for your new question next time so that my colleague can give you a timely reply.

The Thread examples use prebuild OT library for certification and compatibility reasons, uart0 is used by default. You need to set up UARTE1 for your own usage. You can find many discussions on how to UARTE1 by searching Devzone.-

Best regards,

Charlie

RE: Read Thread MAC address

Rohit Rajapure — Mon, 23 Aug 2021 03:30:42 GMT

Hi,

Any update to my query.

I am waiting for your feedback.

Thanks and Regards

Rohit R

RE: Read Thread MAC address

Rohit Rajapure — Thu, 19 Aug 2021 05:08:13 GMT

Hi Charlie,

I have built my project which uses UART0 for my communication with other device.

But when I include UART related files and my command it gave me below error,

1> C:\bamboo\xml-data\build-dir\KNG-OL54-BOLO\sdk\sdk\nrf5\external\openthread\project\nrf52840\plat_nrf52840\uart\armgcc/../../../../openthread/examples/platforms/nrf528xx/src/transport/uart.c:287: multiple definition of `UARTE0_UART0_IRQHandler'; Output/Radiator_thd_v0.9.0 Release/Obj/nrfx_uart.o:D:\Project\Eurotronics\Thread_Radiator\nRF5_SDK_for_Thread_and_Zigbee_v4.1.0_32ce5f8\modules\nrfx\drivers\src/nrfx_uart.c:649: first defined here
Build failed

When I searched about error, I found this is because of CLI library.

Can you please help how to disable this CLI library in CoAP server/ cli code and make UART available for my custom development.

my custom hardware uses P0.6 and P0.8 as Tx/Rx pins.

Please help as early as possible. It is urgent to test my custom boards so requesting query in current ticket only.

Thanks for understanding.

Please find the attached project for reference.

devzone.nordicsemi.com/.../Radiator_5F00_thd_5F00_v0.9.0.zip

Regards,

Rohit R

RE: Read Thread MAC address

Rohit Rajapure — Fri, 13 Aug 2021 03:25:37 GMT

Hi Charlie,

Thank you so much for the response.

I will use this as i configured get address.

In case of any difficulties in further development I will get back to you.

Thanks and Regards

Rohit R

RE: Read Thread MAC address

Charlie — Wed, 11 Aug 2021 13:58:07 GMT

[quote user="Rohit Rajapure"]I need IEEE EUI-64 address (MAC address) for white listing our node with customer Gateway. So let us know the procedure to get address. This is mandatory to integrate our device and dev board with customer gateway and test our system.[/quote]

The codes you shared have no problem. OpenThread CLI command eui64 has the same implemntation.

RE: Read Thread MAC address

Rohit Rajapure — Wed, 11 Aug 2021 11:42:36 GMT

Hi Charlie,

[quote userid="93921" url="~/f/nordic-q-a/78426/read-thread-mac-address/324391#324391"]2) You have to think about the reason why you need a Thread note MAC address, normally it is used for device identification. Thread use IEEE EUI-64 and otLinkGetFactoryAssignedIeeeEui64() is the correct function. EUI-64 is MSB to LSB according to Use of EUI-64 for New Designs.[/quote][quote userid="93921" url="~/f/nordic-q-a/78426/read-thread-mac-address/324391#324391"]3) I do not think you should bother how to get MAC address for your development. It is covered by high-level commissioning process.[/quote]

- I need IEEE EUI-64 address (MAC address) for white listing our node with customer Gateway. So let us know the procedure to get address. This is mandatory to integrate our device and dev board with customer gateway and test our system.

[quote userid="93921" url="~/f/nordic-q-a/78426/read-thread-mac-address/324391#324391"]If you just start your development on Thread protocol, I strongly suggest you switch to NCS. nRF5_SDK_for_Thread_and_Zigbee is currently in the maintenance stage, there will be no further major update.[/quote]

- As we are already begun our development on SDK for thread_Zigbee 4.1 and we are close to completion so it difficult at this time to switch or upgrade to latest SDK (NCS).

Thanks and Regards

Rohit R

RE: Read Thread MAC address

Charlie — Wed, 11 Aug 2021 08:15:26 GMT

Hi Rohit,

1) I am still not clear what's your functions of Gateway, does the application topology look like PC/Mobile Phone <-> Border router(Gateway) <-> Thread mesh nodes? so you can control the Thread node from an external network? If this is what you want, I would suggest you think about Metter/Homkit application protocol or SDK, because Thread is a network layer protocol. It is not very easy to use it directly for this kind of application.

2) You have to think about the reason why you need a Thread note MAC address, normally it is used for device identification. Thread use IEEE EUI-64 and otLinkGetFactoryAssignedIeeeEui64() is the correct function. EUI-64 is MSB to LSB according to Use of EUI-64 for New Designs.

3) I do not think you should bother how to get MAC address for your development. It is covered by high-level commissioning process.

If you just start your development on Thread protocol, I strongly suggest you switch to NCS. nRF5_SDK_for_Thread_and_Zigbee is currently in the maintenance stage, there will be no further major update.

Best regards,

Charlie