Guide to the .sdcard format

cancel
Showing results for 
Search instead for 
Did you mean: 

Guide to the .sdcard format

No ratings

Guide to the .sdcard format

Understanding and using the .sdcard format

One very useful feature enabled by default in both the Yocto Communiy BSP and Release BSP is the option of generating the baked images in .sdcard format.

If the .sdcard format is not selected by default it can be enabled on the conf/local.conf file by adding it with the IMAGE_FSTYPES as follow:

IMAGE_FSTYPES="sdcard"

It’s important to note that if this variable is specified only the file systems typed defined will be created. The default value used most often for this variable is:

IMAGE_FSTYPES="tar.bz2 ext3 sdcard"

The .sdcard format creates an image with all necessary partitions and loads the bootloader, kernel and rootfs to this image. You can just low level copy the data on this file to the SD card device using dd as on the following command example:

$ sudo dd if=<image name>.sdcard of=/dev/sd<partition> bs=1M && sync

Partitions used on the .sdcard file

The .sdcard partitions looks as follow:

SD_Card_Partitions.jpg

IMAGE_ROOTFS_ALIGNMENT
Unpartitioned space reserved for the bootloader

BOOT_SPACE
Kernerl and other data

ROOTFS_SIZE
The rootfs.

Granting more free space on the RootFS partition

The size of the .sdcard file will depend solely on the size of the rootfs. This means that the resulting file won’t partition all our SD Card capacity unless we add extra space to the rootfs partition. (Of course there is always the option of editing the partitions once loaded on the SD Card)

In order to add more space you may use the IMAGE_ROOTFS_EXTRA_SPACE variable. You may add it to your local.conf file with the added free disk space in Kbytes. For example, if you would like to guarantee 1GB of extra space you may add the following line to your local.conf file.

IMAGE_ROOTFS_EXTRA_SPACE = "1048576"

It is important to note that this is space additional to the IMAGE_OVERHEAD_FACTOR variable which defines a multiplier that is applied to the initial image size. This is only applied when the multiplier times the

By default, the build process uses a multiplier of 1.3 for this variable. This default value results in 30% free disk space added to the image when this method is used to determine the final generated image size. This would mean that there should be 30% of free disk space before post install scripts. If you wish for more space you may edit this variable as bellow:

IMAGE_OVERHEAD_FACTOR = "1.5"

Which would result in 50% free disk space added to the image, before post install scripts and without considering overhead that may come from the package management system.

How the IMAGE_ROOTFS_SIZE is calculated

This variable is also measured in Kbytes and it’s determined by the OpenEmbedded build system using an algorithm that considers the initial disk space used for the generated image, the requested size for the image (trough the overhead factor) and the additional free space to be added to the image (trough the extra space variable).

The build system first runs a du (disk usage) command to determine the size of the rootfs directory tree. If the IMAGE_ROOTFS_SIZE current value is larger than the disk usage times the overhead factor only the extra space is added. If the IMAGE_ROOTFS_SIZE is smaller than the disk usage times the overhead factor then the disk usage is multiplied times the overhead factor prior to adding the extra space.

IMAGE_ROOTFS_SIZE must be set on a default value which is usually very low as it’s just initialized and updated with the actual size requirements each time an image is baked.

You may also use this variable directly in order to select the space you would like to allocate to the RootFS.For example setting the RootFS to 2GB would require the following addition to the local.conf file:

IMAGE_ROOTFS_SIZE = “2097152”
IMAGE_OVERHEAD_FACTOR = “1.0”

In this example we would leave the overhead factor to 1 so no extra space is added since we’re specifying the rootfs size that we want.

Comments

SergioSolisCarlosCasillasjamesbonealejandrolozano

Would you please give the document a look and let me know what you think? Any feedback is very much appreciated!

BTW, would anyone please mention Alfredo? I cannot get to mention him correctly.

Great document Gustavo.

Very good document!

Very good document, especially, the topic about expanding the partition capacity, which seems to be a FAQ.

Thank you very much for your feedback!

Bio_TICFSL​, I finally was able to mention you. Would you please provide comments on this document?

Hi gusarambula​, this is document include very important and useful information, hope to next time you can explain us in a tutorial, all the options that can apply to SDs with i.MX with command "dd".

please keep the hard working

Hello,

Is this feature still available in yocto 2.1 ?

I add sdcard in IMAGE_FSTYPES in my conf/local.conf but it generates following error :

