Application suddenly stopped building

RE: Application suddenly stopped building

matangk — Fri, 18 Mar 2022 13:22:33 GMT

(1) Thanks, I will keep that in mind.

nrfjprog --eraseall

So.. the simple "Erase and flash" option doesn't completely delete the flash?

(2) To complete the picture - I tried to program my standalone NRF52805 with my OLD PC. I started with programming the peripheral_uart sample which still kept hanging on bt_enable.

(3) I then programmed the peripheral_lbs (led-button service). This worked. I was able to connect to the module via my phone and run the app.

(4) Afterwards, I reprogrammed the NRF52805 module with the same peripheral_uart app. This time it was working fine!

(5) Afterwards, all my previously failing apps started to work.

(6) I hope this doesn't happen again. It was very time consuming, but I appreciate the assistance and advice.

Cheers

RE: Application suddenly stopped building

Sigurd — Fri, 18 Mar 2022 12:41:31 GMT

[quote user="matangk"]Is it possible that there is some non-volatile area that got corrupted and writing the btl app fixed it??[/quote]

Difficult to say for sure, but that might be the explanation. If you run into this again in the future, try to do a full erase of the flash:

nrfjprog --eraseall

RE: Application suddenly stopped building

matangk — Thu, 17 Mar 2022 15:40:39 GMT

Well. I just had a very confusing half hour. I looked for another sample with BT that might compile on nrf52805. I found the peripheral button-led. I built it for nrf52dk_nrf52805, ant programmed the DK.

This is on my old PC where nothing was working before. Voilla. The btl sample app works.

"Huh" - I thought and now again tried to build a fresh sample of peripheral uart, on sdk 1.9.1. I programmed my NRF52-DK AND IT WORKS.

HOW CAN THAT BE?? I didn't do anything different.

Not only that, now ALL THE FAILED SAMPLES now work fine.

Is it possible that there is some non-volatile area that got corrupted and writing the btl app fixed it??

I'll be happy to know what's going on as two work days were just put into this.T

hanks

RE: Application suddenly stopped building

Sigurd — Thu, 17 Mar 2022 13:28:03 GMT

[quote user="matangk"] Did you use my code snippet [/quote]

No. But I just tested your code(main.c), it advertised, I was able to connect. But I got a error when I tried sending data from the phone to the nRF52 with your code.

Do you have LF crystal on this module? If not, try setting

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

I will check out the sample you attached.

RE: Application suddenly stopped building

matangk — Thu, 17 Mar 2022 07:54:55 GMT

Update (3), 17/3 9:00:

After having the nrf52805 module programming and advertizing the NUS last night I went ahead this morning to program it with my OLD PC

(1) My module, programmed by the OLD PC with the exact same code as in the NEW PC hangs on bt_enable

(2) What's worse - I took it to the NEW PC and programmed it again with the code that was working, and now the module, programmed by the NEW PC won't advertise the NUS. (in debugger hangs on bt_enable)

(3) On the NEW PC, my NRF52-DK programs fine when the app is built with nrf52dk_nrf52832 and I can run the peripheral uart app fine with proj_minimal configuration

(4) Another application, WITHOUT BT, builds on my OLD PC and runs fine with nrf52dk_nrf52805 build

I'm very, very confused.

When retracing my steps all I can come up with are a few things:

(a) I was dabbing with those two following options

CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=y/n

CONFIG_BOARD_ENABLE_DCDC=y/n

Back and forth out of hardware considerations. I'm wondering if programming with my OLD PC could have put the chips in some lockdown state or caused something to burn (my module and the 52dk are equipped with inductors for the DCDC converter). This doesn't explain how the same app works with nrf52832 config, though.

(b) When looking into nrf52dk_nrf52805_defconfig I see the following line there:

# Bluetooth not enabled by default on nRF52805 due to RAM limitations when
# running the default set of kernel tests.

is there anything special I should do to enable BT?

This is a complete nightmare. I suspect having several SDK versions (I have 1.8.0, 1.9.0, 1.9.1 on my OLD PC) is a bad idea. but this issue needs to be solved. I'm attaching the culprit app here.

Thanks ahead, any help will be welcome.

devzone.nordicsemi.com/.../peripheral_5F00_uart_5F00_191_5F00_52805.zip

RE: Application suddenly stopped building

matangk — Wed, 16 Mar 2022 21:08:05 GMT

Update (2), 16/3 22:00:

Well, in continue to my fails to emulate NRF52805 on my NRF52-DK, I went ahead and programmed an actual NRF52805 - and it works.

I'm quite baffled with what's going on and would like some help:

1. my nrf52-DK programs with a minimal and stripped down BT-NUS example, as an nrf52832

2. when I build it for nrf52805 and burn it on my nrf52-dk the bt_enable seems to hang

3. when I actually burn this on an nrf52805 module - bt_enable seems to work and my program runs. I can connect to the NUS from my phone.

4. Mind, this is on a newly installed NRF-SDK on a new PC.

What's going on?

There must be something that I'm missing. I refuse to think that with these symptoms I somehow damaged my NRF52-DK

Thanks ahead

RE: Application suddenly stopped building

matangk — Wed, 16 Mar 2022 20:07:39 GMT

Update (1), 16/3 21:00:

I tested this again on a new PC. Installed nrf connect desktop from scratch and sdk 1.9.1. I import the sample project and remove the relevant code. The blue NUS never starts and I cannot see it with my Android phone.

I must be missing something.

Can you please share your project that runs fine?

RE: Application suddenly stopped building

matangk — Wed, 16 Mar 2022 16:17:28 GMT

Interesting. Did you use my code snippet without the extra 52832 hardware? If not, can you please upload the project? What am I doing wrong. I tried with the same sdk, no success. Could my dk have gotten damaged? It shouldn't I think

RE: Application suddenly stopped building

Sigurd — Wed, 16 Mar 2022 14:50:28 GMT

[quote user="matangk"]This issue should be super simple to recreate if you have an NRF52-dk next to you.[/quote]

I tested the sample using SDK v1.9.1.

Used nRF Connect for VS Code with this configuration

And the sample worked fine here. Was able to connect and send some data using the NUS service

RE: Application suddenly stopped building

matangk — Wed, 16 Mar 2022 10:20:27 GMT

Yes, of course. Otherwise SRAM overflows.

This issue should be super simple to recreate if you have an NRF52-dk next to you.

One thing that upset me is that NRF52805 used to be listed in the supported devices. Now it's listed under "Nordic devices". The NRF52810 though is still listed as supported, and I'm having the same issues with emulating it.

RE: Application suddenly stopped building

Sigurd — Wed, 16 Mar 2022 10:01:43 GMT

Hi,

Did you build the sample using the prj_minimal.conf ?

http://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/nrf/samples/bluetooth/peripheral_uart/README.html#minimal-sample-variant