[U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux

Hi There ! I'm seeing a strange problem with u-boot 2018.1 and Linux 4.14 (Xilinx Petalinux 2018.1). If I write a ubifs image to flash using Linux 4.9 I can mount and read files from the image in both u-boot 2018.1 and Linux 4.14. However as soon as I write a new file to the file-system from Linux

Re: [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux

Hallo Heiko & Richard ! Turns out the len and out_len do not match, much like you suspected. Out_len is 2 bytes short (4094 vs 4096) See log below UBIFS DBG tnc: search key (5725, data, 124) UBIFS DBG tnc: found 1, lvl 0, n 2 UBIFS DBG tnc: LEB 566:61864, key (5725, data, 124) UBIFS DBG io: LEB 5

Re: [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux

Hi Richard ! Correct, the first error is printed in U-boot 2018.1 (which also matches the error I see if I try to read the file in Linux 4.9). The ubi file is created using Yocto 2.4.1 (comes with PetaLinux 2018.1) with the following settings MKUBIFS_ARGS = " -m 2048 -e 126976 -c 4096 -x lzo " U

Re: [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux

time ! /Otto On Sat, May 19, 2018 at 1:37 AM, Richard Weinberger wrote: > Am Samstag, 19. Mai 2018, 01:56:33 CEST schrieb Otto Blom: >> UBIFS error (ubi0:0 pid 0): crypto_comp_decompress: cannot decompress >> 2801 bytes, compressor lzo, error -6 > > LZO_E_LOOKBEHIND_OV

Re: [U-Boot] UBIFS Problems with U-boot 2018.1 & 4.14 Linux

gt;> >> Am Dienstag, 22. Mai 2018, 03:30:04 CEST schrieb Otto Blom: >>> >>> Hi Richard ! >>> >>> To summarize the observations from the last few days. >>> >>> * Linux 4.9 & U-boot 2018 behave the same when attempting to read