ERROR: /opt/angstrom-v2016.06-yocto2.1/layers/meta-linaro/meta-linaro/recipes-linaro/images/linaro-sysroot-lamp.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdcard' - possibly invalid type name or missing support class
ERROR: Failed to parse recipe: /opt/angstrom-v2016.06-yocto2.1/layers/meta-linaro/meta-linaro/recipes-linaro/images/linaro-sysroot-lamp.bb
ERROR: /opt/angstrom-v2016.06-yocto2.1/layers/meta-linaro/meta-linaro/recipes-linaro/images/linaro-sysroot-alip.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdcard' - possibly invalid type name or missing support class
ERROR: /opt/angstrom-v2016.06-yocto2.1/layers/meta-linaro/meta-linaro/recipes-linaro/images/linaro-image-toolchain-benchmark.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdcard' - possibly invalid type name or missing support class
ERROR: /opt/angstrom-v2016.06-yocto2.1/layers/meta-linaro/meta-linaro/recipes-linaro/images/linaro-image-sdk.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdcard' - possibly invalid type name or missing support class
ERROR: /opt/angstrom-v2016.06-yocto2.1/layers/meta-linaro/meta-linaro/recipes-linaro/images/linaro-image-minimal.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdcard' - possibly invalid type name or missing support class
ERROR: /opt/angstrom-v2016.06-yocto2.1/layers/meta-linaro/meta-linaro/recipes-linaro/images/linaro-image-minimal-ltp.bb: No IMAGE_CMD defined for IMAGE_FSTYPES entry 'sdcard' - possibly invalid type name or missing support class

Many thanks for help

Hello everyone,

I got just a question relating this.

Would it also be possible to add an extra partition using this system easily ? 

My goal is to use IMAGE_FEATURE = read-only-roofts but I also want an other mounting point where my app can write.

Thanks,

Jérôme.

jtis‌ I have the same question.  I'm trying to do the exact same thing. 

Hello,

My solution was to add my own function IMAGE_POSTPROCESS_COMMAND in the image recipe and create a partition with fdisk (see partitioning - Creating and formating a partition using a bash script - Super User )

I haven't found any other solution. This is a bit rough but it is working.

Jérôme.

It turns out that the manufacturing tool can also create multiple partitions if you change the manufacturing tool script.  The documentation is included with the manufacturing tool download.  I was planning to use the *.sdcard image to program the eMMC on my device, and needed to use the manufacturing tool for that anyway.  The default settings in the manufacturing tool don't even use the *.sdcard image so I guess I don't need this specific problem solved now. 

Could you please share your solution?  Thanks

Is this being phased out in favor of "WIC" format?  The rocko repo doesn't build .sdcard files by default.

Anyone know if there is a similar description of the WIC file format and how to use it?

To answer my comment: the Yocto Project page has some description how to use .wic files:

Yocto Project Development Manual 

See "Flashing Images Using bmaptool"

Based on the first paragraph, this doc seems to be saying that any of these variables should be added to conf/local.conf.

However, when I add

IMAGE_ROOTFS_SIZE = “2097152”
IMAGE_OVERHEAD_FACTOR = “1.0”

to my conf/local.conf file, I get the bitbake error:

ERROR: ParseError at /home/user/yocto/build/conf/local.conf:26: unparsed line: 'IMAGE_ROOTFS_SIZE = “2097152”'

Probably you copy pasted the command 'IMAGE_ROOTFS_SIZE = “2097152”' from the web page and it has wrong double quota character ( “ ).  Replace it by linux double quota " and Parse Error will disappear.

Hello,

which sdcard(RAW, ext4, FAT32) partition is suitable for .sdcard file.

I'm using yocto build .sdcard file, getting error on booting sequence

for build yocto i'm using core-image-base

After build i'm getting this two file on temp:

1)core-image-base-imx7ulpevk.sdcard

2)core-image-base-imx7ulpevk-20190125080535.rootfs.sdcard

U-Boot 2017.03-00886-gb76bb1bf9f-dirty (Jan 25 2019 - 17:56:02 +0530)

CPU: Freescale i.MX7ULP rev2.0 at 500 MHz
Reset cause: UNKN-10016
Boot mode: Single boot
Model: NXP i.MX7ULP EVK
DRAM: 1 GiB
MMC: FSL_SDHC: 0
*** Warning - bad CRC, using default environment

