Can anyone help me understand why common/env_nand.c has bad block
handling, but common/env_sf.c does not?
env_nand.c writes uboot environment to nand flash and explicitly skips
bad blocks.
env_sf.c also writes writes uboot environment to flash, but does not
have any bad block handling.
For my boar
On Thu, May 4, 2017 at 12:58 PM, Walter Heck wrote:
> Hi all,
>
> I'm completely new to the world of U-boot, so please forgive me if I spout
> nonsense. I'm looking for a bit of guidance.
>
> I'm reverse engineering an old Philips 10FF2 Photoframe, hoping to one day
> customize it, just for the fu
I am running into errors after creating a UBI filesystems on our NAND
device. Can anyone suggest where I might look for the error?
A summary is included below and complete debug logs can be seen at
https://gist.github.com/263e422eefa1401db68565fa3e4149bd
After reset, the low-level `nand` command
I don't know the protocol for revisiting broken patches that have
already been integrated, but the patched offered by NXP for their
ls1046a RDB is wrong.
original patch:
http://lists.denx.de/pipermail/u-boot/2016-September/265974.html
The main error is this patch defines CONFIG_SPI_FLASH_BAR whic
4 matches
Mail list logo