M523evb, gdb, dBug and Multilink

Ivica — Tue, 26 Oct 2010 20:29:58 GMT

Hello,

I am trying to get my M5235evb board debugged under Linux and run a uClinux platform on it. I followed an example that basically uses the Codesourcery sprite to connect the P&E multilink cable. The example uses dBug to init the processor and then it loads the program , in my case the image.elf.

I am not sure if the dBug also starts at address 0x400, but from comparing the dBug link specs (it uses M5208evb) of both boards it seemed like 0x400 is the starting address.

This is what happens when I run the gdb:

--- Cut Here ---

This GDB was configured as "--host=i686-pc-linux-gnu --target=m68k-uclinux".
Reading symbols from /home/ivica/dev/uClinux/uClinux-dist/images/image.elf...(no debugging symbols found)...done.
(gdb) target remote | m68k-uclinux-sprite pe://USBMultilink/PE6011922 m5235evb
Remote debugging using | m68k-uclinux-sprite pe://USBMultilink/PE6011922 m5235evb
m68k-uclinux-sprite: Opening P&E USBMultilink port 1 (USB1 : USB-ML-CF Rev C (PE6011922))
m68k-uclinux-sprite: Target reset
0x00000000 in ?? ()
(gdb) set $pc=0x400
(gdb) c
Continuing.
^C
Program received signal SIGINT, Interrupt.
0xffe18c0a in ?? ()
(gdb) load
Loading section .text, size 0x14ef28 lma 0x20000
Loading section .data, size 0x110d0 lma 0x16ef30
Loading section .init.text, size 0xc0f2 lma 0x180000
Loading section .init.data, size 0xf0c lma 0x18c0f4
Loading section .romfs, size 0x129c00 lma 0x18d000
Start address 0x20000, load size 2714614
Transfer rate: 31 KB/sec, 7800 bytes/write.
(gdb) set $pc=0x20000
(gdb) c

--- Cut Here ---

When I set to start the dBug after the sprite Multilink connection and board reset nothing happens. Thus I am wondering if 0x400 is really the starting address of the dBug.

Any ideas to what am I doing wrong?

Regards,

Ivica Eftimovski

Re: M523evb, gdb, dBug and Multilink

Ivica — Thu, 29 Oct 2020 09:03:01 GMT

I figured it out: it was the Codesourcery’s Sprite script (m5235evb.xml). The address of RAMBAR was wrong. They had:

  <initialize>    <write-register address="RAMBAR1" value="0x20000021"/>    <!-- Enable PST[3:0] signals -->

And it should be:

  <initialize>    <write-register address="RAMBAR1" value="0x20000001"/>    <!-- Enable PST[3:0] signals -->

Now gdb works just fine on Ubuntu with m68k-uclinux tools. I can boot, run and debug the uClinux image.

ColdFire/68K Microcontrollers and ProcessorsのトピックRe: M523evb, gdb, dBug and Multilink

M523evb, gdb, dBug and Multilink

Re: M523evb, gdb, dBug and Multilink