# Clearfog pro cn9130 bootloader

**URL:** <https://community.solid-run.com/t/clearfog-pro-cn9130-bootloader/591>\
**Category:** OCTEON CN9130\
**Created:** [March 11, 2023, 1:40pm UTC](https://community.solid-run.com/t/clearfog-pro-cn9130-bootloader/591 "2023-03-11T13:40:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![doudootiana](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@doudootiana](https://community.solid-run.com/u/doudootiana)\
**Post date:** [March 11, 2023, 1:40pm UTC](https://community.solid-run.com/t/clearfog-pro-cn9130-bootloader/591/1 "2023-03-11T13:40:06Z")

</div>

Hy 🙂

For my bootloader, i use uboot and the fit (kernel+fdt).

When it boots, it freeze after starting kernel…

```auto
  Press UP/DOWN to move, ENTER to select
***Carte : pro***
 **type de DiagBox**
 **=>Pro**
 ***Boot conf : conf-pro***
 ***Chargement Initrd : rootfs_alpha.cpio.gz***
90023840 bytes read in 7982 ms (10.8 MiB/s)
***Chargement Buildargs***
 ***Chargement fichier fit : diagbox.itb***
21945344 bytes read in 1973 ms (10.6 MiB/s)
***Boot M***
## Loading kernel from FIT Image at 05500000 ...
   Using 'conf-pro' configuration
   Trying 'kernel' kernel subimage
     Description: Kernel
     Created: 2023-03-11 13:34:02 UTC
     Type: Kernel Image
     Compression: uncompressed
     Data Start: 0x055000b4
     Data Size: 21893632 Bytes = 20.9 MiB
     Architecture: AArch64
     OS: Linux
     Load Address: 0x07000000
     Entry Point: 0x07000000
     Hash algo: sha1
     Hash value: e09d0e72910065ad6e51e87e4650ec8a33a38467
   Verifying Hash Integrity ... sha1+ OK
## Loading fdt from FIT Image at 05500000 ...
   Using 'conf-pro' configuration
   Trying 'fdt-pro' fdt subimage
     Description: dtb
     Created: 2023-03-11 13:34:02 UTC
     Type: Flat Device Tree
     Compression: uncompressed
     Data Start: 0x069e1394
     Data Size: 25157 Bytes = 24.6 KiB
     Architecture: AArch64
     Load Address: 0x05400003
     Hash algo: sha1
     Hash value: 7241b8c020648d25d9863785409cfd5ef1b16681
   Verifying Hash Integrity ... sha1+ OK
   Loading fdt from 0x069e1394 to 0x05400003
   Booting using the fdt blob at 0x5400003
   Loading Kernel Image
   Loading Device Tree to 000000007f5d5000, end 000000007f5de244 ... OK

Starting kernel ...

```

But if i disconenct the pwoer supply and reconnect, it boots normally.

Has someone an idea please?

Thank you by advance

---

<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:** [March 12, 2023, 9:07am UTC](https://community.solid-run.com/t/clearfog-pro-cn9130-bootloader/591/2 "2023-03-12T09:07:20Z")

</div>

What version of u-boot and kernel are you running?

---

<div class="post-metadata">

**Author:** ![doudootiana](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@doudootiana](https://community.solid-run.com/u/doudootiana)\
**Post date:** [March 12, 2023, 11:16am UTC](https://community.solid-run.com/t/clearfog-pro-cn9130-bootloader/591/3 "2023-03-12T11:16:00Z")

</div>

Hy 🙂

For the kernel, i use the 6.1.

About U-boot, i work with the 209-10, with all patch like here : [https://github.com/SolidRun/cn913x\_build](https://github.com/SolidRun/cn913x_build)

I post the conf of u-boot here : [http://pastebin.fr/120676](http://pastebin.fr/120676)

My kernel image and fdt is in a fit image.

the config of fit image :

```auto
/dts-v1/;
/ {
	description = "Kernel et dtb";

	#address-cells = <1>;
	images {
		kernel {
			description = "Kernel";
			data = /incbin/("/etc/diagbox/binaries/Image");
			type = "kernel";
			arch = "arm64";
			os = "linux";
			compression = "none";
			load = <0x7000000>;
			entry = <0x7000000>;
			hash-1 {
				algo = "sha1";
			};
		};
		fdt-pro {
			description = "dtb";
			data = /incbin/("/etc/diagbox/binaries/diagbox_pro.dtb");
			type = "flat_dt";
			arch = "arm64";
			load = <0x6f00000>;
			entry = <0x6f00000>;
			compression = "none";
			hash-1 {
				algo = "sha1";
			};
		};
		fdt-base {
			description = "dtb";
			data = /incbin/("/etc/diagbox/binaries/diagbox_base.dtb");
			type = "flat_dt";
			arch = "arm64";
			load = <0x6f00000>;
			entry = <0x6f00000>;
			compression = "none";
			hash-1 {
				algo = "sha1";
			};
		};
	};
 
	configurations {
		default = "conf-pro";
		conf-pro {
			description = "Configuration";
			kernel = "kernel";
			fdt = "fdt-pro";
			hash-1 {
				algo = "sha1";
			};
		};
		conf-base {
			description = "Configuration";
			kernel = "kernel";
			fdt = "fdt-base";
			hash-1 {
				algo = "sha1";
			};
		};
	};
};

```

I think the problem come from uboot, deduction made by research on internet.

But i don’t know why it works when a i do an electric reboot

---

<div class="post-metadata">

**Author:** ![doudootiana](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@doudootiana](https://community.solid-run.com/u/doudootiana)\
**Post date:** [March 21, 2023, 9:54pm UTC](https://community.solid-run.com/t/clearfog-pro-cn9130-bootloader/591/4 "2023-03-21T21:54:04Z")

</div>

Hy.  
One question : Is clearfog pro cn9130 compatible with uboot 2022-10?