Searched refs:fuses (Results 1 – 20 of 20) sorted by relevance
| /u-boot/drivers/misc/ |
| A D | rockchip-efuse.c | 56 u8 fuses[128]; in dump_efuses() local
67 ret = misc_read(dev, 0, &fuses, sizeof(fuses)); in dump_efuses()
74 print_buffer(0, fuses, 1, 128, 16); in dump_efuses()
|
| /u-boot/doc/imx/common/ |
| A D | imx6.txt | 17 For reading the MAC address fuses on a MX6Q:
29 Base address for the fuses: 0x400
33 As the fuses are arranged in banks of 8 words:
50 Base address for the fuses: 0x400
54 As the fuses are arranged in banks of 8 words:
77 Rev. 1, 04/2013" document. For example, for the MAC fuses we have:
|
| A D | imx5.txt | 36 After programming a MAC address, consider locking the MAC fuses. This is
|
| A D | mxs.txt | 258 user changes STRIDE by blowing fuses, the user also has to change
260 blowing fuses, the user also has to change "update_nand_count"
|
| /u-boot/doc/ |
| A D | README.fsl_iim | 18 Some fuse bit or word slots may not have the corresponding fuses actually
22 conventions used by U-Boot to store some specific data in the fuses, e.g. MAC
|
| A D | README.mxc_ocotp | 21 Some fuse bit or word slots may not have the corresponding fuses actually
25 conventions used by U-Boot to store some specific data in the fuses, e.g. MAC
|
| A D | README.fuse | 13 A fuse word is the smallest group of fuses that can be read at once from the
36 This is useful to know the true value of fuses if an override has been
61 fuses have already been programmed or are locked (if the SoC allows to
|
| A D | README.armada-secureboot | 292 If the SEC_FUSE_DUMP option was not set, the commands needed to burn the fuses
|
| /u-boot/board/toradex/colibri_imx6/ |
| A D | Kconfig | 38 pf0100_otp_prog - Program the OTP fuses on the PMIC PF0100
|
| /u-boot/board/toradex/apalis_imx6/ |
| A D | Kconfig | 38 pf0100_otp_prog - Program the OTP fuses on the PMIC PF0100
|
| /u-boot/board/freescale/common/ |
| A D | Kconfig | 29 values saved in SoC fuses.
|
| /u-boot/doc/imx/habv4/guides/ |
| A D | mx6_mx7_secure_boot.txt | 141 SoC SRK_HASH[255:0] fuses.
148 - Dump SRK Hash fuses values in host machine:
160 - Program SRK_HASH[255:0] fuses, using i.MX6 series as example:
246 Additional fuses can be programmed for completely secure the device, more
247 details about these fuses and their possible impact can be found at AN4581[1].
|
| /u-boot/arch/arm/mach-imx/ |
| A D | Kconfig | 103 bool "Read NXP board revision from fuses"
107 stored in the fuses. Select this option if you want to be able to
|
| /u-boot/board/boundary/nitrogen6x/ |
| A D | README.mx6qsabrelite | 44 from the fuses.
118 6. Ensure SW1 is returned to "00" to boot from the fuses once done.
|
| /u-boot/arch/arm/mach-imx/imx8/ |
| A D | snvs_security_sc.c | 814 u32 fuses[] = { in do_snvs_sec_status() local
876 for (idx = 0; idx < ARRAY_SIZE(fuses); idx++) { in do_snvs_sec_status()
877 u32 fuse_id = fuses[idx]; in do_snvs_sec_status()
|
| /u-boot/doc/imx/habv4/ |
| A D | introduction_habv4.txt | 33 binary and the SRK Hash is programmed in the SoC fuses for establishing the
235 SRK Hash is programmed in the SoC SRK_HASH[255:0] fuses.
238 SRK Table against the SoC SRK_HASH fuses, in case the verification success the
|
| /u-boot/arch/arm/dts/ |
| A D | tegra30.dtsi | 826 nvidia.xcvr-setup-use-fuses;
863 nvidia.xcvr-setup-use-fuses;
899 nvidia.xcvr-setup-use-fuses;
|
| /u-boot/drivers/nvme/ |
| A D | nvme.h | 65 __le16 fuses; member
|
| /u-boot/doc/imx/mkimage/ |
| A D | imximage.txt | 101 if the fuses for the keys are burned.
|
| /u-boot/cmd/ |
| A D | Kconfig | 930 This allows reading, sensing, programming or overriding fuses
|
Completed in 32 milliseconds