Logs are too big for the mailing list. Below is my e-mail without logs. Regards, Pieter
-----Original Message----- From: Pieter Conradie Sent: 02 November 2009 09:49 AM To: 'Øyvind Harboe' Cc: openocd-development@lists.berlios.de Subject: RE: [Openocd-development] openocd-0.3.0-rc0 bug: Fail to write to Intel NOR Flash on AT91SAM9260 Hi Øyvind, Attached are the logs for 2645 and 2646. Hope it helps! I did testing on the following revisions: 0.2.0: works 0.3.0-rc: broken SVN1399: works SVN2600: works SVN2617: works SVN2636: works SVN2638: works SVN2641: works SVN2643: works SVN2644: works SVN2645: works SVN2646: broken SVN2656: broken It appears that SVN2646 did break it. Best regards, Pieter -----Original Message----- From: Øyvind Harboe [mailto:oyvind.har...@zylin.com] Sent: 30 October 2009 07:23 PM To: Pieter Conradie Cc: openocd-development@lists.berlios.de Subject: Re: [Openocd-development] openocd-0.3.0-rc0 bug: Fail to write to Intel NOR Flash on AT91SAM9260 > SVN 2645: writes 512k to flash, verifies correctly > SVN 2646: flash write_image fails with "timed out while waiting for target > debug-running" Hmm..... this is trickier than I thought.... Can you provide debug_level 3 logs for 2645 and 2646? Try to use the *EXACT* same procedure so the logs can be diff'ed using text diff... (With a bit of manual tinkering...) I see from the log that the the hardware breakpoint is set correctly and that the CPU halts at the address after the DCC algorithm(0x850). The DCC algorithm should run indefinitely until halted when all data has been written to memory... I'm stumped as to what this might have to do with 2645 and 2646.... Except if hw breakpoints were *broken* somehow in 2645 and that hides some other problem that 2645 is somehow able to recover from.... I/D caches appear to be disabled... Is it conceivable that 2645 is in fact broken too and that something conspired to make the test come out as a false positive? -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer Notice This email is intended for the addressee only and may contain legally privileged and/or confidential information. If you have received this email in error and are not the intended recipient, you are hereby informed that you are not entitled to read, broadcast, distribute or in any manner whatsoever use the contents of this email or any attachments thereto. You are requested to please notify Psitek that you have received the email and then delete it. Unless clearly stated otherwise, the content and sentiments expressed in this email or any attachments thereto are those of the sender and not of Psitek (Proprietary) Limited. Psitek does not accept liability for any damages, loss or expense of any nature whatsoever arising (a) out of or in connection with the email or any attachments thereto and/or (b) from any act or omission by the recipient relying upon the content of the email or attachments. Psitek further disclaims liability for any damages caused by computer and/or software viruses. Should this email contain the terms of a contract, no binding agreement will result until such time as a written (hardcopy) document is signed on behalf of Psitek. _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
