[U-Boot] list files on tftp / large kernel-image

[Frank Wunderlich]

Hi,

mw is also strange in my eyes, maybe you can explain me

U-Boot> md 80200000 18 
80200000: 616d4975 345f6567 2e34312e 750a3337    uImage_4.14.73.u
80200010: 67616d49 2e345f65 722d3431 49750a64    Image_4.14-rd.uI
80200020: 6567616d 312e345f 31312e38 6d49750a    mage_4.18.11.uIm
80200030: 5f656761 39312e34 6d2d302e 0a6e6961    age_4.19.0-main.
80200040: 616d4975 345f6567 2e39312e 63722d30    uImage_4.19.0-rc
80200050: 64682d31 0076696d ffff0000 fcffbdf7    1-hdmiv.........

U-Boot> mw.b 8020005a 0
U-Boot> md 80200000 18 
80200000: 616d4975 345f6567 2e34312e 750a3337    uImage_4.14.73.u
80200010: 67616d49 2e345f65 722d3431 49750a64    Image_4.14-rd.uI
80200020: 6567616d 312e345f 31312e38 6d49750a    mage_4.18.11.uIm
80200030: 5f656761 39312e34 6d2d302e 0a6e6961    age_4.19.0-main.
80200040: 616d4975 345f6567 2e39312e 63722d30    uImage_4.19.0-rc
80200050: 64682d31 0076696d ff000000 fcffbdf7    1-hdmiv.........

seems to set 59 (00 after ff)

U-Boot> mw.b 8020005b 0
U-Boot> md 80200000 18 
80200000: 616d4975 345f6567 2e34312e 750a3337    uImage_4.14.73.u
80200010: 67616d49 2e345f65 722d3431 49750a64    Image_4.14-rd.uI
80200020: 6567616d 312e345f 31312e38 6d49750a    mage_4.18.11.uIm
80200030: 5f656761 39312e34 6d2d302e 0a6e6961    age_4.19.0-main.
80200040: 616d4975 345f6567 2e39312e 63722d30    uImage_4.19.0-rc
80200050: 64682d31 0076696d 00000000 fcffbdf7    1-hdmiv.........

seems to set 58 (was ff before)

any idea why higher address counts backwards?

U-Boot> mw.b 8020005c 0 
U-Boot> md 80200000 18 
80200000: 616d4975 345f6567 2e34312e 750a3337    uImage_4.14.73.u
80200010: 67616d49 2e345f65 722d3431 49750a64    Image_4.14-rd.uI
80200020: 6567616d 312e345f 31312e38 6d49750a    mage_4.18.11.uIm
80200030: 5f656761 39312e34 6d2d302e 0a6e6961    age_4.19.0-main.
80200040: 616d4975 345f6567 2e39312e 63722d30    uImage_4.19.0-rc
80200050: 64682d31 0076696d 00000000 fcffbd00    1-hdmiv.........

it seems it gets first the dword at address and then sets the byte x in this dword...not as expected by me

is there a way to calculate the address (loadaddr+filesize) to pass to mw? this way works to display my textfile with strings, but calculation is a bit tricky and have to be done manually at the moment

regards Frank