Cc-wmx93-kit getting started not loading

I just today received my anticipated cc-imx93-kit and started to go through the step by step to get started.
When I boot the board and stop u-boot to load the fw image, I get the message that install_linux_fw_sd does not exist.
Looking at the u-boot information I find the u-boot is version 2022.04 which is not what the guide states.
I also see the device is an A0 device.

I already used diskpart to get the sd formatted as FAT, but still no luck. I also tried to use my linux VM where minicom connect fine and lets me run ‘fastboot 1’. I am assuming that it should stay in that position but the sh script just waits for a USB device to appear.

Is there an alternative way to get fw loaded?

EDIT:
I just saw that the fastboot 1 command creates the USB OTG and can be connected to my VM. So far so good.
Now the VM creates this message when starting to load using fastboot: 1:1 1/ 1 [Bulk(W):LIBUSB_ERROR_TIMEOUT ] fb: ucmd setenv stdout serial,fastboot

EDIT2:
I ran the following UBOOT command and think I need to figure how to run from mmc 1.

=> ls mmc 1
            System Volume Information/
 13785600   dey-image-qt-xwayland-ccimx93-dvk.boot.vfat
 595591168   dey-image-qt-xwayland-ccimx93-dvk.ext4
 20188160   dey-image-qt-xwayland-ccimx93-dvk.recovery.vfat
  1738752   imx-boot-ccimx93-dvk.bin
  1722368   imx-boot-ccimx93-dvk-A0.bin
     7794   install_linux_fw_sd.scr
     7802   install_linux_fw_usb.scr
     9726   install_linux_fw_uuu.sh
     2432   install_usb_driver.sh
      668   README.txt

10 file(s), 1 dir(s)

=> run install_linux_fw_sd
## Error: "install_linux_fw_sd" not defined

How do I get it to run when it does not behave as the guide expects?

I also tried to use my linux VM where minicom connect fine and lets me run ‘fastboot 1’. I am assuming that it should stay in that position but the sh script just waits for a USB device to appear.

You would need to transfer a fastboot USB device from host to the VM. it can be tricky.

if your board is still booting use the second half of the getting started guide:
https://www.digi.com/resources/documentation/digidocs/embedded/dey/4.0/cc93/yocto-gs-program-fw_t.html#download-the-firmware
Scroll down to the section:

Program the firmware using uSD card

If this doesn’t work, please provide logs. For faster response please open a support case by sending an email to tech.support@digi.com

Hi LeonidM

Reading my edits will show that I have tried that already, and that run install_linux_fw_sd fails

I am thinking maybe running mmc dev 1; update uboot imx-boot-ccimx93-dvk-A0.bin will make the update so that the install will work?

This is my boot output

SOC: 0xa0009300
LC: 0x40010
M33 prepare ok
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x0, pagesize 0x200, ivt offset 0x0
Load image from 0x3fc00 by ROM_API
NOTICE:  BL31: v2.6(release):lf-5.15.71-2.2.0-0-g3c1583ba0-dirty
NOTICE:  BL31: Built : 11:27:52, May  3 2023


U-Boot dub-2022.04-r1.2 (May 03 2023 - 11:27:37 +0000)

CPU:   i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz)
CPU:   Consumer temperature grade (0C to 95C) at 31C
Reset cause: POR (0x1)
DRAM:  992 MiB
Core:  189 devices, 22 uclasses, devicetree: separate
MMC:   FSL_SDHC: 0, FSL_SDHC: 1
In:    serial
Out:   serial
Err:   serial
Model: Digi ConnectCore 93 Development Kit
ConnectCore 93 SOM variant 0x01: 992 MiB LPDDR4, Wi-Fi, Bluetooth
  Board version 1
Boot:  MMC0

BuildInfo:
  - ELE firmware version 0.0.8-80d3db4b

flash target is MMC:0
Net:   eth0: ethernet@428a0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot:  0
=>

yes, please take a look at Recover your device | ConnectCore 93
scroll all the way down to Re-program the bootloader from the microSD card

Re-program bootloader from microSD card
Place the U-Boot binary inside a FAT-formatted microSD card.

Insert the microSD card in the board.

Run the following command to update U-Boot into the eMMC:

update uboot mmc 1 fat <u-boot-filename>.bin

If looking at my boot log, do you agree that my device is an A0 revision please?

yes it is A0

=> run install_linux_fw_sd

Error: “install_linux_fw_sd” not defined

Try those commands instead:

=> fatload mmc 1 $loadaddr install_linux_fw_sd.scr
=> source $loadaddr

I now tried your command suggestion and it updated u-boot but failed at a bootcount command and seem to have left out the linux install.

