Migration from rocko to scarthgap

Technical Support
, ,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello! Thank you for providing the details of your issues during the migration from Rocko to Scarthgap. Let’s address your U-Boot and kernel problems step by step.

1. U-Boot: “MMC Device 0 not found” & “MISSING TORADEX CONFIG BLOCK”

Root Cause:
These messages mean that U-Boot is unable to detect the eMMC storage, so it cannot read the environment or the Toradex config block (which holds crucial information like MAC address).

Recommended Checks:

  • eMMC Hardware Boot Area Configuration:
    Since BSP V2.5b2, U-Boot and the configuration block are stored in the primary eMMC hardware boot area partition (/dev/mmcblk0boot0).
    You should ensure the boot partitions are enabled and configured correctly. From the U-Boot prompt, try:

    mmc list
mmc dev 0
mmc part

    If nothing appears or errors persist, U-Boot may not be recognizing the eMMC.

  • Verify eMMC Boot Partition Settings:
    Check boot partition configurations:

    mmc bootbus 0
mmc partconf 0

    More details here:
    Booting from eMMC Hardware Boot Area Partitions

  • Config Block Migration:
    If you migrated a module with the old layout, make sure the config block was properly carried over to the correct location.

    Details about config block and its migration

  • Power Failures or Corruption:
    Sudden power-offs during migration might have left the eMMC in a corrupted state, leading to detection failures.
    Related Community Discussion

2. Kernel: “Failed to start Ethtool configuration for eth0”

This error likely results from a missing MAC address or interface configuration. Since the MAC is normally loaded from the config block on eMMC, your U-Boot issue is the root cause. Once U-Boot can see the config block, the MAC address will be correct, and this kernel error should disappear.

Summary of Steps to Resolve:

  1. From U-Boot, verify and list the MMC devices. Test access to boot partitions as above.
  2. If eMMC is not visible, review your migration steps for moving the config block and ensure correct U-Boot environment settings.
  3. Check power and eMMC connections if the issue persists after the above.
  4. Once U-Boot detects eMMC and the config block, the Ethtool startup issue in Linux should be resolved automatically.

Extra Links for Reference:

Please try the above and let me know what further details you find after running the suggested U-Boot commands. If you have relevant boot logs or screenshots, sharing those can help narrow down the root cause.

Best regards,
Toradex AI Assistant.