Segger alternative for IAR error handler file

[Andrew Waterhouse]

Importing the IAR peripheral beaco example file for S132 into Segger seems to work with the one exception of app_error_handler_iar.c where the assembler reports an error as follows:

Building ‘app_error_handler_iar.c’ from project ‘ble_app_beacon_pca10040_s132’ from solution ‘ble_app_beacon_pca10040_s132’ in configuration ‘nrf52832_xxaa Internal’
  Compiling ‘app_error_handler_iar.c’
    Assembler messages:
    bad instruction `data '
    bad instruction `dc32 16385'
Build failed

The synstax in question starts

DATA                           
1:                             
 DC32 16385                      

Is there a Segger-friendly version of this file or else a quick edit that will overcome this ?

Many thanks !

[Edvin]

Hello,

See how it is done in the SDK examples' ses project files. I have not checked specifically, but I am pretty sure they don't use the app_error_handler_iar.c.

What SDK are you using? Hopefully it is one of the later versions that has SES project files.

Best regards,

Edvin

[Andrew Waterhouse]

Hi Edvin,

thanks heaps for your reply, and sorry, our fault.  Being new to this, and as IAR users without Segger knowledge, we didn't understand exactly where the Segger project and associated source files were  in the  SDK. We had seen a comment on the Nordic web site about Segger now being supported, but couldn't locate a guide to how the example software is structured. THere is extra guidance for Keil  Now we know the project files are in \ses way down in the trees below the example 'main.c' directory.

All good now.

Regards,

Andrew

P.S. during our initial explorations fo the documentation, we are finding that quite few URL links in info centre end up going nowhere, and there are also some 'copy url' buttons that don't copy a coherent url. Is there somewhere to report these ?

[Øyvind]

Hello Andrew,

Happy to hear you found a solution. Edvin is currently on vacation. 

Andrew Waterhouse said:

P.S. during our initial explorations fo the documentation, we are finding that quite few URL links in info centre end up going nowhere, and there are also some 'copy url' buttons that don't copy a coherent url. Is there somewhere to report these ?

 In infocenter you should see a "Documentation feedback" button at the bottom of the page.

Kind regards,
Øyvind