As near as I know, I have followed these steps
RIoTboard: Linux on the RIoTBoard Part 2: Kernel | element14
The first time on a digital ocean server everything worked as expected. I have zipped the linux build and transferred it to a local machine, and now the device won't boot anyway I can figure out.
After putting the new zImage in /boot/ I get this
Hit any key to stop autoboot: 0
MMC: no card present
MMC: no card present
switch to partitions #0, OK
mmc2(part 0) is current device
Scanning mmc 2:1...
Found U-Boot script /boot.scr
293 bytes read in 137 ms (2 KiB/s)
## Executing script at 13100000
switch to partitions #0, OK
mmc2(part 0) is current device
5690392 bytes read in 370 ms (14.7 MiB/s)
31992 bytes read in 61 ms (511.7 KiB/s)
Kernel image @ 0x10800000 [ 0x000000 - 0x56d418 ]
## Flattened Device Tree blob at 16800000
Booting using the fdt blob at 0x16800000
Loading Device Tree to 1fff5000, end 1ffffcf7 ... OK
Starting kernel ...
Changing the boot.scr to boot a uImage, I get this
U-Boot 2015.10-rc3-00214-g8a5f612 (Sep 23 2015 - 07:16:49 -0400)
CPU: Freescale i.MX6SOLO rev1.1 996 MHz (running at 792 MHz)
CPU: Commercial temperature grade (0C to 95C) at 40C
Reset cause: WDOG
Board: RIoTboard
I2C: ready
DRAM: 1 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
*** Warning - bad CRC, using default environment
No panel detected: default to HDMI
Display: HDMI (1024x768)
In: serial
Out: serial
Err: serial
Net: FEC [PRIME]
Error: FEC address not set.
Hit any key to stop autoboot: 0
MMC: no card present
MMC: no card present
switch to partitions #0, OK
mmc2(part 0) is current device
Scanning mmc 2:1...
Found U-Boot script /boot.scr
313 bytes read in 138 ms (2 KiB/s)
## Executing script at 13100000
Unknown command 'bootscript' - try 'help'
switch to partitions #0, OK
mmc2(part 0) is current device
5690456 bytes read in 356 ms (15.2 MiB/s)
31992 bytes read in 61 ms (511.7 KiB/s)
## Booting kernel from Legacy Image at 10800000 ...
Image Name:
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5690392 Bytes = 5.4 MiB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 16800000
Booting using the fdt blob at 0x16800000
Loading Kernel Image ... OK
Loading Device Tree to 1fff5000, end 1ffffcf7 ... OK
Starting kernel ...
So is there some factor I am missing here?
If its is a factor, emdebian doesn't host the toolchain anymore, could the gcc be a factor here? I did an apt-get install gcc-arm-linux-gnueabihf
