Search Results

Thank you very much for your reply Jan. I will keep that in mind when using the Flasher Portable. Best Regards Giuseppe

Dear friends at Segger, Our Flasher Portable fails when trying to program a STM32F4 firmware which includes the Device.pex file (in its proper directory). Notice that: 1. the FAIL LED turns on immediately, as soon as pressing the PROG button 2. the FLASHER.LOG just contains this generic error line: SN: 8014 - Failed 3. the same firmware (including the same .pex file) works fine on a Flasher Portable PLUS 4. if we remove the folder containing the .pex file, then the Flasher Portable too programs …

Thank you Nino for the prompt reply. I will wait for the patch, no problem. KR Giuseppe

Dear friends at Segger, the latest firmware prevents our J-Trace Pro probe to work with the J-Trace Isolator V1.0B. The "Target power " LED keeps on blinking red and the debugger cannot connect. If we remove the isolator board, then the LED blinks alternatively orange and green, and it is possible to connect to the target and debug again. Thank you for your attention. Kind Regards

On second thought, I don't think the crash actually occurs at the moment of the hard fault, but just a few seconds after hitting RUN. KR Giuseppe

Dear friends, I am trying to debug a hard fault through Ozone, connected to our J-Trace Pro. We have full trace capabilities (4-bit) on our hardware, but when I select Trace Pins as Trace Source in the Trace Settings, Ozone crashes - apparently upon meeting the hard fault - with the following message: An unexpected exception occurred and Ozone needs to close. A crash report was stored to: [file path].dmp Please find attached the dump file reported in the message. Any help will be much appreciate…

Dear friends at Segger, the latest versions of J-Flash no longer seem to work when driven by command line. The files .cfg/.dat are not created, although the software does not report any error. We tried with the latest Beta version (6.83b), but that does not work either. We then reverted to a previous version (6.80e), which works fine. Here is the log taken from J-Flash V6.82c, from which you can see all of our command-line parameters. Strangely, when supposed to create the output .cfg/.dat files…

Problem solved! Thank you guys. KR Giuseppe

Thank you Fabian, for your prompt reply. As soon as I connect the J-Trace Pro to the USB port, I get what you see in pic1.png. I press O.K. to restore the firmware, then I get pic2.png. When closing the dialog and return to the command prompt, I see what is in pic3.png Now there is no way to give the command you suggest me: exec invalidatefw as soon as I try, the first pop-up (pic1.png) appears again. KR Giuseppe

Dear Sirs at Segger, I just downloaded the JLink package for Windows V6.82. As soon as I tried to connect my J-Trace Pro to the IDE, the prompt came up to update the firmware, which I have always done without any glitch. But this time was different. Don't know how, but something went wrong with the update procedure. Now, when trying to connect to the probe (e.g. from the command-line JLink) this message pops up: "The firmware of the connected J-Link will now be restored. The connected J-Link is …

Hi Alex, Thanks to all of you guys at Segger for addressing the issue this quick! No real inconvenience caused. I am a firmware developer myself and perfectly understand these things happen. KR Giuseppe

Thank you Alex, for investigating this issue. The log file attached is all the GDB server created when trying to start a debugging session. I suspect the log appears to be cut off because the server shut down unexpectedly. I have tried again this morning and got a similar result, with the last line in the log saying "... Restoring RAMCode". I said in my first post "My firmware seems to load fine on the target". Actually, this is not quite correct. I apologize. Here is exactly what happens with t…

Sure Erik, actually I should have known better and send it in the first place. Thanx Giuseppe

Just updated the software to V6.60, which also updated the firmware on my J-Trace Pro. My firmware seems to load fine on the target, from STM32CubeIDE, through JLinkGDBServer.exe. But as soon as loaded the server closes down and the IDE shows a message saying: Target disconnected. Not a directory. Downgraded the software to V5.56d (leaving the new firmware on the J-Trace alone). Everything works fine again.

Oh, how wonderful are you guys at Segger! Thank you so much and keep up your excellent work.

Using J-Flash V6.20c (latest as of today). MCU is LPC1788 by NXP. Trying to generate both .cfg and .dat files from a .hex firmware file, using command line. Whereas the -savecfg switch works fine, the -savedat fails. Last line in the log file is "- ERROR: Failed to save data file". The same thing from the GUI works fine. Here is my command line: "C:\Program Files (x86)\SEGGER\JLink_V620c\JFlash.exe" -jflashlogTEST.log -openprjTEST.jflash -openTEST.hex -saveprj -savecfgTEST.cfg -savedatTEST.dat A…

Dear Adrian. I tried on the LPCware forum. This is the reply I got: Suggest you report this to Segger: - NXP has no knowledge of, or access to the simulator - the Segger guys do not hang out here, so won't know of your problems as you can see at this page: lpcware.com/content/forum/emwi…tom-fonts#comment-1143067 So, I guess I'm stuck here. Please, can you let me know how much will it cost me to get the "direct support from SEGGER" that you talk about? Thank you. KR Giuseppe

The font was generated by Font Converter for emWin version 5.18, whereas the simulation library (emWin_x86.lib) was taken from an updated emWin fox NXP, version 5.24H. Could this be the reason :?: KR Giuseppe

Dear friends, I am trying to set up an emWin simulation (under Visual Studio 2010) for a firmware of mine that works fine on the real hardware. Unfortunately, every time I try to display some text strings using some custom fonts the program crashes with the message: An unhandled exception of type 'System.AccessViolationException' occurred in Startup.exe Additional information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. The problem disap…