Am 17.03.2016 um 13:55 schrieb Bernhard Nortmann:
I can confirm/reproduce this behaviour on my A20 when accessing the
SID register. Interesting enough, the bytes that actually do get read
(i.e. end up != 0) are "correct", as if the aw_usb_read() somehow
truncates everything down to single-byte range:
sunxi-tools # ./sunxi-fel hexdump 0x01c23800 16
01c23800: 4f 00 00 00 86 00 00 00 48 00 00 00 e9 00 00 00
Btw: This "MSB zero" problem doesn't seem related to the FEL protocol in
any way, but looks like a more general hardware limitation. U-Boot's
memory display exposes the very same quirk when not accessing the SID
registers as "long" (i.e. 32-bit) values:
=> md.l 0x01c23800 4
01c23800: 1651664f 80485686 53504848 0702dde9 OfQ..VH.HHPS....
=> md.w 0x01c23800 8
01c23800: 664f 0000 5686 0000 4848 0000 dde9 0000 Of...V..HH......
=> md.b 0x01c23800 10
01c23800: 4f 00 00 00 86 00 00 00 48 00 00 00 e9 00 00 00 O.......H.......
Regards, B. Nortmann
--
You received this message because you are subscribed to the Google Groups
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
