Search Results

Sorry I must reject your answer on both points. 1) InitTarget is started (see to log bellow), but not from my script! I don't see MessageBox or JLINK_SYS_Report on log output. When I ommit "-device" on command line it works. 2) JLINK_SYS_Report messages is not saved to file. It is just visible on embedded web server log page. But it is lost when jlink is stopped after failure. This mean that is impossible to use it for debug. Can you help me? I can contact support too (I have JLink under support…

Hello, we have two TMS570LC4357 chips in JTAG chain. There is only one chance to set up it for jLink and it is jlinkscript. Problem is that latest version which works for us are V512f. Little bit old. After this version we has problem to port our jlinkscript due to changes on API (removed __int64 etc). Because this version is almost history we want to rewrite jlinkscript for latest version. But there is problem. jLink ignoring our InitTarget function and start some default function. When we omit…

I want to know it too. But my same request is 4 months old and still without answer. forum.segger.com/index.php?page=Thread&threadID=4303

Hello, I made RTOS aware debugging plugin for Segger GDB. Is it possible to make similar plugin for Ozone? I found just notice "Awareness for other OSes can be easily added." But I am not able to found SDK like for GDB. Is it exist? I want to know and fulfill external API of needed plugin. Jiri

Hello, Is it possible to use JLinkScript (same as for GDB) on Ozone? We need to setup JTAG daisychain for connection. It works perfectly on GDB, but we also want to try it in Ozone. Is it possible? How? Jiri

hello, we are using JLinkScript to connect MCU in JTAG daisychain. It was working fine in SW version before 6.16. But script fails on latest SW during compilation because didn't know __int64 type for variables. Documentation in chapter 5.11.5.2 Supported type specifiers still have __int64 as valid type. What changed? What is new size of "int", Is it 64bit and could be used instead __int64? How to make script compatible across version eventually how to test version inside this script to block run…

No reply? This problem is real a serious for us!

Hello, we have problem to write TI TMS570LS313 flash. Problem is simple. This MCU have ECC controller. Therefore we need to "write" 0xFF bytes into this memory. Flash contains 0xFF aftter erase already, but it is necessary to upgrade ECC record for this empty space. Therefore we made file aligned to flash sector, filled with this 0xFFs. An there is problem. jLink ignore this content absolutely and leave ECC unprogrammed! This flash part is unused, therefore normal code don't access it. This is O…

Hi, I notice, that jLink GDB server supports RTOS aware debug on latest beta SW. On user manual I found notice that SDK to create own plugin is available on request. Is it available from now or sometime in future? Can I have it? We would like to write plugin for debug own in house RTOS. Have i nice day, Jiri

Solved. JLinkScript allow to write script to solve it.

deleted post

Any news? Did you made some decision on about bug fix date?

Any news? Did you made some decision on about bug fix date?

-- (deleted post)

Hi, I think that I found some more informations. Problem is on the internal watch dog. Our code enable this watch dog early as is possible during boot. Here is code used on demontration. This user code works without problem: C Source Code (6 lines) And this code not C Source Code (8 lines) Minimalistic binary to demonstrate problem you can found in attachment. After you will flash this into TI HDK TMS570LC4357, you will able to connect only with on-board XDS100v2 JTAG and TI Uniflash SW. Best re…

Hi, we have some difficultes to use J-Link with TMS570LC4357 microcontroller. When program flash is empty, it works fine without any problem and here is result of start GDB with command line Source Code (1 line) Source Code (40 lines) But problem is connection to chip where running SW. JLInk reset target sucessully, but not catch it and MCU boot normally into SW and GDB server fails like this Source Code (43 lines) Ugly and unreliable work arround is reset MCU manually by nRST signal (pin B17) a…