06:17 <ac_slater> hey guys. Can I stash generic data into a FDT?

06:17 <ac_slater> I love that the FDT layer can compress and validate but it doesn't seem to have a 'data' type

06:30 <ac_slater> seems "filesystem" is generic

15:31 <IoT-Maker> hi, fatls show me filenames and size. What dimension is this size? As an example, fatls show me 556 lxfs.hdr. If i load it to memory using fatload usb 0:1 0x20000000 and the show the content using md 20000000 556, the content ends at 0x20001550. I logged the content to a file and used xxd -r -seek -0x20000000 lxfs.hdr.log lxfs.hdr to make a binary. The filesize is now 5464 bytes on my filesystem. How can i

15:31 <IoT-Maker> calculate the file size 5464 from the fatls value 556?

15:35 <Tartarus> base 10 vs base 16

15:35 <Tartarus> fatls is base 10, u-boot commands take base 16

15:36 <Tartarus> also after you fatload $filesize should be set

15:37 <IoT-Maker> Tartarus, yes right. But what is the expected filesize? That one that fatls is showing me?

15:38 <Tartarus> Well, it's expected that the whole file should be loaded in to memory

15:39 <Tartarus> ie both rhash -C lxfs.hdr (in Linux) and crc32 $loadaddr $filesize should match

16:08 <IoT-Maker> my intention was to make a dump of all files via uart. I got a Drobo B810i NAS here with minimal u-boot environment. A firmwareupdate failed. The gui does not start. It's a bit tricky. It is a multistage boot process. Marvell u-boot starts, loads an VxWorks image and after that it starts a linux image. I can access both via 2 different uart ports. The linux image starts in a shell but the vxworks not. I guess that

16:08 <IoT-Maker> the VxWorks image is the one that failed after firmwareupdate.

16:10 <IoT-Maker> i want to manually load the VxWorks-backup image. But when i stop boot process to enter Marvell u-boot shell and load the image, the CPU stops at some point.

16:12 <IoT-Maker> i tried fatload usb 0:1 20000000 vxworks_prev; go 20000000

16:14 <IoT-Maker> the error is: undefined instruction

16:14 <IoT-Maker> pc : [<2000001c>] lr : [<00609ff4>], there are some sp: rl0 etc. values, at the end it'S resetting the CPU.

18:02 <IoT-Maker> sorry for dumb questions, if i load a file to ram at address 0x20000000 with size 556 bytes, reading it with md to have a dump in my logfile, do i need to clear this memory region before loading a different file? Or can i just load the next file to 0x20000000.

18:03 <cambrian_invader> you don't need to clear anything

18:03 <IoT-Maker> I read some files with the same size, It looks like the content is always the same.

19:41 <sjg1> ac_slater: FDT does not store a data type with each property, although fdtdump will infer it. The code using it needs to know the type

19:42 <sjg1> ac_slater: They have been proposals to add a data type, but nothing decided

20:13 <IoT-Maker> Seems to be a different if i use md and filesize in bytes or md.b. It works perfectly using md.b. All dumped files look usable.