On Mon, Apr 4, 2011 at 7:54 PM, Andrew Lyon <andrew.l...@gmail.com> wrote:
> On Mon, Apr 4, 2011 at 6:51 PM, Øyvind Harboe <oyvind.har...@zylin.com> wrote:
>> Any objections to merging 1,2 and 4?
>>
>> I think #3 needs more discussion or cool-off. My objection is
>> that we don't know why this makes things better and it certainly
>> seems to hit performance hard.
>>
>>
>> --
>> Øyvind Harboe
>>
>> Can Zylin Consulting help on your project?
>>
>> US toll free 1-866-980-3434 / International +47 51 87 40 27
>>
>> http://www.zylin.com/zy1000.html
>> ARM7 ARM9 ARM11 XScale Cortex
>> JTAG debugger and flash programmer
>> _______________________________________________
>> Openocd-development mailing list
>> Openocd-development@lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/openocd-development
>>
>
> Hi,
>
> I did some more testing loading much larger images (3226774 bytes) and
> found that both with and without patch #3 the image fails to load
> properly, attempting to bootm the uImage uboot detected bad crc and
> aborted, and verify_image also fails and starts a slow compare that
> would take all night to run.
>
> I can load the same image into ram using uboot and y-modem over
> serial, so there is clearly nothing wrong with the ram setup etc.
>
> Not sure how to approach debugging this further so any advice would be
> appreciated.
>
> Andy
>

I scripted some tests which ran overnight and are still running,
basically just a cycle of cat uboot >>testfile ; load_image ;
verify_image so that the test binary grew by 118k between each run and
I am now close to identifying the point at which images are too big
for me to load successfully:

3226774 uImage fails to load
3089528 testimagerandomuboots loads successfully

I've changed my script to load each of these several times to make
sure the failure is consistent, then I will change to bisecting
between the two file sizes to identify the failure point.

Andy
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to