t1024 flash deployment

[emras]

Hi All,

I have used as usual  NFS Deployment for development environment. Also I have tested SD Deployment.

I wonder about flash deployment. I have seen Ramdisk Deployment from Flash section in sdk documentation but it uses /dev/ram and the changes are disappear after reboot the system. I dont want this situation. How can I implement flash boot with nor or nand flashes with permanent changes. I work with T1024 yocto project and used those images, fsl-image-mfgtool-t1024rdb-64b.rootfs.tar.gz...

When I did quick search, I saw "ubifs". I need to implement ubifs for flash deployment ? is it necessary ?

Could you guide me for permanent flash boot with file system, kernel, device tree?

Thank you for your time and consideration.

[emras]

when I checked mtdparts I obtained the following result,

=> mtdparts
incorrect device type in spi0=spife110000.1

Also, in uboot there is not any command about nor , I mean there are for nand like below commands but nothing for nor flash, I want to use nor flash because nor is 128MB, nand is 64KB. Or could you guide me about how can I do?

Thank you for your consideration.

=> nand help
nand - NAND sub-system

Usage:
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read - addr off|partition size
nand write - addr off|partition size
read/write 'size' bytes starting at offset 'off'
to/from memory address 'addr', skipping bad blocks.
nand read.raw - addr off|partition [count]
nand write.raw[.noverify] - addr off|partition [count]
Use read.raw/write.raw to avoid ECC and access the flash as-is.
nand erase[.spread] [clean] off size - erase 'size' bytes from offset 'off'
With '.spread', erase enough for given file size, otherwise,
'size' includes skipped bad blocks.
nand erase.part [clean] partition - erase entire mtd partition'
nand erase.chip [clean] - erase entire chip'
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub [-y] off size | scrub.part partition | scrub.chip
really clean NAND erasing bad blocks (UNSAFE)
nand markbad off [...] - mark bad block(s) at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
=>

[emras]

Thanks ufedor,

I have checked again and again I have not seen 128 MB any file, when I checked system memory map just IFC-NOR Flash is 128 MB but it is a definition not an image. Also what image did you mean? uboot image or kernel image or file system.. the first link refers to flash memory usage not a how to work with flash with permanent file system. Also I think I need to do something in uboot like /dev/ram (but it is temporary). Could you guide me much more?

Thank you for your time and consideration.

[ufedor]

Please refer to the SDK documentation describing the NOR Flash memory map:

https://docs.nxp.com/bundle/GUID-39A0A446-70E5-4ED7-A580-E7508B61A5F1/page/GUID-9D0808B4-40A3-48AD-9...

Also you can refer or use "as is" complete 128 MB NOR Flash binary image provided in the "QorIQ Linux SDK v2.0 PPC64E5500 IMAGE.iso" available for free download from:

https://www.nxp.com/design/software/embedded-software/linux-software-and-development-tools/linux-sdk...

[emras]

Thanks ufedor,

I have checked again and again I have not seen 128 MB any file, when I checked system memory map just IFC-NOR Flash is 128 MB but it is a definition not an image. Also what image did you mean? uboot image or kernel image or file system.. the first link refers to flash memory usage not a how to work with flash with permanent file system. Also I think I need to do something in uboot like /dev/ram (but it is temporary). Could you guide me much more?

Thank you for your time and consideration.