It doesn't run without connect j-link viewer

[Leoni]

Good evening,

I'm having some difficulties with the thingy52. I used it as the basis of development for the project and up to this point without major problems. However, my code runs only have an active connection without j-link. If I disable j-link and reset nrf52, the system just hangs. Anyone would know informs what happens and how to correct?

[Bjørn Kvaale]

Hi,

First off, are you running custom firmware or programming the FW written by Nordic on your thingy:52? If you are programming custom FW, did you follow this link to get the custom FW setup? This link could also be helpful. If done correctly, you should be able to erase the Thingy memory via a JLINK (either external or via the Debug Out port, P19, on the nrf52 DK) & a 10 pin SWD cable, then upload the correct softdevice (v 4.0.2) & lastly program the Thingy:52 with your custom FW application. Does this answer your question?

[Leoni]

Hello Njorn,

I'm sorry, I didn't explain well.

In my a application, basically, I just kept battery service and motion service. To load this application into my custom hardware, I used J-link. After a upload the firmware in mu custom board, the application goes into a constant reset loop. If I open J-link Viewer application and connect as perform a debug, my application start and work normaly without problems or error messagem.

If I close connection in J-link Viewer SW or just unplug J-link connector from the board, and do a power cycle, the system comes to reset loop again.

My problem is similar as "bloobird0" describe in your post (https://devzone.nordicsemi.com/f/nordic-q-a/17829/application-does-not-start-without-debugger-connected/68696#68696). But I don't think that my problem is HW, because, when I try upload a I2C or eddystone examples (Nordic SDK), the system start normaly without using J-link and the SW J-link Viewer.

I belive that are something reseting nRF5 or I miss to do some configuration.

[Bjørn Kvaale]

I'm slightly confused. When you are referring to custom hardware, are you referring to loading a custom application onto the Thingy:52? Or are you using a custom nrf52 board instead? You refer to loading the I2C or eddystone examples in the Nordic SDK, so it seems as if you are using a custom nrf52 board. Unsure whether it is so easy to get sdk examples on the Thingy:52 to work (it could be, I just have not tested this). What example have you based your custom application off of? What changes have you made to your custom application. As you most likely correctly say, it does seem like this is a software & not a hardware problem, as other SDK examples work without any issues.

[jing]

thingy52_sdk enables the DCDC regulator inside ble_stack_init() of m_ble.c

Comment out sd_power_dcdc_mode_set(NRF_POWER_DCDC_ENABLE) if your custom board doesn't have the required external LC filter to use the DCDC regulator.

[Leoni]

Hello Bjorn,

About custom hardware, we developed a custom nrf52 board based in thingy52 hardware. I agree with you when you say that it does seem like this is a software problem, because, if I do a simples blink application and upload in my custom board, this problem doesn't happens.

About what example I based to create my applicantion, I use the thingy52 FW on github (https://github.com/NordicSemiconductor/Nordic-Thingy52-FW). I removed all BLE services and hardware function access (like led functions, buttons, other sensores) that are not related of MPU9250 sensor and  battery monitoring service.