Search Results
Search results 1-9 of 9.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
Nino, Veit, Many thanks for the sound advice. The clarification of which linkers use which formats was the info I needed I guess it begs the question: Which linker should I choose for a Nordic 51822 application? Rob
-
What is the current best practice? I am using Segger Embedded Studio v4.12 for programming a Nordic 51822 application (SDK 12.3) and need to configure the section placement file Information on the Segger wiki discusses use of linker scripts (*.icf) wiki.segger.com/Porting_from_GCC_to_SEGGER_Linker But documentation from Nordic and in the Segger Manual suggest use of flash_placement.xml files studio.segger.com/index.htm?ht…placement_file_format.htm Advice from Nordic for importing a Keil project …
-
Removing the lines from thumb_crt0.s made no difference to printf However I could no longer find the HELPER lines in the disassembler window showing that the modified files had been compiled Back to the drawing board! Rob
-
Thankyou for this suggestion; I hit a snag. _DoInit is a called through macro INIT() in Segger_RTT.c. However in my configuration INIT() is not called; I cannot add breakpoints in the INIT() block. Not sure why. RTT is enabled in debug options. And indeed printf directs to the debug terminal When I look at the assembler code for start() - attached file I see the following order of execution: Cortex_M_Startup.s SEGGER_THUMB_Startup.s system_nrf51422.c This seems like a candidate for the problem -…
-
Jev Belated thanks for the sound advice. Unfortunately it did not fix it. I found a similar suggestion from Nordic: devzone.nordicsemi.com/f/nordi…default_mode-blocking-app I get the same problem when I include the lines below in in sdk_config.h. The printf statement prevents the code running without an RTT console Source Code (25 lines)
-
When debugging, printf directs to the debug terminal - the app seems to function When I build a release version I need to comment out printf otherwise the app will freeze How can I redirect printf output to the com port so as to prevent this? How is stdio set in the ses environment? (I am using a JLINK Edu with a Nordic development board to develop an app using a UART for serial comms) Many thanks for any help Rob
-
Nino Thanks for your help. I'll check with Nordic Rob
-
I am tracing a problem with an app running on a Cortex M0 using a JLink debugger and have been trying to analyse a hard fault. Execution freezes. If I pause exceution the call stack indicates HardFaultHandler() as the last function called and a call address in the vector table. The call address is ExternalISR9 rather than the address of the HardFault_Handler ???!!! Segger provides HardFaultHandler code which I've compiled and linked. However when the hard fault occurs, the code is not invoked. F…
-
Using Segger Embedded Studio what is the best practice for configuring the debugger for an app with interrupts(PWM for NRF51822)? For example: - are there any files that should be added to the project that assist debugging? - is it possible/useful to mask interrupts to facilitate debugging – if so, how? Many thanks for any help pS