imx6sx fuses issue

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

imx6sx fuses issue

1,178 Views
ambroiseaa
Contributor I

Hi,

We're working on a custom board based on imx6sx MCIMX6X1CVO08AB. Everythings working good and now we'd like to boot from a SDcard on SD4 port using eFUSES.

We are using uboot version 2015.04 from freescale.

We used the command : "fuse prog 0 5 0x00003841" to configure the eFUSE (we haven't imxotp command). Then setting boot pin to 00 (fuses mode).

This command works. But on next boot nothing happened. We have chance, internal mode works on GPIOs fuses so the board is not dead!

What was wrong with this command ? Did we forget something ? Can we modify the actual eFUSEs configuration or not?

Thanks for your help,

Labels (1)
0 Kudos
2 Replies

634 Views
igorpadykov
NXP Employee
NXP Employee

Hi ambroiseaa

seems this command is used in mainline uboot

http://boundarydevices.com/fuse-command/

so one can post question on uboot mailing list

U-Boot Info Page

or try uboot from Freescale official BSP (using imxotp command)

Board Support Packages (27)

SABRE Board Reference Design|Freescale

L3.14.28_1.0.0_iMX6SX_BUNDLE (REV L3.14.28_1.0.0)

i.MX 6SoloX Linux Binary Demo Files and Linux BSP Documentation

Differencies between Freescale official BSPs and Community releases is described on

Re: difference between Yocto Community BSP and Freescale BSP Release

One can check if fuse is programmed correctly with imxotp read command :

https://community.freescale.com/docs/DOC-95458

After boot fail one can connect jtag and check boot configuration (it is copied from fuses)

in registers SRC_SBMR1,2

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

634 Views
ambroiseaa
Contributor I

Thanks for your answer,

We find our mistake : we didn't program the fuse BT_FUSE_SEL

the command "fuse prog 0 6 0x00000010" solved the problem.

0 Kudos