To the best of my knowledge, I had could single step but not run to a breakpoint in the initial u-boot code on PPC8540( an E500 core based) system Esp. in the code in start.S. I had a problem where the flash was busted and The start.S was running from a DDR2 memory at 600+MHz rate. So, I had to lock the TLB and define LAW for the DDR memory in BDI so that we could run entire u-boot, kernel, ramdisk from RAM.
It seemed like a BDI bug to me unless the processor is designed to always boot from a slow deviceflash or eeprom) till the initialization sequence is Completed. Did not try extensive debug with it, so not sure. If it helps. -- Atul -----Original Message----- From: [EMAIL PROTECTED] [mailto:linuxppc-embedded-bounces at ozlabs.org] On Behalf Of Fahd Abidi Sent: Friday, February 03, 2006 10:41 AM To: linuxppc-embedded at ozlabs.org Subject: Gdb with MPC85xx Hello, I am wondering if someone here is using GDB to debug code on an 85xx platform with the BDI. I have been running into several issues with GDB 5.x and 6.x where the E500 core does not seem to either step properly to the next line of code in the kernel or uboot or gets lost altogether. Each version of GDB seems to have its own set of bugs. If someone has been using a version of GDB that works pretty well then let me know what version it is and I can try and download it and build it and see if it behaves better. This is probably more of a tools question then a Linux question, I'm hoping I can get an answer anyway. Thanks, Fahd _______________________________________________ Linuxppc-embedded mailing list Linuxppc-embedded at ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-embedded
