View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004883 | UBoot | U-Boot | public | 2021-10-04 16:47 | 2021-10-05 10:52 |
Reporter | derksen | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Target Version | fsimx8mm-Y2021.04 | Fixed in Version | fsimx8mm-Y2021.04 | ||
Summary | 0004883: fs_image.c: Have two copies of BOARD-CFG and FIRMWARE | ||||
Description | fs_image.c: Have two copies of BOARD-CFG and FIRMWARE When loading the BOARD-CFG or FIRMWARE fails, there is a second copy available. Load this second copy. - In fsimx8mm.h: have two different addresses for BOARD-CFG/FIRMWARE: CONFIG_FUS_BOARDCFG_NAND_OFFSET1, CONFIG_FUS_BOARDCFG_NAND_OFFSET2, CONFIG_FUS_FIRMWARE_NAND_OFFSET1, CONFIG_FUS_FIRMWARE_NAND_OFFSET2 Actually FIRMWARE is now immediately behind BOARD-CFG in the same NAND block, which means they always have to be written in one go. - Remove old CONFIG_SPL_BOARDCFG and CONFIG_SPL_FIRMWARE values. - Define maximum sizes CONFIG_FUS_BOARDCFG_NAND_SIZE for BOARD-CFG and CONFIG_FUS_FIRMWARE_NAND_SIZE for FIRMWARE in NAND. This is to make sure that we do not read or write beyond these limits when skipping bad blocks in NAND. - Add these CONFIG_FUS_* values to scripts/config_whitelist.txt to avoid compilation warnings. - In fs_image.c, add code to load the second copy of BOARD-CFG and FIRMWARE if the first copy fails. Fix fs_image_get_cfg_addr() that used a reverse meaning of the with_fs_header argument. - In fsimx8mm.h, remove the RAM layout for fsimx8m. This was only a reminder of how the loading could be done on i.MX8M. Update the comment for the NAND flash layout. | ||||
Forum Link | |||||