I need some help in getting the "debugging the kernel" to work. I can't
see the instructions in ram. I can see the instructions in ram if the ram
is in the internal block ram of the Xilinx. Here is a synopsis of the
steps:
I pulled up the "debug the kernel" page, and had to work around a few
of its issues. I'm using EDK 6.2 from Xilinx.
Since I am running using dynamic ram, I had to have the microblaze with
the dynamic ram controller running (for refresh) before I loaded anything
else. I have a "g" command in the microblaze internal code space to go to
the kernel once I'm ready to execute.
Workarounds:
First, I couldn't get a good environment by starting xmd.exe from a cmd
prompt. Running it from the Xilinx Platform Studio did provide a good
environment, however.
Second, image.elf does not load using gdb or XMD. Instead I loaded
image.bin using XMD. Then I started mb-gdb
Third, I only did a "sym image.elf" in the GDB console window, since
image.bin was already loaded previously.
After that, I was able to run the kernel by doing a "cont" in the gdb
console window. This executed the current block ram code in the Xilinx.
Then, I ran the kernel using the "g" statement in my console (Hyperterm
over RS232),
I was able to break the kernel by pressing "stop" button on the gdb gui.
I was able to see the instruction address. However I got a statement:
"Unable to Read Instructions at 0x8000413c"
The gdb window shows "process.c" and "default_idle" in the drop down list
boxes, so I know that the symbols are loaded and the processor knows where
it is. The call stack can be shown. I can show memory at the current
$pc! (that puzzles me) I can use the function browser and see functions
within the files in the window, but I can't "view source." I can see the
registers.
Here is the environment per the gdb show environment command:
!C:=C:\tools\edk_projects\nh3s400
ALLUSERSPROFILE=C:\Documents and Settings\All Users
APPDATA=C:\Documents and Settings\maxfield\Application Data
COMMONPROGRAMFILES=C:\Program Files\Common Files
COMPUTERNAME=CFW70372D
COMSPEC=C:\WINNT\system32\cmd.exe
HOME=/xygdrive/c/Documents and Settings/maxfield
HOMEDRIVE=C:
HOMEPATH=\Documents and Settings\maxfield
J2D_D3D=false
LMC_HOME=C:\Xilinx\smartmodel\nt\installed_nt
LOGONSERVER=\\CFW70372D
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
OS2LIBPATH=C:\WINNT\system32\os2\dll;
PATH=/xygdrive/c/EDK/gnu/microblaze/nt/bin:/xygdrive/c/EDK/gnu/powerpc-eabi/nt/bin:/usr/bin:/xygdrive/c/CBuilderX/bin:/xygdrive/c/EDK/bin/nt:/xygdrive/c/PROGRA~1/Borland/CBUILD~1/Bin:/xygdrive/c/PROGRA~1/Borland/CBUILD~1/Projects/Bpl:/xygdrive/c/WINNT/system32:/xygdrive/c/WINNT:/xygdrive/c/WINNT/System32/Wbem:/xygdrive/c/Program
Files/Common Files/Adaptec Shared/System:/xygdrive/c/Xilinx/bin/nt
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH
PROCESSOR_ARCHITECTURE=x86
PROCESSOR_IDENTIFIER=x86 Family 15 Model 0 Stepping 10, GenuineIntel
PROCESSOR_LEVEL=15
PROCESSOR_REVISION=000a
PROGRAMFILES=C:\Program Files
PROMPT=$P$G
SYSTEMDRIVE=C:
SYSTEMROOT=C:\WINNT
TEMP=/xygdrive/c/DOCUME~1/maxfield/LOCALS~1/Temp
TMP=/xygdrive/c/DOCUME~1/maxfield/LOCALS~1/Temp
USERDOMAIN=CFW70372D
USERNAME=maxfield
USERPROFILE=C:\Documents and Settings\maxfield
WINDIR=C:\WINNT
XILINX=C:\Xilinx
XILINX_EDK=C:\EDK\
TERM=cygwin
Attached is the mhs file we are using. We aren't using the fsl bus.
The hardware engineer does not think it is needed, and since gdb can read
the memory at the $pc, I'm assuming it isn't needed either. Are we wrong?
Any help would be appreciated.
thanks,
Wade
(See attached file: system.mhs)
***CONFIDENTIALITY NOTICE***
This communication (and any attachment) is confidential. It should only be
read by the person(s) to whom
it is addressed. If you have received this communication in error, please
notify the sender by reply and delete this communication.
*****************************************
Attachment:
system.mhs
Description: Binary data