Cannot flash iMX7D with uuu

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

Cannot flash iMX7D with uuu

723 Views
blz
Contributor I

I'm currently working on migrating an ucl2.xml file to program the board with uuu in linux. Right now I have the initial part working:

SPD: dcd -f u-boot.imx
SPD: write -f "u-boot.imx" -ivt 0
SPD: write -f "zImage" -addr 0x80800000
SPD: write -f "initramfs" -addr 0x83800000
SPD: write -f "device_tree_file" -addr 0x83000000
SPD: jump -f "u-boot.imx" -ivt 0

 

However, after jumping to the image, I cannot send commands over FBK. I noticed that the vid: 0x066F and pid: 0x37FF. The vid is listed in uuu -v but not the pid. 

I don't believe I'm allowed to modify the initramfs nor do I think that's the issue. I don't believe I can SSH to the device after the fact. Is this a dead end with uuu? Thanks for any help. 

Labels (1)
0 Kudos
Reply
3 Replies

700 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

Maybe it is not needed to fully translate your script, you may use the sample we have using kernel:
https://github.com/nxp-imx/mfgtools/wiki/Sample-scripts#burn-yocto-image-to-emmc-by-linux-kernel

Best regards/Saludos,
Aldo.

0 Kudos
Reply

678 Views
blz
Contributor I

Hi Aldo,

I don't think the script will work given what I have. I'd like to make a correction though earlier, I had suspected that the initramfs was irrelevant and I said I had to use the old one which isn't the case. 

I had actually opened a github issue to confirm the initramfs: https://github.com/nxp-imx/mfgtools/issues/471

That being said, I'm going through the documentation to flash the board with yocto. Here's what I've done:

I've setup the repo like so:

repo init -u https://github.com/nxp-imx/imx-manifest\n-
b imx-linux-styhead -m imx-6.12.3-1.0.0.xml

Previously, I had three files u-boot.imx, zImage, and fsl-image-mfgtool-initramfs.

I can make the initramfs with 

bitbake fsl-image-mfgtool-initramfs

but I'm not sure how to make the corresponding u-boot.imx and zImage. My understanding is that the u-boot.imx is dependent on the type of boot-media. For example if you were booting off of the emmc storage or an SD card. I think the board is booting off of emmc or QSPI flash. Is there a way for the u-boot.imx to be able to support both? 

I'm new to the Yocto project and working with embedded Linux on these boards so thank you for your patience!

Best,

Benjamin

0 Kudos
Reply

663 Views
AldoG
NXP TechSupport
NXP TechSupport

Hello,

It may not possible to have an all in one uboot image, you will need to have one for each target boot media, for eMMC/SD it is possible since both are almos the same.

For doing this using yocto you may use the following command:
$  echo "UBOOT_CONFIG = \"<boot_media>\"" >> conf/local.conf

where boot media can be any of the following (imx7D sabresd):
sd epdc qspi1 nand sd-optee

You may here build normally which should create all images needed, both uboot and kernel, in case you want to build them separetedly you may use the following commands:

For uboot:
$ MACHINE=imx7dsabresd bitbake u-boot-imx
For kernel image (zImage):
$ MACHINE=imx7dsabresd bitbake linux-imx

Best regards/Saludos,
Aldo.

0 Kudos
Reply