ODROID C1/C1+ PROJECT ----- Turn MXQ S805 based into Odroid C1/C1+ Board

[germinbmxer]

Sorry for my english... I'm brazilian.
Hello to all members.
I'm interesting to convert my TV box MXQ S805 based into an ODROID C1/C1+ board (like Raspberry Pi) to run Arcade system and test others plataforms.

I saw Odroid hardware and it is identical to TV box, use same processor, IR sensor, HDMI, USB, and same 1gb RAM memory.

Odroid C1/C1+ home page: http://www.hardkernel.com/main/produ...=G143703355573
Odroid C1/C1+ Technical detail: http://www.hardkernel.com/main/produ...5573&tab_idx=2
Odroid Full Eschematics: http://dn.odroid.com/homebackup/odro..._201401107.pdf (temporary off-line)

The difference is TV box has a NAND chip to store Android and Odroid have nothing(it boots directly from eMMC or SD card).
I removed that NAND from TVbox (to boot directly from SD card).
Next, i used "win32 Disk Imager" to create SD card but when i saw it on Gparted, only 2 partitions are present on SD, one FAT and other EXT4 (i think that need another partition with boot sector, but i don't know how create it. ).
I tryed to boot with SD card with system for Odroid C1 but appear this message:

-----------------------------------------------------------------------------------------------
* Welcome to Hardkernel's ODROID-C... (built at 19:33:00 Dec 8 2014*
-----------------------------------------------------------------------------------------------
CPU : AMLogic S805
MEM : 1024MB (DDR3@792MHz)
BID : <unknown>
S/N :
***** Warning!! ************************************************** ***
* This board have not been autorized or product keys are not valid. *
* Please contact with Hardkernel or your distributor *
************************************************** *******************

Anyone help-me?
Thank's for all.

[germinbmxer]

Board detail:

[balbes150]

Loader Odroid is not suitable for TV consoles. As an option, you can view useful info here.

http://forum.armbian.com/index.php/forum/16-amlogic/

[germinbmxer]

Loader Odroid is not suitable for TV consoles. As an option, you can view useful info here.

http://forum.armbian.com/index.php/forum/16-amlogic/

balbes150, if the hardware is the same, why not suitable? because if i remove the NAND from the board of TV, the access is directly to the SDcard. Or have configuration internal of S805 to accept especific FW, not depending only hardware? For example, BID showing <unknown> and S/N ( in blank) is archived internal in S085 chip?

[balbes150]

Is not suitable because the primary binary u-boot Odroid prescribed rigid adherence to their hardware. Collect your own version of u-boot. Or use a modified version of the standard (multi-boot)

[germinbmxer]

Is not suitable because the primary binary u-boot Odroid prescribed rigid adherence to their hardware. Collect your own version of u-boot. Or use a modified version of the standard (multi-boot)

Ok, i understand.
have you an u-boot.bin for i use with lakka arcade?


ex:
i'm using a S805 tv box without NAND:
i prepair sdcard with an u-boot.bin to boot this: http://mirror.lakka.tv/nightly/Odroi...1ab3658.img.gz
when i flash this image to sdcard, it creates three files: boot.ini, SYSTEM and KERNEL
but it dont boot because i dont have correct u-boot.bin.

i use an u-boot.bin and use PUTTY to do commands:

m8b_m201_1G#fatload mmc 0:1 0x00000000 KERNEL
reading KERNEL

6504942 bytes read
m8b_m201_1G#fatload mmc 0:1 0x00800000 meson8b_odroidc.dtb
reading meson8b_odroidc.dtb

18358 bytes read
m8b_m201_1G#fdt addr 00800000
m8b_m201_1G#bootm 0x00000000 - 0x00800000
Wrong Image Format for bootm command
ERROR: can't get kernel image!
m8b_m201_1G#

i coppy address from this image

[balbes150]

fatload mmc 0 0x11000000 KERNEL

fatload mmc 0 0x1000000 dtb.img

bootm 0x11000000


I recommend to read this information. There are many examples of working scripts from which you can obtain a lot of useful information about the logic and commands.

https://github.com/150balbes/Amlogic_s905

Note the correct file "dtb.img" . It must be the file from YOUR TV box. From Odroid will not work. Without a valid dtb file will not work. Can try different options one by one from here.

https://yadi.sk/d/nBL7MchXvAFGL

After the recording of any image in the FAT partition will be able to find several options for the dtb.


Still recommend to read this topic.

http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s805/others-ab/596804-linux-for-amlogic-s805

http://forum.armbian.com/index.php/topic/1919-armbian-for-amlogic-s805/

[germinbmxer]

fatload mmc 0 0x11000000 KERNEL

fatload mmc 0 0x1000000 dtb.img

bootm 0x11000000

m8b_m201_1G#fatload mmc 0:1 0x11000000 kernel
reading kernel

6504942 bytes read
m8b_m201_1G#fatload mmc 0:1 0x10000000 img.dtb
reading img.dtb

20450 bytes read
m8b_m201_1G#bootm 0x11000000
## Booting kernel from Legacy Image at 11000000 ...
Image Name: Linux-3.10.75
Image Type: ARM Linux Kernel Image (gzip compressed)
Data Size: 6504878 Bytes = 6.2 MiB
Load Address: 00208000
Entry Point: 00208000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
uboot time: 1360693781 us.
EFUSE machid is not set.
Using machid 0xf81 from environment
Enter Exception:0x00000004
link addr:0x1febdabc



after, board restart automaticaly

[germinbmxer]

what is ramdisk address?

[balbes150]

1. Show the contents of the file "boot.ini". We need to see what there is indicates the address and the command to run the system.
2. Try to run it without a command download "dtb.img". But most likely the dtb data is already integrated in the KERNEL and are not suitable for Your TV box. You can try to unpack the KERNEL and try to use the separate download of the kernel, dtb and initramfs (which is now probably Packed all together in one file).

[germinbmxer]

I put this commands on "debian_mate_s805_20160919.img" after change dtb.img

m8b_m201_1G#setenv bootargs "root=LABEL=ROOTFS rootwait rw console=ttyS0,115200n8 console=tty0 consoleblank=0 no_console_suspend logo=osd1,loaded,0x7900000,720p,full hdmimode=720p m_bpp=32 vout=hdmi"
m8b_m201_1G#fatload mmc 0:1 0x11800000 dtb.img
reading dtb.img

22880 bytes read
m8b_m201_1G#fatload mmc 0:1 0x11000000 uInitrd
reading uInitrd

3923795 bytes read
m8b_m201_1G#fatload mmc 0:1 0x12000000 uImage
reading uImage

5574439 bytes read
m8b_m201_1G#bootm 0x12000000 0x11000000 0x11800000
## Booting kernel from Legacy Image at 12000000 ...
Image Name: Linux-3.10.80-20-odrobian
Image Type: ARM Linux Kernel Image (lzo compressed)
Data Size: 5574375 Bytes = 5.3 MiB
Load Address: 00208000
Entry Point: 00208000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 11000000 ...
Image Name: uInitrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3923731 Bytes = 3.7 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 11800000
Booting using the fdt blob at 0x11800000
Uncompressing Kernel Image ... OK
uboot time: 75801475 us.
EFUSE machid is not set.
Using machid 0xf81 from environment
From device tree /memory/ node aml_reserved_end property, for relocate ramdisk and fdt, relocate_addr: 0x53c7001
Loading Ramdisk to 05009000, end 053c6f13 ... OK
Loading Device Tree to 05000000, end 0500895f ... OK

Starting kernel ...

BUT nothing after "Starting kernel ..."

1. Show the contents of the file "boot.ini". We need to see what there is indicates the address and the command to run the system.

I dont have boot.ini file

[balbes150]

Probably not correct dtb file. You need to find such that the system will fail to start.