=> fatload mmc 1 $loadaddr install_linux_fw_sd.scr
7794 bytes read in 5 ms (1.5 MiB/s)
=> source $loadaddr

Executing script at 80400000

############################################################

Linux firmware install from micro SD

############################################################

This process will erase your eMMC and will install the following files
on the partitions of the eMMC.

PARTITION FILENAME


bootloader imx-boot-ccimx93-dvk-A0.bin
linux_a dey-image-qt-xwayland-ccimx93-dvk.boot.vfat
rootfs_a dey-image-qt-xwayland-ccimx93-dvk.ext4

Press CTRL+C now if you wish to abort or wait 10 seconds
to continue.

Installing U-Boot boot loader image imx-boot-ccimx93-dvk-A0.bin (target will reset)

1722368 bytes read in 76 ms (21.6 MiB/s)
switch to partitions 1, OK
mmc0(part 1) is current device

MMC write: dev # 0, block # 0, count 3364 … 3364 blocks written: OK
Reading back firmware…

MMC read: dev # 0, block # 0, count 3364 … 3364 blocks read: OK
Verifying firmware…
Total of 430592 word(s) were the same
Update was successful
Unknown command ‘bootcount’ - try ‘help’
Saving Environment to MMC… Writing to redundant MMC(0)… OK
resetting …

U-Boot SPL dub-2023.04-r3.2+gd27aefc1691+p0 (Feb 06 2024 - 22:15:48 +0000)
SOC: 0xa0009300
LC: 0x40010
PMIC: Over Drive Voltage Mode
M33 prepare ok
Normal Boot
Trying to boot from BOOTROM
Boot Stage: Primary boot
image offset 0x0, pagesize 0x200, ivt offset 0x0
Load image from 0x4b400 by ROM_API
NOTICE: BL31: v2.8(release):lf-6.1.55-2.2.0-0-g08e9d4eef-dirty
NOTICE: BL31: Built : 22:15:48, Feb 6 2024

U-Boot dub-2023.04-r3.2+gd27aefc1691+p0 (Feb 06 2024 - 22:15:48 +0000)

CPU: i.MX93(52) rev1.0 1700 MHz (running at 1692 MHz)
CPU: Consumer temperature grade (0C to 95C) at 37C
Reset cause: WDOG3 (0x20)
DRAM: 992 MiB
Core: 202 devices, 29 uclasses, devicetree: separate
MMC: FSL_SDHC: 0, FSL_SDHC: 1
*** Warning - bad CRC, using default environment

WARNING: Dummy default MAC in ‘ethaddr’
WARNING: Dummy default MAC in ‘eth1addr’
WARNING: Dummy default MAC in ‘wlanaddr’
WARNING: Dummy default MAC in ‘btaddr’

Error: Can’t overwrite “ethaddr”

himport_r: can’t insert “ethaddr=00:04:f3:ff:ff:fa” into hash table

Error: Can’t overwrite “wlanaddr”

himport_r: can’t insert “wlanaddr=00:04:f3:ff:ff:fb” into hash table

Error: Can’t overwrite “btaddr”

himport_r: can’t insert “btaddr=00:04:f3:ff:ff:fc” into hash table

Error: Can’t overwrite “eth1addr”

himport_r: can’t insert “eth1addr=00:04:f3:ff:ff:fd” into hash table
In: serial
Out: serial
Err: serial
Model: Digi ConnectCore 93 Development Kit
ConnectCore 93 SOM variant 0x01: 992 MiB LPDDR4, Wi-Fi, Bluetooth
Board version undefined, ID undefined
Boot: MMC0

BuildInfo:

  • ELE firmware version 0.0.10-af252062

flash target is MMC:0
Net: eth0: ethernet@428a0000 [PRIME]
Fastboot: Normal
Normal Boot
Hit any key to stop autoboot: 0
Running BSP bootcmd …
switch to partitions 0, OK
mmc0(part 0) is current device
** No partition table - mmc 0 **
Couldn’t find partition mmc 0:1
Can’t set block device
** No partition table - mmc 0 **
Couldn’t find partition mmc 0:1
Can’t set block device
Booting from net …
ethernet@428a0000 Waiting for PHY auto negotiation to complete… done
BOOTP broadcast 1
DHCP client bound to address 192.168.68.79 (152 ms)
Using ethernet@428a0000 device
TFTP from server 192.168.42.1; our IP address is 192.168.68.79; sending through gateway 192.168.68.1
Filename ‘os_cntr_signed.bin’.
Load address: 0x98000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Authenticate OS container at 0x98000000
Error: Wrong container header
ERR: failed to authenticate
=>

I now did, however, do the run install_linux_fw_sd command and it installed Yocto this time round :slight_smile: