# eMMC error on custom carrier board

**URL:** <https://community.solid-run.com/t/emmc-error-on-custom-carrier-board/915>\
**Category:** OCTEON CN9130\
**Created:** [October 22, 2024, 5:31pm UTC](https://community.solid-run.com/t/emmc-error-on-custom-carrier-board/915 "2024-10-22T17:31:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lolo\_Bee](https://avatars.discourse-cdn.com/v4/letter/l/e8c25b/32.png) [@Lolo\_Bee](https://community.solid-run.com/u/Lolo_Bee)\
**Post date:** [October 22, 2024, 5:31pm UTC](https://community.solid-run.com/t/emmc-error-on-custom-carrier-board/915/1 "2024-10-22T17:31:15Z")

</div>

We’ve create a custom carrier board for CN9130 based on ClearFog Pro board’s schematics.  
The SOM boots perfectly in base (which is the model we have for testing) and boots ubuntu with no error, but when pluggin the SOM into our carrier board, we’re getting this error related to eMMC

```auto
BootROM - 2.03
Starting AP IOROM 1.02
Booting from eMMC 0
Found valid image at boot postion 0x004
lNOTICE: Starting binary extension
NOTICE: SVC: DEV ID: CN913x, FREQ Mode: 0x1
ERROR: SVC: Unsupported Frequency 0x1
w/o ecc; strap value=0
4GB capacity; strap value=0
mv_ddr: 14.0.0-gef2995c (May 30 2024 - 09:15:22)
SSCG_EN
mv_ddr: ddr freq 1 unsupported
error: mv_ddr_tdllk_get: unsupported data rate found
Synopsys DDR43 PHY Firmware version: A-2017.11
error: init_phy_pllctrl2_get: unsupported frequency found
error: init_phy_ardptrinitval_get: unsupported frequency found
error: init_phy_procodttimectl_get: unsupported frequency found
error: init_phy_caluclkinfo_get: unsupported frequency found
error: dmem_1d_2d_dram_freq_get: unsupported frequency found
error: mv_ddr_mr0_wr_get: unsupported t_wr value found
Training step/s sequence 31e failed
SNPS DDR: 1D training failed
SNPS DDR: training failed
error: mv_ddr_init failed

```

From a regular boot, the only parameter which changes is the FREQ Mode. In base board it’s 0x0 and in our board it is 0x1

Where does this value comes from? as SW1 and SW2 are for different purposes.

Thank you.

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [November 3, 2024, 6:05am UTC](https://community.solid-run.com/t/emmc-error-on-custom-carrier-board/915/2 "2024-11-03T06:05:25Z")

</div>

Sorry for the delays. The Freq mode is a dual purpose pin that is tied the SPI MOSI signal. I will check if it can be overridden by software if your board design conflicts with it.

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/solid_run/original/1X/a819312997b7375119e5e766b4d92c8f07c8d8dd.png)

---

<div class="post-metadata">

**Author:** ![Lolo\_Bee](https://avatars.discourse-cdn.com/v4/letter/l/e8c25b/32.png) [@Lolo\_Bee](https://community.solid-run.com/u/Lolo_Bee)\
**Post date:** [November 3, 2024, 12:01pm UTC](https://community.solid-run.com/t/emmc-error-on-custom-carrier-board/915/3 "2024-11-03T12:01:26Z")

</div>

Thank you!  
We will try to patch the board and will update you.

Cheers

---

<div class="post-metadata">

**Author:** ![Lolo\_Bee](https://avatars.discourse-cdn.com/v4/letter/l/e8c25b/32.png) [@Lolo\_Bee](https://community.solid-run.com/u/Lolo_Bee)\
**Post date:** [November 14, 2024, 9:54am UTC](https://community.solid-run.com/t/emmc-error-on-custom-carrier-board/915/4 "2024-11-14T09:54:12Z")

</div>

Hello!  
We’ve patched the board according to your tips but it did not work, and after double checking everything, we’ve found some missmatch in pin assignment:

- From SOM schematics, page 2, connector J1:

- From Pro Board Schematics, Page 2:

Also from your directions, there’s no CP1\_MPP15 pin in SOM, there’s CP0\_MPP15 tied to SPI\_MOSI, which is supposed to be the pin we’re talking about right?

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/solid_run/original/1X/409d6a9323de54fb98ccdc822b2bef51055471a8.png)

Is there’s a mistake in schematics?

Also, what kind of patches should be done from u-boot in order to force the eMMC mode? Which branch from u-boot source [from your repo](https://github.com/SolidRun/u-boot) should be used, as no one is named CN913x.

Thank you