Hi Oyvind, I agree wholeheartedly. I'm looking into it... I'm going to probably have to take blame for configuration file differences... I realized that in my systematic testing at version 826 I started having to futz with my configurations a bit to get things running (hmmh, so not really so systematic).
i've installed the latest svn head and am re-analyzing my configurations... As I wrote this email: I'm blue in the face. i think i forgot a line of code... jtag_speed 0 in my olimex-arm-usb file... however, the flashing worked a single time then failed on the latest trunk. now i'm getting a segmentation fault. *shakes his head in confusion* any tips on how to verify that my configs are working? i can erase the flash, i can read the flash... but i just can't seem to write it? "Anyone who has never made a mistake has never tried anything new." - Albert Einstein On Thu, Nov 6, 2008 at 2:45 PM, Øyvind Harboe <[EMAIL PROTECTED]> wrote: > On Thu, Nov 6, 2008 at 2:17 PM, Federico Spadini <[EMAIL PROTECTED]> wrote: >> Hey Guys, >> So to respond, r826 is the first point of failure I found (825 works >> and flashes) 826 fails and does not flash. > > It is inconceivable (ref. The Princess Bride) that the problem was introduced > with 826. > > If you do find that 826 introduces the problem, can you create a patch > against 825 which contains *only* the changes that breaks 825? > > This is very strange indeed. > > -- > Øyvind Harboe > http://www.zylin.com/zy1000.html > ARM7 ARM9 XScale Cortex > JTAG debugger and flash programmer > > _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
