This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Nrf52840 openthread , ble , usbd ( for usb dfu )

so far i am doing good with my nrf52840. i have played with so many examples they all work good. but the problem is when i try to merge them to full fill my need like i was able to combine ble and usbd cdm acm after a week same thing i can do this in esp32 or stm32 within a day.

now the real problem. whoever wrote this sdk has to understand that usb is the key point its the really necessary thing. i mean how can i see debug logs and upload a code. if coding setup takes a week to setup. then its really broken. so i was trying to upload a openthread code its fine working properly now i tried to upload multiprotocol ble and openthread example.

but it doesn't work. it wad fine till i found out that openthread consumes one uart and i can't see logs on uart so really. i got frustrated at this point. i really loved openthread coz i used cli example. and it was good but apart from cli example if i try to merge it will anyother thing it does not work.

i tried to use usb + (ble + openthread) an multiprotocol example given by nrf thread sdk.

i mean i really want use nrf52840 but i am moving to esp32 mesh because itd easy to setup and upload a code. really its very easy i can show my creativity easily there. sorry but if anyone can guide me how can i enable logs on usb and openthread together i will really want to move to nrf52840. but sdk sucks very much.

and that sdk_config.h i mean if i want to use library i will add it why is that another layer to enable any ***. i mean its common sense that i want use library then i will include otherwise i don't .

please help i just want to see logs on usb if you can help i want to switch to nrf52840.

and yeah you should fire your sdk developer. so many developers in our area wants to switch to nrf52840 but they all are using esp32 mesh just because sdk sucks. you guys loosing a lot in this mesh battle.just because google released openthread doesn't mean everyone gonna use it even if it sucks.

please make a working example of usb + mesh + ble and remove that sdk_config.h ***.

please help i am speaking from 50 people team. we writing this after a lots of google search and no luck. we don't want arduino support in nrf52840 we love makefile . 

i am not talking about perticular problem but we want an examples which works in mixed peripherals. industry don't just wants to blink with mesh

thank you.

Parents
  • Hi,

    I'm forwarding response from our Thread developers:

    First of all sorry that you find our SDK disappointing.

    We have recently released nRF5 SDK for Thread and Zigbee in version 3.0.0 that is based on new SDK 15.3, I encourage you to base your application on the improved version.

    Unfortunately removing of sdk_config.h is not possible due to the fact that all modules depend on the single configuration file, but hopefully, we will be able to configure it correctly.

    Before I can help with it, I need to correctly understand your use-case, which I was unable to pull out from your description above. Please provide answers to the questions listed below:

    1. Have you based your code on any of the existing examples in the SDK? If yes, which one?
    2. What do you mean by "debug logs". Are you referring to application logs using "NRF_LOG" or OpenThread core logs or other?
    3. What is the usage of USB? Do you want to use NRF_LOG with USB as a transport simultaneously having OpenThread CLI there, or CLI over UART? Or OpenThread CLI on USB and NRF_LOG with UART as a transport?
    4. What do you mean by "multiprotocol BLE and OpenThread example doesn't work"?
    5. OpenThread does not consume UART by default. Only when it is used as a transport for CLI or NCP. Please check our latest SDK and this code: https://github.com/openthread/openthread/blob/master/examples/platforms/nrf52840/uart.c#L52. If you don't need CLI or NCP you can simply build your application with DISABLE_TRANSPORTS=1 flag: https://github.com/openthread/openthread/blob/master/examples/Makefile-nrf52840#L106

    Best regards,
    Jørgen

  • The Thread and Zigbee SDK is built on regular nRF5 SDK, there is not much that can be done with regards to sdk_config.h and lack of build system as long as the regular SDK is implemented this way.

    If you have any specific issues, we are happy to help you resolve it!

Reply Children
No Data
Related