Changes between Version 3 and Version 4 of Tools/Xilinx_SDK

Timestamp:

May 4, 2012, 11:38:51 AM (12 years ago)

Author:

murphpo

Comment:

--

Tools/Xilinx_SDK

@@ -22 +22 @@
  * Use the "Debug" launch process. This processes uses GDB to read the start address, which succeeds where XMD fails.
 
- * If you can't update your address map (likely if you're using the 2GB DRAM, which should be at 0x0), you can still use the "Run" launch process. Let it execute normally. Then, when it fails to boot, at the XMD prompt run {{{stop}}} then {{{con 34 0xFFFFFFFC}}}. This will force the PPC to start executing code from the PPC reset vector (0xFFFFFFFC), which (if the .elf is valid) will boot the PPC, then jump to the address for .text specified in your linker script.
+ * If you can't update your address map (likely if you're using the 2GB DRAM, which should be at 0x0), you can still use the "Run" launch process. Let it execute normally. Then, when it fails to boot, at the XMD prompt run {{{stop}}} then {{{con 34 0xFFFFFFFC}}}. This will force the PPC to start executing code from the PPC reset vector (0xFFFFFFFC), which, if the .elf is valid, will boot the PPC then jump to the address for .text specified in your linker script.
 
 
 ----
-'''ISOCM access via XMD'''
+'''PPC ISOCM access via XMD'''
+The PowerPC instruction side on chip memory (ISOCM) interface is a useful feature- a memory block for code which the PPC can access without occupying the main PLB. But, because the ISOCM memory is not on the main PLB, the debugger cannot access it directly. XMD can access ISOCM, but it requires specific flags be passed during XMD initialization. Unfrotunately Xiilnx did not automate the process of setting these flags, even in projects which use the ISOCM.