summaryrefslogtreecommitdiff
path: root/board/beckhoff/mx53cx9020/mx53cx9020_video.c
diff options
context:
space:
mode:
authorMax Krummenacher <max.krummenacher@toradex.com>2019-02-08 18:12:22 +0100
committerStefano Babic <sbabic@denx.de>2019-04-13 20:30:08 +0200
commit5135db4d8b6def5eda4e47ca3f97b38fd7bc7702 (patch)
treec4251fb8b5a7d69bb5b581f90d6f2419a2802b25 /board/beckhoff/mx53cx9020/mx53cx9020_video.c
parent389f61ef44fd032ae5efd3995623842d9281b4c1 (diff)
apalis_imx6: revert fuse value set in mfgr_fuse
We have two commands to change the bootmode fuses: mfgr_fuse which set fuse 0/5 and 0/6 and updt_fuse which burns bit 4 of 0/5. Before BSP 2.6 we fused in mfgr_fuse 0x5062, which boots from the user partition of the eMMC. To workaround certain hangs we moved to fastboot mode and using the first bootpartition of the eMMC requiring a fuse value of 0x5072 which could be achieved by the then added updt_fuse command. At the same time the mfgr_fuse command was changed to also fuse 0x5072, revert that second change so that one can fuse both values, one with just mfgr_fuse and the later with mfgr_fuse;updt_fuse. Note that the mfgr_fuse command is only needed at module production time, a customer might need to use updt_fuse when upgrading an older module to be compatible with a newer image. The command is integrated into the image update scripts. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Acked-by: Stefan Agner <stefan.agner@toradex.com> Acked-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
Diffstat (limited to 'board/beckhoff/mx53cx9020/mx53cx9020_video.c')
0 files changed, 0 insertions, 0 deletions