[U-Boot-Users] marvell db64460
hi,
we have purchased marvell DB64460 development board by means of NDA agreement. the board comes with patch for uboot 1.0.0, I successfully compiled it with gcc 2.95 recommended by marvell and board boots well. But my aim is to debug uboot,because I wanna learn uboot programming and debugging for our custom board that hasn't any bootloader. our debugger is bdi2000 and I prepare configuration file via looking configuration files of other boards.now I can successfully write flash with jtag. But I have some problems with gdb, gdb that I'm using is version 5.2.1. When I set breakpoints somewhere in code, code doesn't stop in breakpoints. sometimes it stop but gives "Program received signal SIGSTOP" error. sometimes I'm able to execute code step by step,sometimes not. I'm confused too much. In your opinion Is there any combination between gdb and gcc version? For gcc 2.95, what is right gdb version?
thanks a lot.
Engin KARABULUT engink@gmail.com wrote:
we have purchased marvell DB64460 development board by means of NDA agreement. the board comes with patch for uboot 1.0.0, I successfully compiled it with gcc 2.95 recommended by marvell and board boots well. But my aim is to debug uboot,because I wanna learn uboot programming and debugging for our custom board that hasn't any bootloader. our debugger is bdi2000 and I prepare configuration file via looking configuration files of other boards.now I can successfully write flash with jtag. But I have some problems with gdb, gdb that I'm using is version 5.2.1. When I set breakpoints somewhere in code, code doesn't stop in breakpoints. sometimes it stop but gives "Program received signal SIGSTOP" error. sometimes I'm able to execute code step by step,sometimes not. I'm confused too much. In your opinion Is there any combination between gdb and gcc version? For gcc 2.95, what is right gdb version?
Ummm, you didn't mentioned CPU type and gave BDI config file and log message. So it's hard to give useful hints, I am afarid. GDB version is just one possible part, anyway.
Thanks,
Sam
P.S. And pls don't post HTML to this list. Only plain TEXT is welcome!
___________________________________________________________ 抢注雅虎免费邮箱-3.5G容量，20M附件！ http://cn.mail.yahoo.com
Our board is DB64460A1-MPC7457,which has MPC7457 cpu. I give the configuration file to you below. could you give us your bdi2000 configuration file? and what is the version of gdb and gdb using by you?
;bdiGDB configuration file
;-------------------------------------------------------------- ; [INIT] ; init core register WREG MSR 0x00000000 ;MSR : ME,RI WSPR 1017 0x00000000 ;L2CR : disable L2 cache WSPR 1008 0x84000000 ;HID0 : disable I/D cache
;init memory controller
[TARGET] CPUTYPE 7457 ;the CPU type JTAGCLOCK 0 ;use 16 MHz JTAG clock BOOTADDR 0xfff00100 ;WORKSPACE 0x42000000 ;workspace in target RAM for data cache flush and L3PM access BDIMODE AGENT ;the BDI working mode (LOADONLY | AGENT | GATEWAY) STARTUP RESET BREAKMODE HARD ;SOFT or HARD, HARD uses PPC hardware breakpoint ;STEPMODE HWBP ;TRACE or HWBP, HWPB uses a hardware breakpoint STEPMODE TRACE ;DCACHE FLUSH ;data cache flushing (FLUSH | NOFLUSH) ;MMU XLAT 0xC0000000 ;enable virtual address mode MMU XLAT PTBASE 0x000000F0 ;address where kernel/user stores pointer to page table pointers ;VECTOR CATCH ;catch unhandled exceptions ;SIO 7 9600 ;TCP port for serial IO, check BCSR1: enable RS232-1 !!!
;MEMDELAY 4000 ;additional memory access delay ;REGLIST STD ;select register to transfer to GDB ;L3PM 0x00100000 0x80000 ;L3 privat memory
[HOST] IP 10.18.3.183 LOAD MANUAL ;load code MANUAL or AUTO after reset DEBUGPORT 2001
[FLASH] CHIPTYPE STRATAX16 ;Flash type (AM29F | AM29BX8 | AM29BX16 | I28BX8 | I28BX16) CHIPSIZE 0x800000 ;The size of one flash chip in bytes (e.g. Am29LV800BB = 0x100000) BUSWIDTH 32 ;The width of the flash memory bus in bits (8 | 16 | 32 | 64) WORKSPACE 0x42000000 ;workspace in SDRAM /marvell internal sram/
Engin KARABULUT engink@gmail.com wrote:
Our board is DB64460A1-MPC7457,which has MPC7457 cpu. I give the configuration file to you below. could you give us your bdi2000 configuration file? and what is the version of gdb and gdb using by you?
Actually, I am also puzzled by this issue. We used another JTAG tool on MPC7447A debug and had the similar issue. Recently, we used BDI2000 on a MPC7448 target for u-boot debug with a third party support and encountered the same result. GDB console cannot be inserted with a hardware breakpoint. It was simply reported by BDI2000 with the message 'All breakpoints are in use'. No matter how you clear breakpoints, problems still existed.
In a word, target cannot be stoped by a pre-defined breakpoint like board_init_f in BDI2000 and hardware breakpoints cannot be set in GDB.
Similar report in archive could be found:
http://sourceforge.net/mailarchive/message.php?msg_id=6101766
A nice hint could be helpful:
http://www.ultsol.com/faq_p304.htm
Good luck and happy hacking,
Sam
P.S. Pls don't TOP-REPLY. For discuss better, I changed the thread as the title above.
___________________________________________________________ 抢注雅虎免费邮箱-3.5G容量，20M附件！ http://cn.mail.yahoo.com
Hi,
Sam Song samsongshu@yahoo.com.cn wrote:
Engin KARABULUT engink@gmail.com wrote:
Our board is DB64460A1-MPC7457,which has MPC7457 cpu. I give the configuration file to you below. could you give us your bdi2000 configuration file? and what is the version of gdb and gdb using by you?
Any progress on debug? Could you pls try to check BDI2000 confile [INIT] part and adjust MSR value like 0x02003002 and IABR - 1010 as 0x702?
In 74xx BDI UM P40, MSR[IR] bit should be match with IABR[TE] bit to make the breakpoint valid.
Thanks,
Sam
___________________________________________________________ 抢注雅虎免费邮箱-3.5G容量，20M附件！ http://cn.mail.yahoo.com
participants (2)
-
Engin KARABULUT -
Sam Song