On 02/16/2015 08:13 AM, Przemyslaw Marczak wrote:
This patchset reduces the boot time for ARM architecture, Exynos boards, and boards with DFU enabled.
I tested this series on NVIDIA's Jetson TK1 board. It doesn't seem to introduce any new issues, but I did find a couple have crept in recently:
I'm running the following in U-Boot:
setenv dfu_alt_info "/dfu_test.bin ext4 0 1;/dfudummy.bin ext4 0 1" dfu 0 mmc 0
1)
Whenever any file is uploaded through DFU, I see:
#File System is consistent file found deleting update journal finished File System is consistent update journal finished 18425346722729591336 bytes written in 4070 ms (3.9 EiB/s)
Notice that the byte count is way off (that's from a 4KB file). The byte count is always the same invalid number. I'm not sure if this message comes from the ext4 or DFU code.
2)
Both the 4096 and 1048576 DFU tests fail in the read-back stage, with the following appearing on the U-Boot console:
#File System is consistent file found deleting update journal finished File System is consistent update journal finished 18425346722734241092 bytes written in 4070 ms (3.9 EiB/s) DOWNLOAD ... OK Ctrl+C to exit ... #File System is consistent file found deleting update journal finished File System is consistent update journal finished 18425346722734241092 bytes written in 4091 ms (3.9 EiB/s) DOWNLOAD ... OK Ctrl+C to exit ... 4096 bytes read in 127 ms (31.3 KiB/s) # UPLOAD ... done Ctrl+C to exit ... 4096 bytes read in 126 ms (31.3 KiB/s) #dfu_read: Wrong sequence number! [1] [3]
The host-side DFU test log ends with:
Opening DFU USB device... ID 0955:701a Warning: Assuming DFU version 1.0 Run-time device DFU version 0100 Found DFU: [0955:701a] devnum=0, cfg=1, intf=0, alt=0, name="/dfu_test.bin" Claiming USB DFU Interface... Setting Alternate Setting #0 ... Determining device status: state = dfuIDLE, status = 0 dfuIDLE, continuing DFU mode device DFU version 0110 Device returned transfer size 4096 bytes_per_hash=4096 Copying data from DFU device to PC Starting upload: [###dfu_upload: libusb_control_msg returned -9