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

[Simon Goldschmidt]

Am 02.12.2018 um 10:33 schrieb Frank Wunderlich:
> can you give me an example how to download and display it, seems i only have tftpboot which runs kernel directly?
> 
> also found no strings-command in https://www.denx.de/wiki/DULG/Manual

=> tftp ${loadaddr} 192.168.1.1:list.txt
Speed: 100, full duplex
Using ethernet at ff702000 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.101
Filename 'list.txt'.
Load address: 0x1000000
Loading: #
          12.7 KiB/s
done
Bytes transferred = 158 (9e hex)
=> strings ${loadaddr} 9e
dhcppkgstyle.xsl
dhcpstyle.xsl
favicon.ico
index.html
ldlinux.c32
list.txt
mini.iso
netboot.tar.gz
pxelinux.0
pxelinux.cfg
RJ45_5.JPG
RJ45_52.JPG
  ã(Ðå
=>

The 'strings' command has to be enabled under "Command line interface" 
-> "Memory commands". It helps to show the contents, but not really for 
scripting...

Simon

> 
> Frank
> 
>> Gesendet: Montag, 19. November 2018 um 12:29 Uhr
>> Von: "Simon Goldschmidt" <simon.k.r.goldschmidt at gmail.com>
>> An: "Frank Wunderlich" <frank-w at public-files.de>
>> Cc: "U-Boot Mailing List" <u-boot at lists.denx.de>
>> Betreff: Re: Re: [U-Boot] list files on tftp / large kernel-image
>>
>> On Wed, Nov 14, 2018 at 4:52 PM Frank Wunderlich
>> <frank-w at public-files.de> wrote:
>>>
>>> Hi Simon,
>>> thanks for fast answer
>>>
>>> i hope mediatek release ethernet soon (i know it's a more complex driver for r2 than the other 18 patches ), than i can drop the old uboot ;)
>>>
>>> for list tftp, it seems to be a protocol limitation.
>>> here https://unix.stackexchange.com/questions/76400/download-directory-structure-from-a-tftp-server the server creates a textfile...this can be a workaround
>>>
>>> can i download (to memory) and display it (without writing it)? i only have loaded kernel and executed it's address. I don't know how to print a "Textfile" (if it's in memory i need to know it's size and print this "data block"). maybe there is a way to load the data directly to an env-var
>>
>> Have you tried the 'strings' command? Is that enough?
>>
>> Simon
>>