Hex file update not working on custom board

[joshi]

Hi,

I have successfully detected my custom board (nrf52832 chip  )  with nrf 52dk board and program it with blinky hex file given in SDK 15 version and works.

Now, i update the blinky file with correct pin number  setting on GPIO pin and it works fine with 52 dk board but when i try to program my custom board with 52dk with SWD protocol it is  not working.

I realize that Hex file folder never update with new GPIO setting , only i manage to update the debug and release but if i try to upload that Hex file it dose not work.

well any help is appreciated.

thanks

[email protected]

[Edvin]

Hello,

The hex files in the hex folder inside the example folder will never update. These are precompiled .hex files that are intended to test the examples on the DK without having to install anything.

When you compile a project, the new hex file is found inside the "_build" folder in Keil and SES, or the "output" folder in Segger Embedded Studio (SES).

What compiler do you use? Since you mention "debug" and "release" I assume it is SES.

Referencing the blinky example, when you build this project in SES, the new .hex file is located in:

SDK\examples\peripheral\blinky\Output\Release\Exe\blinky_pca10040.hex

Was this the issue, or did I misunderstand?

[joshi]

Yes I am using ses and my goal is to program my custom board with nRF 52dk which I achieved it but the hex file I use was already precompiled in hex folder updated on 2018.

now I change the code and compile it I found that release folders hex file updated . Now the same code I wrote works on 52dk but dose not work on my customs board. I use hex file which was under release and debug version .

What should I do or is it something I am missing?

my board works well .

[Edvin]

joshi said:

my board works well .

 How do you determine this?

 

joshi said:

Now the same code I wrote works on 52dk but dose not work on my customs board.

 Have you tried debugging? Where does it stop? Try to turn off optimization in your project if it is difficult to debug. What IDE do you use?

Is it the peripheral\blinky example that doesn't work on your custom board?

I need some more information to be able to tell what's going on.

[joshi]

hi

 well i manage to program the board and as u ask me i am using segger embedded studio.

but now BLE is not working.

when i scan on nrf ios app i can see my custom board name but can not connect.

interesting thing is i manage to connect once with my board to nrf app on IOS and blinky BLE program works but after that i can not connect it.

i was reading the last post and i found one has the same issue according to that i turn on the internal LFRC oscillator but when i am checking that my HFCLK ( external 32MH) crystal is working or not but code stuck. i do not have optional or extra crystal on my custom board.

my soldering connections are good i checked for crystal 32 MH high frequency.

well any help is appreciated.

thanks 

joshi 

[Edvin]

What did you program om the custom board? does the same project work on the DK? Is the device advertising? What happens when you try to connect? Have you tried to sniff the connection establishment using nRF Sniffer?