• State Verified Answer
  • Replies 11 replies
  • Subscribers 69 subscribers
  • Views 2694 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 235284
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Is the SDK ble_app_template project for PC10056e properly working?

Julian

I'm getting started developing an app for nRF52811. have worked with nRF52832 before. 

I was wanting to start my development on top of the basic ble app template project, from the supplied example code in SDK15.3.0 and running the p10056e version (which is simulating the smaller nRF52811 on the nRF52840-DK)

But the app crashes and runs off into the weeds on the call of ble_stack_init() from main

This crashing does not happen when I load up the "native" 10056 version of the project and run it on the same nRF52840-DK, I end up with a board happily sitting there advertising itself to my phone.

I'm using segger embedded studio as my IDE. 

This should be pretty fast to duplicate as it's 100% nordic DK and SDK . 

Full disclosure - I've got hardware made with a real nRF52811 I'm trying to use.. with a modified copy of the 10056e project made following the process as described in the nordic docs - that also fails the same way as the 10056e project on the official DK board. I'm expecting that the crash can be fixed for the emulated project on 52840-DK and that will also apply to my custom hardware.

Parents
  • 0
    Julian said:
    the app crashes and runs off into the weeds

    It shouldn't "run off into the weeds" - it should just end up in the Error Handler.

    With the Debug configuration, you should get some info on the Log output to say what the error is ...

  • 0 in reply to awneil

    there is no debug build for the 10056e for SES... but having a look  there is a debug build for 10056, so I will try to copy that configuration across as a build option for 10056e... I guess it'll be helpful next time something funny happens.. unless debug build isn't in the project for 10056e for a reason? 

    by "run off into the weeds" yeah I could have explained that better - it was getting trapped in the handler.. but since it wasn't compiling a debug build, there wasn't much in the way of useful info I could see when it got there.

    Anyway.. it seems that the full erase has fixed it... I haven't seen that kind of issue before with nRF52832 or any other arm processor.. 

Reply
  • 0 in reply to awneil

    there is no debug build for the 10056e for SES... but having a look  there is a debug build for 10056, so I will try to copy that configuration across as a build option for 10056e... I guess it'll be helpful next time something funny happens.. unless debug build isn't in the project for 10056e for a reason? 

    by "run off into the weeds" yeah I could have explained that better - it was getting trapped in the handler.. but since it wasn't compiling a debug build, there wasn't much in the way of useful info I could see when it got there.

    Anyway.. it seems that the full erase has fixed it... I haven't seen that kind of issue before with nRF52832 or any other arm processor.. 

Children
Related