<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>RE: debugging custom Xilinx boot loader with abatron and Montavistadevrocket</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>> 1) In DevRocket, what kind of project do you choose to debug an<BR>
> externally build .elf file?<BR>
> MontaVista support engineers had no clue.<BR>
<BR>
Not sure about DevRocket specifically, but in Eclipse you would choose a C<BR>
application with external makefile. In Eclipse 3.1 (with CDT) its specifically<BR>
called a "Standard Make C Project". There's also something similar in the<BR>
Xilinx EDK Eclipse-based offering (called Platform Studio SDK). The PS-SDK<BR>
defaults to using backend xmd/gdb through the FPGA JTAG port.<BR>
<BR>
My personal preference is to use gdb standalone or ddd/gdb<BR>
<BR>
> 2) How do you use DevRocket to create a cross compiled set of code<BR>
> linked to a specific address.<BR>
> MontaVista support engineers also had no clue on this one.<BR>
<BR>
Again, not sure in DevRocket. In general, you will want to use a custom<BR>
linker script. You can tailor a linker script from one of your EDK projects.<BR>
To pass it into the linker (ld), use the -T option. Another useful option is<BR>
-M to create a map file. If you're calling the linker from gcc, remeber to<BR>
preface these options with -Wl. man ld and man gcc are your friends.<BR>
<BR>
If you get really stuck, you can look at a the makefile from an example EDK<BR>
project and see what it is doing.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>