Problems with gdb with mcf5235BCC EVB

matthew riek matthew.riek at gmail.com
Fri Feb 8 13:37:34 UTC 2008


Hi all,

My earlier post can be somewhat ignored now.  It seems I have a problem
either with VMWare or the machine it is installed on.  I did a fresh install
of *nix on another box, and the bdm seems stable now.  I no longer get
target bus errors, and things are behaving far more as expected.  At least
now, I can launch debug sessions as per the gdb-init supplied with the 5235
BSP.

Has anyone else had problems with gdb with dbg monitor on VMWare?  I am
still interested to hear about 5329 BSP's, and init scripts that don't
require booting and breaking dBug first.  I have pasted my init script below
(the attachement didnt work in the earlier post).  I'm sure I will find it,
but as of now, this script still has SP issues.  I can set the stack pointer
to the top of SRAM but the SP keeps being set to 0xfffffffe such that any
jsr or rst will throw and exception.

Cheers for any help or comments.

my .gdb-init script... The goal is to not have to have freescale dBug boot
and break first before loading the elf....


target remote | m68k-bdm-gdbserver pipe /dev/bdmcf0

monitor bdm-reset

#
# Show the exception stack frame.
#
define show-exception-sframe
 set $frsr = *(unsigned short *)((unsigned long)$sp + 2)
 set $frpc = *(unsigned long *)((unsigned long)$sp + 4)
 set $frfvo = *(unsigned short *)((unsigned long)$sp + 0)
 set $frcode = $frfvo >> 12
 set $frvect = ($frfvo & 0xFFF) >> 2
 set $frstatus = ((($frfvo >> 10) & 3) << 2) | ($frfvo & 3)
 printf "EXCEPTION -- SR:0x%X  PC:0x%X  FRAME:0x%x  VECTOR:%d  STATUS:%d\n",
$frsr, $frpc, $frcode, $frvect, $frstatus
 if $frstatus == 4
  printf " Fault Type: Error on instruction fetch"
 end
 if $frstatus == 8
  printf " Fault Type: Error on operand write"
 end
 if $frstatus == 12
  printf " Fault Type: Error on operand read"
 end
 if $frstatus == 9
  printf " Fault Type: Attempted write to write-protected space"
 end
end

# Set RAMBAR = 0x20000001
monitor bdm-ctl-set 0xc05 0x20000001

# Set PAR_SDRAM to allow SDRAM signals to be enabled
set *((char*) 0x40100046) = 0x3f

# Set PAR_AD to allow 32-bit SDRAM if the external boot device is 16 bits
set *((char*) 0x40100040) = 0xe1

# Turn off WCR
set *((short*) 0x40140000) = 0x0000

# 1MB ASRAM on CS1 at 0x30000000  (THE 5235 BCC doesn have this, the EVB
doesnt populate)
set *((short*) 0x4000008C) = 0x3000
set *((long*) 0x40000090) = 0x000f0001
set *((short*) 0x40000096) = 0x3d20

# 2 meg flash on CS0 at 0xffe000
set *((short*) 0x40000080) = 0xffe0
set *((long*) 0x40000084) = 0x001f0001
set *((short*) 0x4000008a) = 0x1980

# 16 meg sdram (page 18.6.4 of ref 5235 ref-manual)

#powerup sequence
set *((short) 0x40000040) = 0x0446
set *((long) 0x40000048) = 0x00001300
set *((long) 0x4000004c) = 0x00fc0001

#precharge
set *((long) 0x40000048) = 0x00001308
set *((long) 0x00000000) = 0xdeadbeef

#refresh sequence
set *((long) 0x40000048) = 0x00009300

#wait at least 8 auto refresh cycles to occur
# I don't know how to wait, so im just getting gdb to print something for a
pause
print $pc

#enable IMRS
set *((long) 0x40000048) = 0x00009340

#access sd ram to initialize the mode register
set *((long) 0x00000400) = 0x00000000

#set stack pointer
set $sp = 0x2000fffc

b _uhoh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/users/attachments/20080208/c39c213c/attachment.html>


More information about the users mailing list