Hello,
I followed steps in below link but block at ETS download
https://github.com/nxp-appcodehub/dm-knx-iot-zephyr-apps-with-ets-support-on-nxp-mcus
details logs show me the reason is can not find the access token. My question is how to get the access token and write into devices. Thanks
Hello, @Shawn_LSQ .
Can you please detail the steps you took to download the ETS configuration?
Typically, the first part of the download consists on establishing the secure channel through SPAKE2+ protocol, which can take up to 30 seconds in the current Zephyr build of RW612. When this happens, you should be able to see a log entry like:
203418 : INF : oc_knx.c 1586 : oc_core_knx_spake_separa... > oc_core_knx_spake_separate_post_handler - startThe process continues after this cryptography calculation part is done and you should be able to see the process continuing on ETS's side.
BR,
Mihai
Hello,
I notice that ETS start PASE request through the ETS messages， Is it my ETS version too new? I use ETS V6.4.1
Hi Mihai,
Thanks your reply! All steps is followed the official NXP steps. I attached the usart logs information for you analysis and don't see you what your mentioned spake.
Hi Mihai，
OTBR also use the FRDM-RW612 and followed bellow link
The uart logs I has been attached. Please check it, Thanks!
Hello, @Shawn_LSQ .
Your ETS version should be fine, I am also using ETS 6.4.1 Build 8718 and I see no issues.
Can you please provide details on the OpenThread Border router that you are using and the configuration for the OTBR device?
Thanks.
Mihai
Usart logs
Hello, @Shawn_LSQ .
Sorry for the long time. Due to priority calls, I can't handle further debugging at the moment, but from a quick overview, I can suggest trying the FreeRTOS OTBR firmware as workaround, due to suspecting that there might be an issue with the Zephyr OTBR.
The RW612 FreeRTOS OTBR build instructions are available here . I know from another thread that you had an issue with building from CLI on Windows. I did a clean test setup and found that during Git install, you need to select a couple of options, please see the pictures below.
This will enable building from command prompt (CMD).
You still need to enable the environment from command line with command:
sdk\repo\mcuxsdk\mcux-env.cmdCan you please try these instructions and come back with feedback?
We will also update the readme with the proper instructions.
BR,
Mihai