Search Results
Search results 1-4 of 4.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
[SOLVED] [bug]ozone v3.10b can not get the correct initial PC based iar7.10 *.out
caowent - - Ozone related
PostTested on Ozone v3.10g, the problem is still there(Only for new projects).
-
[SOLVED] [bug]ozone v3.10b can not get the correct initial PC based iar7.10 *.out
caowent - - Ozone related
Post1. Thank you for your attention. 2. Please change the file name "project.out.bin" to "project.out". 3. The same problem was encountered again today. This time in MDK. 4. The problem caused the program to skip "SystemInit ()". 5. After I used Target.ReadU32 (VectorTableAddr + 4) to get the PC value, the problem was solved.
-
[SOLVED] [bug]ozone v3.10b can not get the correct initial PC based iar7.10 *.out
caowent - - Ozone related
Post1. It is possible to debug the same * .out (created by iar 7.10) with the ozone project created by v2.70, but the ozone project created by v3.10 is wrong. 2. The screenshot below shows that they got a different PC and v2.70 got the right PC. 3. The source code shows different content inside the two projects. 4. Elf.GetEntryPointPC (), this api cannot get the correct initial pc, at least * .out created by iar 7.10. C Source Code (14 lines) C Source Code (19 lines)
-
C Source Code (1 line)1. The same target machine code is parsed normally in V2.52d. 2. Under V3.10, the log level mark is not rendered, and the error log cannot be highlighted. And format output, parameter parsing is abnormal. 3. “SEGGER_SYSVIEW_ErrorfTarget” is parsed normally, but the color rendering is not. - Figure 1, V2.52d is normal - Figure 2, V3.10 is abnormal