Hi Jon, On Fri, Jul 5, 2013 at 4:10 AM, [email protected] <[email protected]> wrote: > On Thu, Jul 4, 2013 at 7:40 PM, Drasko DRASKOVIC > <[email protected]> wrote: >> On Thu, Jul 4, 2013 at 11:32 PM, Andreas Fritiofson >> <[email protected]> wrote: >> >>> What is at 0x80200000? At 0x80040000? Is it slow if you load something to >>> the latter (make sure not to overlap with the working area)? >> >> Which reminded me that this might be a cache problem. >> >> Jon, >> can you please try loading to Kseg1, i.e. replace your addresses with >> 0xA0200000 and similar. > > 0x00200000, 0x80200000, 0xA0200000 all are the same 15 minutes > I'm loading uboot right after reset and the ROM has run. Have the > virtual segments been setup yet?
Yes, this is HW setup. > What should I be using for a work area? Exactly non-cachable region, 0xA<something>. Work area is where EJTAG miniprograms (that assembly that you see in mips32_pracc.c) > > This is something to do with reads, writes are almost instant. It is > like openocd is getting an error on every read. But nothing usual > displayed when I ran openocd -d 3 What I was most concerned is to see if mips32_pracc_fastdata_xfer() gets called, or you are reading byte by byte (long). > > What about those 18 dummy registers I had to remove into order to get > started? With them in-place I couldn't start gdb. I can try putting > them back and using direct openocd commands. Huh... I do not know much about this (did not follow all the conversation, I'll check it later), but from what I know mips used to work fine. I can guarantee only till the period of my last commit (I do not know really what was added later), so can you maybe try git reseting to that point, just to check. From what i see from git log, it is a commit 8e198e94712f8e677faffb8e0e3e9e590bae0161. BR, Drasko ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
