Crash enabling softdevice on Fanstel USB840F (based on nrf52840)

RE: Crash enabling softdevice on Fanstel USB840F (based on nrf52840)

awneil — Fri, 07 Dec 2018 11:25:08 GMT

[quote userid="24816" url="~/f/nordic-q-a/41311/crash-enabling-softdevice-on-fanstel-usb840f-based-on-nrf52840/160697"]Ok, thank you!! Bluetooth works great now![/quote]

Excellent - so please Verify the Answer:

This will show other readers that the problem has been resolved.

[quote userid="24816" url="~/f/nordic-q-a/41311/crash-enabling-softdevice-on-fanstel-usb840f-based-on-nrf52840/160697"]I have other two questions:[/quote]

So start new threads for them!

It helps to keep to 1 question per thread to avoid confusion, and so that it can be seen when the question has been answered!

RE: Crash enabling softdevice on Fanstel USB840F (based on nrf52840)

gio — Fri, 07 Dec 2018 10:05:38 GMT

Ok, thank you!! Bluetooth works great now!

I have other two questions:

1. When I attach it to a powerbank, the powerbank turns the power off after some time (let's say a minute) due to its low power consumption. How can I prevent this from happening?

Unfortunately two leds+always on bluetooth RX seem to not provide sufficient load.

Is there an alternative load that I can enable periodically using gpio, to prevent powerbank from cutting power?

Do you know alternative solutions to this issue?

2. I see that it can be flashed via USB too, withouth even opening the enclosure. Can you confirm? Can this be done with custom made firmware withouth the need for any signature, or it can only be done with firmware provided by Fanstel?

RE: Crash enabling softdevice on Fanstel USB840F (based on nrf52840)

LeoChen — Fri, 07 Dec 2018 01:06:31 GMT

The USB840F dongle doesn't included 32K crystal.

Therefore, Please change the clock setting to internal RC.

nrf_clock_lf_cfg_t const clock_lf_cfg =
{
/*
.source = NRF_SDH_CLOCK_LF_SRC,
.rc_ctiv = NRF_SDH_CLOCK_LF_RC_CTIV,
.rc_temp_ctiv = NRF_SDH_CLOCK_LF_RC_TEMP_CTIV,
.accuracy = NRF_SDH_CLOCK_LF_ACCURACY
*/

.source = 0,
.rc_ctiv = 16,
.rc_temp_ctiv = 2,
.accuracy = 7

};

RE: Crash enabling softdevice on Fanstel USB840F (based on nrf52840)

awneil — Thu, 06 Dec 2018 20:33:01 GMT

[quote userid="24816" url="~/f/nordic-q-a/41311/crash-enabling-softdevice-on-fanstel-usb840f-based-on-nrf52840/160637"]

The function doesn't even return. It hangs indefinitely!

[/quote]

I see.

Is it ending up in the Hard Fault handler?

Have you asked Fanstel if they have an example for their module? Or if there's anything "special" that you need to do differently from the Nordic boards?

RE: Crash enabling softdevice on Fanstel USB840F (based on nrf52840)

gio — Thu, 06 Dec 2018 20:26:34 GMT

[quote userid="6462" url="~/f/nordic-q-a/41311/crash-enabling-softdevice-on-fanstel-usb840f-based-on-nrf52840/160636"]The whole point of having ret_code is that it tells you what the error was![/quote]

The function doesn't even return. It hangs indefinitely!

[quote userid="6462" url="~/f/nordic-q-a/41311/crash-enabling-softdevice-on-fanstel-usb840f-based-on-nrf52840/160636"]Is that loading the exact same binary, or are you building different configurations?[/quote]

I built using segger embedded studio using pca10056 configuration for nrd52840DK and pca10059 configuration for nrf52840dongle.

Unfortunately configuration for Fansterl UDB840F is not included in nrf52DK, thus I tried flashing the two hex files for pca10056 and pca10059 to USB840F, but it doesn't work.

RE: Crash enabling softdevice on Fanstel USB840F (based on nrf52840)

awneil — Thu, 06 Dec 2018 19:57:23 GMT

[quote userid="24816" url="~/f/nordic-q-a/41311/crash-enabling-softdevice-on-fanstel-usb840f-based-on-nrf52840"]

ret_code = sd_softdevice_enable(&clock_lf_cfg, app_error_fault_handler);

[/quote]

So what value of ret_code are you getting?

The whole point of having ret_code is that it tells you what the error was!

[quote userid="24816" url="~/f/nordic-q-a/41311/crash-enabling-softdevice-on-fanstel-usb840f-based-on-nrf52840"]Running the same examples on nrf52840 Dongle and nrf52840DK works well[/quote]

Is that loading the exact same binary, or are you building different configurations?