Talk:Dfu-util

From Openmoko

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
Is there any particular reason for the "NOTE: You cannot transfer more than 2MB of data into RAM using this method"?  I had no problem transferring a 29 MB file to the RAM.  I recognise 32 MB (size which latest rootfs builds have crossed recently) will be a problem because the u-boot's stack or other section starts at 0x34000000.  Moving the RAM download address in DFU to 0x31000000 seems to work around that though. [[User:Balrog|balrog]] 14:37, 12 June 2007 (CEST)
 
Is there any particular reason for the "NOTE: You cannot transfer more than 2MB of data into RAM using this method"?  I had no problem transferring a 29 MB file to the RAM.  I recognise 32 MB (size which latest rootfs builds have crossed recently) will be a problem because the u-boot's stack or other section starts at 0x34000000.  Moving the RAM download address in DFU to 0x31000000 seems to work around that though. [[User:Balrog|balrog]] 14:37, 12 June 2007 (CEST)
 +
 +
I can verify that the latest dfu-util does not work with big-endian (host running dfu-util).
 +
Transfer size is obtained as 0x0010 instead of 0x1000.
 +
Oh, I see that the usb wire encoding convention is apparently little endian, not network byte order. :(
 +
Is transfer size the only one that needs to be swapped? It seemed to be the only one specifically marked with a Endian-todo comment. [[User:Don|Don]] 17:41, 31 July 2007 (CEST)

Revision as of 17:41, 31 July 2007

Is there any particular reason for the "NOTE: You cannot transfer more than 2MB of data into RAM using this method"? I had no problem transferring a 29 MB file to the RAM. I recognise 32 MB (size which latest rootfs builds have crossed recently) will be a problem because the u-boot's stack or other section starts at 0x34000000. Moving the RAM download address in DFU to 0x31000000 seems to work around that though. balrog 14:37, 12 June 2007 (CEST)

I can verify that the latest dfu-util does not work with big-endian (host running dfu-util). Transfer size is obtained as 0x0010 instead of 0x1000. Oh, I see that the usb wire encoding convention is apparently little endian, not network byte order. :( Is transfer size the only one that needs to be swapped? It seemed to be the only one specifically marked with a Endian-todo comment. Don 17:41, 31 July 2007 (CEST)

Personal tools

Is there any particular reason for the "NOTE: You cannot transfer more than 2MB of data into RAM using this method"? I had no problem transferring a 29 MB file to the RAM. I recognise 32 MB (size which latest rootfs builds have crossed recently) will be a problem because the u-boot's stack or other section starts at 0x34000000. Moving the RAM download address in DFU to 0x31000000 seems to work around that though. balrog 14:37, 12 June 2007 (CEST)

I can verify that the latest dfu-util does not work with big-endian (host running dfu-util). Transfer size is obtained as 0x0010 instead of 0x1000. Oh, I see that the usb wire encoding convention is apparently little endian, not network byte order. :( Is transfer size the only one that needs to be swapped? It seemed to be the only one specifically marked with a Endian-todo comment. Don 17:41, 31 July 2007 (CEST)