Search Results
Search results 1-20 of 24.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
It seems the last address byte is somehow "ignoreded": Target.WriteU32(0xdc,0x90000); Target.WriteU32(0xe0,0x90000); Target.WriteU32(0xe4,0x90000); Target.WriteU32(0xe8,0x90000); Target.WriteU32(0xec,0x90000); => Console Target.WriteU32 (000000DC, 0x00090000); Target.WriteU32 (0, 0x00090000); Target.WriteU32 (0, 0x00090000); Target.WriteU32 (0, 0x00090000); Target.WriteU32 (000000EC, 0x00090000); But I just see: It is only a "console" problem. The data is (at least for the above addresses) writt…
-
Hi I have a strange bug in Ozone (2.56s). I do this: Target.WriteU32(0x506000e4,0x90000); The console shows: Target.WriteU32 (-2147483648, 0x00090000); Anyone has an idea what is wrong? Addendum: Target.WriteU32(0x506000e0,0x90000); => Console Target.WriteU32 (506000, 0x00090000); This is bizar as 0x506000c0 works! Same with decimal: Target.SetReg("R0",1348468964); Target.WriteU32(1348468964,0x90000); => Target.SetReg ("R0", 0x506000E4); Target.WriteU32 (-2147483648, 0x00090000);
-
Hi, finally I am back on the project. It is a custom HW using a TMS570LC43. To be sure I am now using latest DLL (6.32g) with IAR 7.80.4. I can connect to the target, download etc. as normal. But after the first instruction executed, "go" is no longer working, but stepping works. Meanwhile, it seems to be IAR related, as with the Jlink commander I can halt and go as often I want. InitEMU() seems not to be called, but SetupTarget() (I added a "Report"), so the script seems to be ok.
-
Quote from keylevel: “Do you need to add: Source Code (1 line)to your JLink script? More information in the JLink manual. ” Ok, I use IAR, so I tried to add a JlinkScript with JLINK_ExecCommand("SuppressInfoUpdateFW"); But which function should I use. I tried "ConfigTargetSettings", "TargetSetup" and "InitEmu": It is just ignored. I tried "InitTarget" and cannot connect to the target anymore.
-
Ok, I checked again and noticed, that even I have 6.30i installed Code Composer Studio uses 6.30f !? I will try 6.30i which I have installed and update the FW with the commander. ... Ok, yes. With the FW installed from 6.30i there are no more problems (at least with IAR C-Spy, but this is another topic). Thanks for the hint.