On 2011-07-22 17:30, Andreas Fritiofson wrote:
According to objdump, the completely different hex file is located in RAM:
Oops (; Indeed it is - I forgot that it's from a project I recently
experimented on... Sorry for the mess (;
So - I cannot confirm the issue, it works for me with 0.4.0 -
On Fri, Jul 22, 2011 at 4:57 PM, Freddie Chopin wrote:
> On 2011-07-21 23:02, Andreas Fritiofson wrote:
>
>> However I can't explain Freddie's reproduced failures. Maybe post the
>> hex files (matching, slightly different and very different) and I can
>> see if I can take a closer look at it?
>>
>
On Thu, Jul 21, 2011 at 10:44 PM, Magnus S. wrote:
> Freddie Chopin writes:
>
> >
> > I can partially confirm...
> >
> > Tested with 0.5.0-rc1
> >
> > Comparing with "right image" works fine:
> >
> >
> > Comparing with "almost right image" (compilation date inside has
> > changed) works fine too
Freddie Chopin writes:
>
> I can partially confirm...
>
> Tested with 0.5.0-rc1
>
> Comparing with "right image" works fine:
>
>
> Comparing with "almost right image" (compilation date inside has
> changed) works fine too:
>
>
> However... when checking against something completely wrong (
I can partially confirm...
Tested with 0.5.0-rc1
Comparing with "right image" works fine:
verify_image c://stm32_blink_led.bin 0x800
verified 29888 bytes in 0.468750s (62.267 KiB/s)
verify_image c://stm32_blink_led.bin
verified 29888 bytes in 0.484375s (60.258 KiB/s)
verify_image c://s
