Search Results

Is this true? I thought the example "Hello, world." used SWO to print console messages. Edit: Sorry. I was wrong. It's using RTT. I don't know why this site reformats my code to a single line :(. Source Code (1 line)

I will eventually use the internal tool chain (assuming it's using at least GCC 5.x so that I get C++14 support) but I just inherited this project and its nested makefiles etc and do not have time to convert the project. Choosing the files by clicking on the call stack gave me the errors that I posted (as images). Somehow though things are working smoothly now. I think it may have had to do with where the SES project file was located. I moved it to the root directory of my project but I'm not su…

I found it. Properties->Debugger->Debugger Options->Register Definition File to .svd file (I downloaded mine from the ARM website). Properties->Debugger->Debugger Options->Register Definition File Type->SVD

Hi, I'm using an STM32F415. I am not using SES to build only to to debug an externally generated .elf file. There is this from the manual: The Registers window shows the set of register groups defined in the memory-map file the application was built with. If there is no memory-map file associated with a project, the Registers window will show only the CPU registers. This described what I am seeing but where do I find a memory-map file and how do I associated with my project? I did tell the proje…

Thanks for the support. It turned out that the STM32F4 PDR_ON pin was left floating in the design which lead to unpredictable behavior. Fortunately VDD is pin 144 and PDR_ON is pin 143 so I was able to simply bridge the two and everything is fine. Sorry for the false alarm.

I am debugging a project that was built externally with make and the ARM GCC tools. I'm having difficulty getting the IDE to find the C source. Please see attached images for: 1. If I right click on the call stack and 'Go to Source' I get an error. 2. I tried adding the search path. 3. If I concatenate the path the .elf file is using with the search path the file is found at the command line. Thanks, Kenny Embedded Studio: V2.20 ARM GCC: 4_9-2015q1 OSX: 10.11.5 JLink Plus

OSX 10.11.4, GDB Server v5.12e I'm chasing an elusive bug on an STM32F415. It looks as if it is resetting as it prints a message that only happens during boot. I'm using OSX and tried to use Ozone. I set a breakpoint in main() but when I induced the error the processor did not halt. I set a breakpoint in the one and only place where the message is printed and it also did not halt on failure. Unfortunately I got to a place where Ozone kept crashing that I do not think is related to my bug. (I do …

Nevermind. The script had a trailing space in the device name. I might suggest that the parser handle that case. Thanks, Kenny

Hi, I get this error (see attached) trying to run a JLink script from the command line: $ jlink Soft.Device.jlink The script contains this line which works when opening JLink Commander and typing it. device NRF51422_XXAC When the error occurs I can also find and select this device when it asks me to manually select a device. This is on Windows 7 with JLink 4.96. Fails with both a Git/Windows Unix shell and the ordinary DOS shell.

Weirdly after a couple of hours of trying I managed to find some sequence that allowed me to flash both of these. It seemed to be unlock, followed by erase, followed by a read of address 0, followed by reset. Sorry, I tried to delete this post.

Hi, I have two freedom K64 boards that are now bricked or at least very erratic behavior. I've tried all kinds of things but cannot seem to bring them back to life. I'm completely dead in the water. Would you mind looking at this post I made in the Freescale community: community.freescale.com/message/433280#433280 Thanks, Kenny

Regarding your first issue. There must be a way to set the reset type in Code Warrior wherever you configure your debugger. In IAR there is the notion of a 'normal' reset type which maps to JLink's reset type 0--effectively let JLink decide which is best which I suppose is type 6. See the section "Strategies for Cortex-M Devices" in the JLink manual. If you wrote a JLink script you could select the device and the use 'rsettype' to set it explicitly but I'd be surprised if there is not a better w…

A couple of things to try: Uncheck "Use Flashloaders" in the debugger configuration. I always thought that was a terrible name for that option--if you aren't using a flash loader what *are* you using?--but I believe it selects which binary to download to perform the programming. When checked it uses the one that shipped with IAR. If not checked it will use the one that is part of the JLink DLL. Perhaps install the latest JLink software release if you haven't. Similarly you can run JLink Commande…

Hi Torsten, Your first statement is that it runs without errors then you say it produces errors on OSX. Under what conditions did it work? You go on to say that you enter arguments by hand and it returns 0. How would an interactive JLink session return 0? If the conditions in which it worked were under Windows is it possible that the script has incorrect line separators? "\r\n" rather than "\n"? That problem still creeps in every once and a while. Kenny

I see that you are using a JLink "On Board". Apparently these have the same features as JLink Base in which case the Flash Breakpoints feature may be in evaluation mode. On Windows it will annoyingly prompt you to enable it each time once you run out of breakpoints. The driver will do this so if you start with no breakpoints and start adding them it would pop up at some point. On Linux or OSX perhaps they don't have support for the pop-up in the driver so it may be silently failing? This is base…

Hi, I have a JLink Plus 9.3 with software V4.90 and I'm using IAR 7.20.2 with a Kinetis K64. I have configured things to use Semihosting + SWO Output and it works. The problem is that each time I enter a debug session it doesn't remember to enable ITM port 0 and direct it to the terminal window. Is this a JLink or IAR issue? Basically Port 0 is unchecked in the SWO Configuration window. Thanks, Kenny

This usually means that your device has run out of hardware breakpoints. One is used for single stepping so if you have a couple more set then you may be out. You may only have two total but I'd have to look that up. It wouldn't surprise me on this core. Does your JLink have the flash breakpoints feature? This is how I solved this on a Cortex-M3 (Analog Devices ADUCM320) that only had two hardware breakpoints. Sometimes I build the code to run completely or mostly out of RAM so that I can use as…

I received my replacement JLink+ and installed V4.88B software. The firmware upgrade was successful. I have been experimenting for a couple of hours now and I can't find a consistent way to successfully flash this part with JLink. Twice I was able to erase the chip, issue a hardware reset (reset button), and use the attached scripts with no errors. That's out of 20 or so attempts. Edit: The flash loader from ADI seems to work repeatably with IAR but this is not a solution to my problem. There is…

Hi, Using version 4.86B of the software and firmware I tried to flash two binaries--an FPGA configuration and the firmware. It failed with an error related to block verification. This is a new chip from Analog Devices and the device is recognized but the loader seems incompatible with the released silicon in some way (perhaps the unreleased silicon as well I'm not sure). I tried to upgrade to 4.88A thinking that it had been improved but the upgrade bricked my JLink so I don't have the specific e…

For posterity: This issue was caused by configuring the GPIO pin that also determines the boot mode as an output (P2.3/BM). The released silicon retains the configuration of I/O through a software reset by default and it caused the bootloader to be invoked. The previous silicon did not have this feature. Another bit that is somewhat confusing for this ADI part is that you must use reset strategy 7 "Halt after Kernel". In IAR it is called "Halt after Bootloader", which is the name of another rese…