Friday, May 25th 2018, 1:12pm UTC+2

You are not logged in.

  • Login
  • Register

Search results

Search results 1-7 of 7.

Yesterday, 10:17am

Author: jev

oZone + IAR: ElfDwarf problems and unexpected break

Quoted from "SEGGER - Nino" Regarding 1: Such an issue is not known to us. Could you provide the .elf file for reproduction? Sure, see attachment. I took the BLE blink app from Nordic's SDK15, compiled for Nordic nRF52832 with an S132 softdevice. In order to reproduce my environment, you'ld need to flash the softdevice first (download the SDK from Nordic's website here, the softdevice is stored in ~/nRF5_SDK_15.0.0_a53641a/components/softdevice/s132, than load this compiled application through ...

Thursday, May 17th 2018, 11:30am

Author: jev

oZone + IAR: ElfDwarf problems and unexpected break

Hey guys, I'm using oZone 2.56l on a Nordic nRF52832 connected by a J-Link Plus. Toolchain: IAR 8.11.2. I have two problems with this configuration lately: 1. On loading the generated .out file, I get messages from oZone: Source code 1 2 3 File.Open ("C:/projects/foo/_build/foo.out"); ElfLib: libdwarf: Debug info NULL in func _dwarf_strtab_init (.debug_str, 0x0) ElfLib: libdwarf: No Error in func _dwarf_loclist_add_locdesc (base address entry in location list unsupported, 0x0) It still loads the...

Thursday, April 26th 2018, 12:21pm

Author: jev

oZone reset behavior

I use oZone with a J-Trace for ARM Cortex-M on a Nordic nRF52832. When resetting the system, I see different behavior with tracing disabled, also different behavior on first start. It seems oZone just reads the start address from the ELF file and jumps to that address, is that right? Can I change this behavior so that it mimics a true cold reset (through the bootloader, using the MBR etc.)?

Tuesday, January 23rd 2018, 11:39am

Author: jev

[SOLVED] [Ozone] stepping / running interrupt disabled

Okay, fair enough. I'll just have to work around the issue until it's implemented - hopefully soon!

Monday, January 22nd 2018, 5:03pm

Author: jev

[SOLVED] [Ozone] stepping / running interrupt disabled

I'm using oZone on a J-Link (well euhm... J-Trace to be honest) to debug an nRF52 system running FreeRTOS. I can't really step through the source because FreeRTOS swaps tasks on a timer interrupt and than crashes. Is there a way to disable interrupts from the debugger once it hits a breakpoint?

Friday, January 12th 2018, 5:34pm

Author: jev

[SOLVED] J-Trace to debug using IAR

Thanks for your prompt answers Nino! Unfortunately, ETB selection results in continuous popups of "Driver" dialogs "Warning: ERROR: Failed to stop trace" at every command I execute (step, reset, everything really). Unfortunately, we have no support contract with IAR (we're just a small startup that can't justify the extra expense there) so basically we're euhm... you know. Is there anything Segger can do to push this issue a bit harder to IAR? I know IAR has its own debug pod but it never hurts ...

Thursday, January 11th 2018, 9:37pm

Author: jev

[SOLVED] J-Trace to debug using IAR

I have a project that was built using IAR's Embedded Workbench. The target hardware contains an Nordic Semi nRF52832 from which only GND, Vcc, SWDIO and SWCLK are available on the outside. Flash and debug always worked flawlessly on this hardware using a simple J-Link but that one is no longer available to me. I do have a J-Trace Pro for ARM Cortex-M available though. The problem I'm facing is that IAR's debugger won't play nice with J-Trace. It flashes correctly but once the debugger is started...