Arduino Nano 33 BLE sense rev2 serial Monitor in zephyr envirnoment

Hi, after uploading a Zephyr project (like the "Hello World" example), I couldn't see the device in the serial monitor. i add the below commend in overlay file also but still nothing is happening i read some document says the uart stack is not enabled in the arduino board after uploading the sample code but after enabling that also same issue i am getting. 

Board: Arduino Nano 33 BLE sense Rev2 (which has nRF52840 microcontroller in it)
Platform : nrF connect sdk in vs code and zephyr environment both i tried

overlay file:

&usbd {
status = "okay";
cdc_acm_uart {
compatible = "zephyr,cdc-acm-uart";
label = "CDC_ACM";
};
};

Need to see the serial monitor in zephyr environment using Arduino Nano33 BLE sense rev 2 board.
Parents
  • Hello Ebi,

    I don't have access to the same HW that you are testing, but based on the schematics that I found here, it looks like there is no UART->USB device on this board. This is something we have on our nRF52840 DKs. The debugger reads all UART messages, and translates this to USB, which is why you can see UART messages on the computer (computers typically don't have UART peripherals).

    The reason I mentioned the nRF52840 dongle in the first place, is that this doesn't have a debugger, so when you build e.g. the hello world sample for our dongle, nrf52840dongle_nrf52840, it has devicetree settings that will forward the console directly to the nRF's own USB peripheral. 

    This doesn't seem to be the case for the arduino nano 33 ble sense board files. I tried adjusting the behavior with the attached application:

    1526.hello_world.zip

    Note the boards\arduino_nano_33_ble_sense.overlay file, where I just copied parts of the nrf52840dongle_nrf52840.dts file. This way it will adapt this behavior without changing the board file in your SDK directly.

    Also, note that I enabled the USB_CDC in the prj.conf.

    Again, I don't have the arduino board to test on, but I tried to build it for the nrf52840dongle_nrf52840 as well, and flashed it, and I can see the "hello world" messages via the USB CDC in a terminal.

    Give it a go, and let me know if it doesn't work.

    Best regards,

    Edvin

Reply
  • Hello Ebi,

    I don't have access to the same HW that you are testing, but based on the schematics that I found here, it looks like there is no UART->USB device on this board. This is something we have on our nRF52840 DKs. The debugger reads all UART messages, and translates this to USB, which is why you can see UART messages on the computer (computers typically don't have UART peripherals).

    The reason I mentioned the nRF52840 dongle in the first place, is that this doesn't have a debugger, so when you build e.g. the hello world sample for our dongle, nrf52840dongle_nrf52840, it has devicetree settings that will forward the console directly to the nRF's own USB peripheral. 

    This doesn't seem to be the case for the arduino nano 33 ble sense board files. I tried adjusting the behavior with the attached application:

    1526.hello_world.zip

    Note the boards\arduino_nano_33_ble_sense.overlay file, where I just copied parts of the nrf52840dongle_nrf52840.dts file. This way it will adapt this behavior without changing the board file in your SDK directly.

    Also, note that I enabled the USB_CDC in the prj.conf.

    Again, I don't have the arduino board to test on, but I tried to build it for the nrf52840dongle_nrf52840 as well, and flashed it, and I can see the "hello world" messages via the USB CDC in a terminal.

    Give it a go, and let me know if it doesn't work.

    Best regards,

    Edvin

Children
No Data
Related