No panel detected: default to HX8363_WVGA
Display: HX8363_WVGA (480x854)
Video: 480x854x24
In: serial
Out: serial
Err: serial
Net: Net Initialization Skipped
No ethernet found.
Normal Boot
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc0 is current device
reading boot.scr
** Unable to read file boot.scr **
reading zImage
7248912 bytes read in 358 ms (19.3 MiB/s)
Booting from mmc ...
reading imx7ulp-evk.dtb
21688 bytes read in 17 ms (1.2 MiB/s)
Kernel image @ 0x60800000 [ 0x000000 - 0x6e9c10 ]
## Flattened Device Tree blob at 63000000
Booting using the fdt blob at 0x63000000
Using Device Tree in place at 63000000, end 630084b7

Starting kernel ...

Booting Linux on physical CPU 0xf00
Linux version 4.14.78-imx_4.14.78_1.0.0_ga+g66620c3d281c (oe-user@oe-host) (gcc version 7.3.0 (GCC)) #1 SMP PREEMPT Fri Jan 25 09:35:37 UTC 2019
CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c53c7d
CPU: div instructions available: patching division code
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt: Machine model: NXP i.MX7ULP EVK
Memory policy: Data cache writealloc
Reserved memory: created CMA memory pool at 0x92000000, size 192 MiB
OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool
DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
percpu: Embedded 16 pages/cpu @bf678000 s35532 r8192 d21812 u65536
Built 1 zonelists, mobility grouping on. Total pages: 259842
Kernel command line: console=ttyLP0,115200 root=/dev/mmcblk0p2 rootwait rw
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 826096K/1047552K available (9216K kernel code, 505K rwdata, 3200K rodata, 1024K init, 442K bss, 24848K reserved, 196608K cma-reserved, 0K highmem)
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xc0000000 - 0xff800000 (1016 MB)
lowmem : 0x80000000 - 0xbff00000 (1023 MB)
pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)
modules : 0x7f000000 - 0x7fe00000 ( 14 MB)
.text : 0x80008000 - 0x80a00000 (10208 kB)
.init : 0x80e00000 - 0x80f00000 (1024 kB)
.data : 0x80f00000 - 0x80f7e640 ( 506 kB)
.bss : 0x80f80000 - 0x80fee8e0 ( 443 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1.
Tasks RCU enabled.
RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
i.MX7ULP clock tree init done.
Switching to timer-based delay loop, resolution 333ns
sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 715827882841ns
clocksource: imx-tpm: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 637086815595 ns
Console: colour dummy device 80x30
Calibrating delay loop (skipped), value calculated using timer frequency.. 6.00 BogoMIPS (lpj=30000)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
CPU: Testing write buffer coherency: ok
/cpus/cpu@0 missing clock-frequency property
CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00
Setting up static identity map for 0x60100000 - 0x60100060
Hierarchical SRCU implementation.
smp: Bringing up secondary CPUs ...
smp: Brought up 1 node, 1 CPU
SMP: Total of 1 processors activated (6.00 BogoMIPS).
CPU: All CPU(s) started in SVC mode.
devtmpfs: initialized
random: get_random_u32 called from bucket_table_alloc+0x114/0x23c with crng_init=0
VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: 2, 16384 bytes)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
mxs_phy 40350000.usbphy: 40350000.usbphy supply phy-3p0 not found, using dummy regulator
hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
hw-breakpoint: maximum watchpoint size is 8 bytes.
imx7ulp-pinctrl 40ac0000.iomuxc1: initialized IMX pinctrl driver
MU is ready for cross core communication!
fsl-edma 40080000.dma-controller: fsl_edma2_irq_init Found 17 interrupts
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
i2c i2c-0: LPI2C adapter registered
i2c i2c-1: LPI2C adapter registered
Linux video capture interface: v2.00
pps_core: LinuxPPS API ver. 1 registered
pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
PTP clock support registered
MIPI CSI2 driver module loaded
MU is ready for cross core communication!
platform 40000000.ahb-bridge0: coherent DMA mask is unset
virtio_rpmsg_bus virtio0: rpmsg host is online
platform 40000000.ahb-bridge0: coherent DMA mask is unset
virtio_rpmsg_bus virtio1: rpmsg host is online
imx rpmsg driver is registered.
Advanced Linux Sound Architecture Driver Initialized.
Bluetooth: Core ver 2.22
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
clocksource: Switched to clocksource imx-tpm
VFS: Disk quotas dquot_6.6.0
VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
NET: Registered protocol family 2
TCP established hash table entries: 8192 (order: 3, 32768 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
UDP hash table entries: 512 (order: 2, 16384 bytes)
UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
hw perfevents: no irqs for PMU, sampling events not supported
hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
Bus freq driver module loaded
workingset: timestamp_bits=30 max_order=18 bucket_order=0
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
jffs2: version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
fuse init (API version 7.26)
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
io scheduler mq-deadline registered
io scheduler kyber registered
pwm-backlight backlight: backlight supply power not found, using dummy regulator
mipi_dsi_northwest 40a90000.mipi_dsi: i.MX MIPI DSI driver probed
adv7535 probing phase
adv7535 0-003d: main addr = 0x3d
i2c i2c-0: ADV7535 not found
mxsfb 40aa0000.lcdif: 40aa0000.lcdif supply lcd not found, using dummy regulator
mipi_dsi_northwest 40a90000.mipi_dsi: MIPI DSI dispdv inited
mxsfb 40aa0000.lcdif: registered mxc display driver mipi_dsi_northwest
Console: switching to colour frame buffer device 80x30
sii902x bound to mxs-lcdif from 40aa0000.lcdif
mxsfb 40aa0000.lcdif: initialized
SW1: failed to get the current voltage(-22)
pf1550-rpmsg pf1550-rpmsg: Failed to initialize regulator-0
pf1550-rpmsg: probe of pf1550-rpmsg failed with error -22
402d0000.serial: ttyLP0 at MMIO 0x402d0010 (irq = 40, base_baud = 1500000) is a FSL_LPUART
console [ttyLP0] enabled
fsl-lpuart 402d0000.serial: NO DMA tx channel, run at cpu mode
fsl-lpuart 402d0000.serial: NO DMA rx channel, run at cpu mode
imx sema4 driver is registered.
[drm] Initialized vivante 1.0.0 20120216 for platform:Vivante GCCore on minor 0
[drm] Initialized vivante 1.0.0 20120216 on minor 0
brd: module loaded
loop: module loaded
libphy: Fixed MDIO Bus: probed
CAN device driver interface
usbcore: registered new interface driver kaweth
pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
usbcore: registered new interface driver pegasus
usbcore: registered new interface driver rtl8150
usbcore: registered new interface driver r8152
usbcore: registered new interface driver asix
usbcore: registered new interface driver ax88179_178a
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver net1080
usbcore: registered new interface driver cdc_subset
usbcore: registered new interface driver zaurus
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-mxc: Freescale On-Chip EHCI Host driver
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usb_ehset_test
usbmisc_imx 40330200.usbmisc: 40330200.usbmisc supply vbus-wakeup not found, using dummy regulator
input: rpmsg-keys as /devices/platform/rpmsg-keys/input/input0
input: fts_ts as /devices/platform/40800000.ahb-bridge1/40a50000.lpi2c7/i2c-1/1-0038/input/input1
input: step_detector as /devices/platform/rpmsg-sensor/input/input2
input: step_counter as /devices/platform/rpmsg-sensor/input/input3
imx_rpmsg_rtc rtc-rpmsg: rtc core: registered rtc-rpmsg as rtc0
i2c /dev entries driver
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR Sharp protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR XMP protocol handler initialized
Bluetooth: HCI UART driver ver 2.3
Bluetooth: HCI UART protocol H4 registered
Bluetooth: HCI UART protocol BCSP registered
Bluetooth: HCI UART protocol ATH3K registered
usbcore: registered new interface driver bcm203x
usbcore: registered new interface driver btusb
usbcore: registered new interface driver ath3k
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
sdhci-esdhc-imx 40370000.usdhc: Got CD GPIO
sdhci-esdhc-imx 40380000.usdhc: Got CD GPIO
sdhci-esdhc-imx 40380000.usdhc: Got WP GPIO
caam 40240000.caam: ERA source: CCBVID.
caam 40240000.caam: device ID = 0x0a16030100000000 (Era 9)
caam 40240000.caam: job rings = 1, qi = 0, dpaa2 = no
caam_jr 40241000.jr0: Entropy delay = 3200
caam_jr 40241000.jr0: Instantiated RNG4 SH0.
caam_jr 40241000.jr0: Instantiated RNG4 SH1.
caam algorithms registered in /proc/crypto
caam_jr 40241000.jr0: registering rng-caam
platform caam_sm: blkkey_ex: 8 keystore units available
platform caam_sm: 64-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: 64-bit black key:
platform caam_sm: [0000] 91 f5 45 3e 28 88 47 06
platform caam_sm: [0008] 0f d7 0d fd 60 55 06 0a
platform caam_sm: 128-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
platform caam_sm: 128-bit black key:
platform caam_sm: [0000] ec a1 e2 31 dc dd 71 66
platform caam_sm: [0008] e4 0e d2 9e a3 df c1 f7
platform caam_sm: 192-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
platform caam_sm: [0016] 10 11 12 13 14 15 16 17
platform caam_sm: 192-bit black key:
platform caam_sm: [0000] 29 e4 44 70 07 b1 ea f5
platform caam_sm: [0008] 48 b1 ec 38 8c 61 e0 65
platform caam_sm: [0016] 5c 66 1a eb 0f a4 cc 70
platform caam_sm: [0024] 09 ef 1e 21 f8 34 44 d7
platform caam_sm: 256-bit clear key:
platform caam_sm: [0000] 00 01 02 03 04 0f 06 07
platform caam_sm: [0008] 08 09 0a 0b 0c 0d 0e 0f
platform caam_sm: [0016] 10 11 12 13 14 15 16 17
platform caam_sm: [0024] 18 19 1a 1b 1c 1d 1e 1f
platform caam_sm: 256-bit black key:
platform caam_sm: [0000] a1 d0 ee fc fe ff 6c 52
platform caam_sm: [0008] 24 c7 16 54 ae a3 fe b8
platform caam_sm: [0016] 73 2d be 5e 85 95 27 5c
platform caam_sm: [0024] d6 c1 60 64 2d 67 9e cf
platform caam_sm: 64-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 128-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 196-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 256-bit unwritten blob:
platform caam_sm: [0000] 00 00 00 00 00 00 00 00
platform caam_sm: [0008] 00 00 00 00 00 00 00 00
platform caam_sm: [0016] 00 00 00 00 00 00 00 00
platform caam_sm: [0024] 00 00 00 00 00 00 00 00
platform caam_sm: [0032] 00 00 00 00 00 00 00 00
platform caam_sm: [0040] 00 00 00 00 00 00 00 00
platform caam_sm: [0048] 00 00 00 00 00 00 00 00
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 64-bit black key in blob:
platform caam_sm: [0000] 2b bb 6f 78 4a 91 95 b3
platform caam_sm: [0008] 9d 8a 13 76 aa ed fd 41
platform caam_sm: [0016] 43 78 a9 4e 30 1e 2e ab
platform caam_sm: [0024] 82 eb 3b 43 2b 17 35 63
platform caam_sm: [0032] 41 ed 76 59 ff 7c ce cb
platform caam_sm: [0040] 74 9a cc 0a b9 39 09 7c
platform caam_sm: [0048] c6 7a 65 5c e9 55 11 84
platform caam_sm: [0056] 00 00 00 00 00 00 00 00
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 128-bit black key in blob:
platform caam_sm: [0000] 17 6c 69 d8 76 c2 9b 78
platform caam_sm: [0008] 88 0b a4 87 6b 92 e8 b4
platform caam_sm: [0016] 00 23 2f 3e 7a 8c e6 2c
platform caam_sm: [0024] 7c 09 50 4c 9f 26 57 17
platform caam_sm: [0032] da d3 cf ee 2e 7c 9c ef
platform caam_sm: [0040] cc 53 9b 7d f3 53 ee 3c
platform caam_sm: [0048] f1 86 d5 c4 93 65 9a b4
platform caam_sm: [0056] de cb 22 f1 c2 08 4b e2
platform caam_sm: [0064] 00 00 00 00 00 00 00 00
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 192-bit black key in blob:
platform caam_sm: [0000] 89 55 93 eb 44 af 3d 51
platform caam_sm: [0008] 88 f7 96 ce 2e b5 5a 44
platform caam_sm: [0016] ec 48 e7 c6 fb 45 6b 8f
platform caam_sm: [0024] 6b 1b 0c a5 35 2b bb 97
platform caam_sm: [0032] cf 40 3e af cc af 12 7f
platform caam_sm: [0040] 08 af 03 c6 18 d0 eb d9
platform caam_sm: [0048] 1f 06 58 0e 21 c7 e0 87
platform caam_sm: [0056] 69 7e e3 cc 72 91 bb c8
platform caam_sm: [0064] 90 c0 6f bf 62 63 bf 1f
platform caam_sm: [0072] 00 00 00 00 00 00 00 00
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: 256-bit black key in blob:
platform caam_sm: [0000] 97 12 b8 c6 ce 19 ac 6c
platform caam_sm: [0008] 2a 8b e5 62 fb 49 00 23
platform caam_sm: [0016] 7c c1 b8 39 0e 5a 7f 76
platform caam_sm: [0024] 22 e7 fb cb cd 04 81 73
platform caam_sm: [0032] c2 18 5f 36 eb d9 ca 82
platform caam_sm: [0040] 97 ab c9 95 93 9e e0 29
platform caam_sm: [0048] ea 46 7f 7f 84 bc 72 3a
platform caam_sm: [0056] f2 cd c8 80 7c 41 74 9b
platform caam_sm: [0064] fe a4 18 16 a8 8f eb 87
platform caam_sm: [0072] 1f fc 89 04 f8 d0 50 bc
platform caam_sm: [0080] 00 00 00 00 00 00 00 00
platform caam_sm: [0088] 00 00 00 00 00 00 00 00
platform caam_sm: restored 64-bit black key:
platform caam_sm: [0000] 6f 54 eb 9a b1 f1 44 66
platform caam_sm: [0008] 0f d9 2a 66 39 2e cb bb
platform caam_sm: restored 128-bit black key:
platform caam_sm: [0000] ec a1 e2 31 dc dd 71 66
random: fast init done
platform caam_sm: [0008] e4 0e d2 9e a3 df c1 f7
platform caam_sm: restored 192-bit black key:
platform caam_sm: [0000] 29 e4 44 70 07 b1 ea f5
platform caam_sm: [0008] 48 b1 ec 38 8c 61 e0 65
platform caam_sm: [0016] 5e 0f d8 10 a6 39 ba 70
platform caam_sm: [0024] 09 70 44 57 02 e7 c8 46
platform caam_sm: restored 256-bit black key:
platform caam_sm: [0000] a1 d0 ee fc fe ff 6c 52
platform caam_sm: [0008] 24 c7 16 54 ae a3 fe b8
platform caam_sm: [0016] 73 2d be 5e 85 95 27 5c
platform caam_sm: [0024] d6 c1 60 64 2d 67 9e cf
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
NET: Registered protocol family 26
NET: Registered protocol family 10
Segment Routing with IPv6
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20170425 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20170425)
can: broadcast manager protocol (rev 20170425 t)
can: netlink gateway (rev 20170425) max_hops=1
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: BNEP socket layer initialized
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
Bluetooth: HIDP socket layer initialized
8021q: 802.1Q VLAN Support v1.8
lib80211: common routines for IEEE802.11 drivers
Key type dns_resolver registered
cpu cpu0: failed to get regulator
imx7ulp-cpufreq: probe of imx7ulp-cpufreq failed with error -2
gpio-reset modem-reset: failed to request gpio 143: -22
gpio-reset: probe of modem-reset failed with error -22
WLAN_EN: Failed to request enable GPIO142: -22
reg-fixed-voltage regulators:sd1_regulator: Failed to register regulator: -22
reg-fixed-voltage: probe of regulators:sd1_regulator failed with error -22
sdhci-esdhc-imx 40370000.usdhc: Got CD GPIO
sdhci-esdhc-imx 40380000.usdhc: Got CD GPIO
sdhci-esdhc-imx 40380000.usdhc: Got WP GPIO
mmc1: SDHCI controller on 40380000.usdhc [40380000.usdhc] using ADMA
sdhci-esdhc-imx 40370000.usdhc: Got CD GPIO
imx_rpmsg_rtc rtc-rpmsg: hctosys: unable to read the hardware clock
usb_otg1_vbus: disabling
VSD_3V3: disabling
VSD_3V3B: disabling
ALSA device list:
No soundcards found.
Waiting for root device /dev/mmcblk0p2...

Did you figure out what was happening? In the tmp/deploy/images/<machine>/ folder, the shorted sdcard filename is just a link to the longer one.  when running the dd command I always just use the longer file name.

also, i see you have the bad CRC environment error in bootloader. for whatever reason, it is always required that the first time you boot from a newly imaged card, you interrupt boot, and type in "saveenv" (no quotes), then reset.  that may fix your problem. i have to do it every single time i write a new image to my sdcard.

Version history
Revision #:
1 of 1
Last update:
‎06-10-2015 02:07 PM
Updated by: