# How to boot pre-built debian images on cf-base. Missing cn9130-cf-base.dtb in boot/marvell

**URL:** <https://community.solid-run.com/t/how-to-boot-pre-built-debian-images-on-cf-base-missing-cn9130-cf-base-dtb-in-boot-marvell/969>\
**Category:** OCTEON CN9130\
**Created:** [January 21, 2025, 1:50pm UTC](https://community.solid-run.com/t/how-to-boot-pre-built-debian-images-on-cf-base-missing-cn9130-cf-base-dtb-in-boot-marvell/969 "2025-01-21T13:50:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\
**Post date:** [January 21, 2025, 1:50pm UTC](https://community.solid-run.com/t/how-to-boot-pre-built-debian-images-on-cf-base-missing-cn9130-cf-base-dtb-in-boot-marvell/969/1 "2025-01-21T13:50:38Z")

</div>

Hi i’ve decided to try out a pre-built image from images.solidrun. as i’ve been having a nightmare compiling a working ubuntu image.

anyway i’ve downloaded from cn913x\_build/sdk12/2025-01-19\_3bceda1  
cn9130-cf-base-debian-bookworm-microsd.img.xz

On burning the img to sdcard. it drops to u-boot. previously my u-boot environment pointed to cn9130-cf-base.dtb in boot/marvell/. However that dtb doesn’t exist in the img file. only dtb’s which seem unrelated to the build.

```auto
virtual@virtual-VirtualBox:/mnt/md126/boot/marvell$ ls
armada-8040-clearfog-gt-8k.dtb armada-8040-mcbin-singleshot.dtb cn9130-crb-B.dtb cn9130-db.dtb cn9131-db.dtb cn9132-db.dtb
armada-8040-mcbin.dtb cn9130-crb-A.dtb cn9130-db-B.dtb cn9131-db-B.dtb cn9132-db-B.dtb

```

typically i’d set environment from uboot prompt. e.g from documentation

```auto
setenv get_images "load mmc 1:1 $kernel_addr_r boot/Image /
load mmc 1:1 $fdt_addr_r boot/marvell/cn9130-cf-base.dtb /
setenv root 'root=/dev/mmcblk1p1 rootwait rw' /
setenv ramdisk_addr_r -"
saveenv
boot

```

i didn’t think it’d work but i did try some of the dtb’s but obvioulsy didn’t work. Am i missing something stupid?

---

<div class="post-metadata">

**Author:** ![RoutingLoop](https://avatars.discourse-cdn.com/v4/letter/r/ac8455/32.png) [@RoutingLoop](https://community.solid-run.com/u/RoutingLoop)\
**Post date:** [January 21, 2025, 11:29pm UTC](https://community.solid-run.com/t/how-to-boot-pre-built-debian-images-on-cf-base-missing-cn9130-cf-base-dtb-in-boot-marvell/969/2 "2025-01-21T23:29:09Z")

</div>

I’ve may have realised something. My device is a very early model, i had it on pre-order. December 2021, original build felt simple compared to this.

looks like devices pre April 2022, didn’t have uboot shipped on SPI. Does anyone know if I need to install u-boot on SPI to get it working with the pre-compiled images. I’m reluctant to go through the pain and risk of flashing SPI and alerting my jumper settings if it’s not that.

---

<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:** [January 22, 2025, 5:40am UTC](https://community.solid-run.com/t/how-to-boot-pre-built-debian-images-on-cf-base-missing-cn9130-cf-base-dtb-in-boot-marvell/969/3 "2025-01-22T05:40:19Z")

</div>

it shouldn’t be a problem to flash spi-nor. It should be accessible in u-boot for you to test.