Hello,

this message should be only visible if the debug output enabled. If you have 
usb read/write problems
sometimes, this is the point you have to look.


Regards,

Mathias

Am 03.03.2011 10:19, schrieb Jon Povey:
> Since 6ddcee7d20ee873f1c214736c22f29d9781dded4
> 
> When I try to read memory, I get "read buffer size looks to high"
> (I suppose that should be "too" instead of "to")
> 
> e.g. amontec jtagkey, TI DM355 (ARM926EJ-S)
> 
>> mdb 0 64
> read buffer size looks to high
> read buffer size looks to high
> read buffer size looks to high
> 0x00000000: fe 1f 00 ea fd 1f 00 ea fc 1f 00 ea 04 f0 5e e2 08 f0 5e e2 f9 1f 
> 00 ea f8 1f 00 ea e0 27 00 ea
> 0x00000020: 29 0b 00 00 00 00 00 00 31 0f 09 ee 11 0f 19 ee 38 00 9f e5 1d 00 
> 80 e3 11 0f 09 ee 34 00 9f e5
>>
> 
> As a user, how am I supposed to react to this message?
> It's rather opaque. And things still seem to work.
> So far just noticed it on longish memory dumps.
> 
> --
> Jon Povey
> [email protected]
> 
> Racelogic is a limited company registered in England. Registered number 
> 2743719 .
> Registered Office Unit 10, Swan Business Centre, Osier Way, Buckingham, 
> Bucks, MK18 1TB .
> 
> The information contained in this electronic mail transmission is intended by 
> Racelogic Ltd for the use of the named individual or entity to which it is 
> directed and may contain information that is confidential or privileged. If 
> you have received this electronic mail transmission in error, please delete 
> it from your system without copying or forwarding it, and notify the sender 
> of the error by reply email so that the sender's address records can be 
> corrected. The views expressed by the sender of this communication do not 
> necessarily represent those of Racelogic Ltd. Please note that Racelogic 
> reserves the right to monitor e-mail communications passing through its 
> network
> 
> 
> 

_______________________________________________
Openocd-development mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/openocd-development

Reply via email to