Search Results
Search results 1-11 of 11.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
I am using your implementation of semihosting to do file I/O (the generic one with SEGGER_SEMIHOST_DebugHalt and no bkpt). Everything works great under Ozone. Now I would like to execute that under gdb. I start arm-none-eabi-gdb my_project.elf. My gdb session is: Source Code (6 lines)I have a BKPT after my file I/O. It is reached almost immediately (it takes ~1 minute to do all the I/O under Ozone), no files are created, nothing happens. I don't see any error messages. Am I enabling semihosting …
-
I am in the process of moving my project from gcc to clang. I am using RTT. Everything builds fine except the SEGGER_RTT_LOCK(); macro from SEGGER_RTT_Conf.h (the code will build cleanly when I change that macro to empty). The header is marked with Revision: $Rev: 13430 $. Build command: clang -o build_output/build/my_project_standalone.elf//my/project/path/libs/RTT/SEGGER_RTT.o -c -MD --target=arm-none-eabi -nostdlib --sysroot=/opt/toolchains/gcc-arm-none-eabi-9-2019-q4-major/bin/../arm-none-ea…
-
Okay - I'll wait for the fix. Just for your info: the very same setup worked fine on Windows locally with Ozone or J-Flash Lite + remote desktop, but was not as convenient if I had Ozone running on my development machine. Remote server on Windows gave identical #28 error.
-
Hello, I am trying to use Ozone 2.56e with JLinkRemoteServer 6.32b ARM (raspberry pi). Unfortunately communication seems to break down. Thank you for help. On the server end I get: Source Code (7 lines) In Ozone log I see: Source Code (100 lines)
-
This is an example Kinetis Design Studio project. It runs on K22-FRDM board. When -fPIC is enabled the code "crashes" (you have to press pause in the debug perspective to see it). I want to use PIC to have two firmware copies in flash at different addresses.
-
Hello, I want to use RTT on Kinetis K22 (FRDM-K22F board with SEGGER firmware). Final product will use the same MCU. I have a problem when I compile with -fPIC option. When I call SEGGER_RTT_Init() the MCU goes into an interrupt (EWM) I have not configured and hangs there. I know that calling SEGGER_RTT_Init() is not required, but when I try to output it is called anyway and hangs in the same spot. When I follow the call stack the last thing called is an "innocent" strcpy in SEGGER_RTT.c . My pr…
-
Hello, I am trying to use a Flasher Portable with a M25P SPI memory. When I use J-Flash SPI I only get 0xFF from the device during identification. I figured out that the CS line is not going low (even with no hardware attached at all). To test the hardware I tried the regular J-Flash and when trying to connect to a target the same pin is pulled low (so the hardware is okay). Is that a programmer firmware problem? I use the latest September 18th firmware and 5.02d software.
-
Hello, I have just got one Flasher Portable from Mouser. I want to use it to flash M25P and N25Q SPI flash memories. When I try to connect to the target using J-Flash SPI I get: - Connecting via USB to J-Link device 0 - ERROR: The connected probe (S/N 651100568) does not support the SPI interface - VTarget = 3.312V I use the most recent 8th July firmware. Do I need to to anything special to use the SPI mode?