Search Results

Hi, i recently bought an STM32H745I Discovery board to test the STM32H7 dual core uc. I now wonder if the ST-Link on this borad could also be used with the J-Link firmware. According to this site: segger.com/products/debug-prob…j-links/st-link-on-board/ the stm32h7 disco board is not supported yet. I tought the ST-Link might be not that different from the the one on the other discovery boards so it might work out of the box. Does someone tried it already ? Is it planned to support this board too…

Hi, i wasn't able to find anything in the manual about this. I want to replace the Ram area J-Link uses for Flash breakpoints (reprogramming the flash). I think the command for this is "SetWorkRam". I only found a Wiki-Page which says the amount of Ram should not be lower than 512 bytes. But what is the recommended size of RAM J-Link needs to work properly with Flash Breakpoints for CFI flashes ? Thanks for your help. Hans

Hi, we use an IS25LP128 QSPI flash chip together with an LPC43xx uC. The IS25LP128 can be ordered in different versions. 1. A version which has a fixed byte on a specific memory location which indicates QSPI functionality. 2. A version where this byte is programmable by software. We use the second version at the moment and JFlash clears that every time we reprogram the flash chip. This is a little annoying since the boot after the flashing is very slow since the QSPI byte is erased and signals t…

Hi there, i had a similar problem with ozone a year ago and it seems to have come back. Our embedded software uses c++ quite alot. Also with templates etc. There the symbol table is quite huge and the elf file has around 40MB. When i load the .elf file in ozone, it hangs for about 5min until it loads the elf file. The error message looks like this: ELF warning (1009): the symbol location decoder encountered an unsupported operand: DW_OP_GNU_convert. ELF warning (1009): the symbol location decode…

ok strange. The Xplorer Evalboard has no ISSI FlashChip as far as i know. I double checked and the newest version have to reset the QE in the ISSI Flash because after i flash it the chip starts in normale spi mode and QSPI mode. I should have mentioned to the other problem with the RamCode. When there a programm running on the M0APP_Core and on the M4_Core and i then want to flash the M0_APP core. Only then this error occurs. If there is only a program running on the M4 it works fine. I'll check…

Hi, i'm using a custom hardware. Its an LPC4370 with an ISSI IS25LP128 QSPI Flash chip. The flash chip is connected through the SPIFI interface of the LPC4370. I'm also sure that earlier versions of JLink worked fine. I'm not exactly which one it is at the moment. Best, Hans

I tried the newest 6.34 version of JLink and the problems remain

I think a problem in ozone is related to this. When i am attached to a running program i get this error message after a few seconds.

Hi there, with the recent versions of JFlash etc. i got that the attached error message occurs quite often. I have to reset the board a few times and find the right timing when the flashing works. Using Ozone or gdb server is no problem as far as i can tell. With the 6.32i version is also still the case that the QE Bit in the ISSI qspi is cleared when i reprogram the flash. I another thread about this it was said that there will be a fix soon. Is there already a time when this will happen ? Than…

Hi, ok now it makes sense to me. I have to say i don't understand the reason why to clear the QE bit after flashing ? Is there a specific reason why you do this ? The workaround is a little annoying because during my development cycles i have to flash frequently. But a fix in 2-4 Weeks is perfect. Thanks so much, Hans

Hi Nino, ok thats weird. Than why is this happening with the current JLink version if this is not implemented yet ?

Hi there, i currently use the IS25LP128 flash chip with an LPC4370. The SPIFI interface is capable to run code in QuadMode directly from the flash chip. In order to activate the QuadMode you have to set a bit in the ISSI flash chip to signal that the FlashChip is able to run in quad mode. Normally i had to set this bit just once because its non volatile. Currently with the newest JLink version this seems to be reset, when i flash a new program. So now i have to set the QE again every time i fals…

Ah thats perfect. Thanks so much

Hi there, since the manual of ozone does not say anything about it, i assume that it is not possible with ozone to be attached to two different cores at the same time. Am i right ? I just want to be sure if this is possible or not. Can i start multiple instances of Ozone ? with different configured projects ? In my work with the LPC4370 with 3 MCU it is very helpful to attach to all 3 cores simultaneously with Gdb through different ports on the Gdb-Server. If its not possible with Ozone. Is it p…

Hi Nino, sorry my notification settings were not set anymore. I am using the GNU Arm Eclipse tools at the moment for debugging. I will have a close look at OZone. I use a small piece of assembler code at the moment to set the SP at the beginning of my ResetISR. Thanks for the answer i might forward this to the GNU Arm guys. Best, Hans

Hi there, i currently work with an iMX6SX. I already read in some threads here, that the DAP is not correctly implemented from NXP/Freescale so you cannot load code to the M4 with the J-Link probe directly. So i have a small A9-Boot program which i load via gdb, which enables the M4 core and load a minimal program which directly hits a wfi so that the processor remains in a valid state until i load the real application to the M4 core. The gdb and j-link are correctly loading the program and it s…

Hi Nino, my host PC specs are the following: - Surface Book generation 1 - Prozessor Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz, 2808 MHz, 2 Kern(e), 4 logische(r) Prozessor(en) - Installierter physischer Speicher (RAM) 16,0 GB - Windows 10 Pro, Version 10.0.16299 Build 1629, Runs natively I could provide you with the elf file but only if you keep it closed at SEGGER for debug purpose. I don't want to be it public in this forum. The file is about 20MB i could provide you with a download link via e…

Ah sorry again some infos. I don't have the problem that ozone consumes to much ram. All the time the memory consumption is about 500MB. But the cpu load is high.

Oh ok. I think i have the same problem as other users already experienced it. After approx. 15min of hanging/stalling Ozone managed to open my elf file. Is this still normal with the newest version ?

Hi there, i searched the forum and found similar posts, that ozone directly closes if an large .elf file is loaded. In my case ozone just hangs and does not respond anymore when i load my .elf file. The elf file is about 20MB. I use Ozone 2.56 64-bit and the newest j-link tools. I am running it on a Win10 64-Bit laptop with 16GB of ram which should be enough i think. Does anyone else have a similar problem ? Best, Hans