helloworld and blinky don't work in RAYTEC-MDBT50Q-CX-40.

[Susumu Shiota]

I am currentry trying to evaluate the RAYTAC-MDBT50Q-CX-40.

Raytac Corporation 勁達國際電子股份有限公司

But sample applications(helloworld, blinky) don't work.

I installed the SDK by following the instructions on the following website.

Installing the nRF Connect SDK

Edit Build configuration following.

Add sample applications.

C:\ncs\v2.9.1\zephyr\samples\basic\blinky

C:\ncs\v2.9.1\zephyr\samples\hello_world

Both apps were built successfully, and merged.hex was generated in the build folder.

I tried to flash merged.hex with Programmer. Both are successful.

 

But, I can no longer connect to the UART and I don't get the "hello world" or other debug messages.

And the LED is still off. It blinks blue when I run DFU so the HW is not broken.

I'm guessing I'll probably need to create an overlay file to connect the LEDs and UARTs, but I'm not sure how to do that.

Could you please tell me what to do?
Thank you so much.

 

[Susumu Shiota]

Thank you for your quick response.

I tried DFU with build/blinky/zephyr/zephyr.hex.
The DFU is successful, but the symptoms are the same as with merge.hex.

I uploaded zephyr.hex and merged.hex for C:\ncs\v2.9.1\zephyr\samples\basic\blinky.

80823.zephyr.hex2475.merged.hex

I haven't done anything related to signing firmware,

I assumed the SDK or some tool would implicitly take care of that, right?

Thank you.

[James168]

I am not sure the bootloader address that is your root cause, but try the following, may be help.

devzone.nordicsemi.com/.../nrf52840-dongle-ble-peripheral_uart-example-sdk-migration-from-2-6-0-to-2-9-0

[James168]

According to raytek's web, you need to disable DCDC, do you modify it?

https://raytaccorp.blogspot.com/2024/07/user-manual-of-mdbt50q-cx-nrf52840-usb.html

[Susumu Shiota]

No, I added this definition to prj.conf and did a prinstone build, but I am getting a build error.

I've been trying to fix the build errors but haven't been successful.

[James168]

I suggest back to the raytek's same NCS version v2.6.0 to try it first, it can avoid NCS version differences.

[Susumu Shiota]

I downgraded SDK.
nRF Connect SDK: v2.9.1 -> v2.6.0

I added c:\nsc\v2.6.0\nrf\samples\bluetooth\peripheral_uart as application,
and add
CONFIG_BOARD_ENABLE_DCDC=n
CONFIG_BOARD_ENABLE_DCDC_HV=n
to proj.conf.(The power remains the same as V3.0.)

I was able to successfully build and confirm that some message was coming from UART.
I also got blinky to work, so I was finally able to start evaluating this dongle.
My mistake was sticking with the latest SDK.
Thank you for some advice!

[Sigurd Hellesvik]

Good job finding this was the DCDC regulator!

Since v2.6.0, we have updated the way DCDC is configured. Now, DTS is used instead of Kconfig.

If you want to do the same in v2.9.1, see the Migration guide to Zephyr v4.0.0.
To disable DCDC, do this in an DTS overlay file:

/* configure REG/REG1 in DC/DC mode */
&reg/reg1 {
    regulator-initial-mode = <NRF5X_REG_MODE_LDO>;
};