Greetings, When using the DIAB linker for the PPC8250 target I see some anomalies in the generated o/p srec. I have a bunch of STORE 0xAABBCCDD, 4 directives in the .dld file to put some sort of a header, however I see the 0XAABBCCDD in the srec. followed by 12 zero bytes. Anyone encounter this. I guess I should use ddump to look at the .elf to see whether there is a goof up there or in the ddump from elf to srec conversion. Any pointers?

DIAB 5.2.0.0 Linker issue
Started by ●December 8, 2004
Reply by ●December 9, 20042004-12-09
"Whaddayawant" <cunkar@sbcglobal.del.net> wrote in news:48vtd.3491$Dh2.1232@newssvr31.news.prodigy.com:> Greetings, > When using the DIAB linker for the PPC8250 target I see some anomalies > in the generated o/p srec. I have a bunch of STORE 0xAABBCCDD, 4 > directives in the .dld file to put some sort of a header, however I see > the 0XAABBCCDD in the srec. followed by 12 zero bytes. Anyone encounter > this. I guess I should use ddump to look at the .elf to see whether > there is a goof up there or in the ddump from elf to srec conversion. > Any pointers?Instead of using store directives in the dld file, how about creating a section in the dld file at the location you want the header. Then create an assembler file that contains the header in the same named function. Add the file to your source list and then check you map file for the correct location and header contents. What does your binary output file look like? That is, is this an SREC issue or a linker output issue? -- - Mark -> --
