Jump to content

codiflow

Members
  • Posts

    3
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Pleinfeld, Germany
  • Interests
    IT, Tinkering

Contact Methods

  • Website URL
    https://sweetgood.de

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. codiflow

    codiflow

  2. I already got some "late night success" 🎉 Thanks to the work from @granitr in the following thread I could already successfully boot the stvm8b using the default meson8b-onecloud.dtb Currently it just seems that WIFI is not (yet) working – HDMI output worked directly from the beginning. I will keep everyone posted here on my progress 🙏
  3. Maybe we can bundle our effords regarding a working S805 image? I also have hundreds of new TV sticks (not boxes) with an Amlogic S805 (Meson 8B). The original Android ROM has the codename stvm8b. Currently I only have a working Android 4.2.2 image with a patched kernel for real 1080p output which can be flashed using TWRP onto the internal eMMC. I really would love to get some kind of more recent and non-Android image up and running. It's a real struggle to get any custom images as most links are dead already which makes it more complicated. Currently I have full UART access to the device and I'm able to interact with the uBoot shell. I also see the full kernel output of the working Android image and have a root shell there. But as others already pointed out kernel 3.10 is way to old to be used in production. So "porting" a more recent kernel would be great. My main goal is to get a Linux image up and running on the box which makes it still useful as device for digital signage or as a small webserver. Some more details on the hardware: ro.product.name=stvm8b ro.product.device=stvm8b ro.product.board=stvm8b ro.product.cpu.abi=armeabi-v7a ro.board.platform=meson8 uBoot output dropping to shell: QA5:A;SVN:B72;POC:1FF;STS:0;BOOT:0;INIT:0;READ:0;CHECK:0;PASS:0; no sdio debug board detected TE : 76654 BT : 15:34:06 May 13 2015 ##### VDDEE voltage = 0x044c CPU clock is 792MHz DDR mode: 32 bit mode DDR size: 1GB (auto) DDR check: Pass! DDR clock: 636MHz with 2T mode DDR pll bypass: Disabled DDR init use : 14831 us HHH Boot From SDIO C SD_boot_type: 00000002 card_type: 00000003 0x0000009f ucl decompress...pass 0x12345678 Boot from internal device 1st eMMC on SDIO C TE : 301370 System Started U-Boot Version: 2011.03-ad3b84b(20150513.153356) clr h-ram DRAM: 1 GiB relocation Offset is: 2feb4000 show partition table: part: 0, name : logo, size : 2000000 part: 1, name : recovery, size : 2000000 part: 2, name : misc, size : 2000000 part: 3, name : boot, size : 2000000 part: 4, name : system, size : 40000000 part: 5, name : cache, size : 20000000 part: 6, name : backup, size : 20000000 part: 7, name : data, size : end aml_card_type=0x0 MMC: [mmc_register] add mmc dev_num=0, port=1, if_type=6 [mmc_register] add mmc dev_num=1, port=2, if_type=6 SDIO Port B: 0, SDIO Port C: 1 power init out reg=c110804c,value=dfffffff IR init done! register usb cfg[0][1] = 3ff6c19c register usb cfg[0][2] = 3ff6c184 NAND: EMMC BOOT: not init nand do not init nand : cause boot_device_flag without nand get_boot_device_flag: init_ret -1 get_boot_device_flag EMMC BOOT: Emmckey: Access range is illegal! [mmc_init] SDIO Port C:1, if_type=7, initialized OK! [mmc_get_partition_table] skip cache partition. Partition table get from SPL is : name offset size flag =================================================================================== 0: bootloader 0 400000 0 1: reserved 2400000 4000000 0 2: cache 6c00000 20000000 2 3: env 27400000 800000 0 4: logo 28400000 2000000 1 5: recovery 2ac00000 2000000 1 6: misc 2d400000 2000000 1 7: boot 2fc00000 2000000 1 8: system 32400000 40000000 1 9: backup 72c00000 20000000 1 10: data 93400000 13ec00000 4 mmc read lba=0x12000, blocks=0x1 mmc read lba=0x12001, blocks=0x1 mmc_read_partition_tbl: mmc read partition OK! eMMC/TSD partition table have been checked OK! i=0,register --- emmc_key MMC BOOT, emmc_env_relocate_spec : env_relocate_spec 59 set_storage_device_flag: store 2 bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Multi dtb tool version: v2 . Multi dtb detected, support 5 dtbs. aml_dt soc: stvm8b platform: dongle variant: 1g dtb 0 soc: stvm8b plat: dongle vari: 1g dtb 1 soc: stvm8b plat: dongle vari: 512m dtb 2 soc: stvm8b plat: normal vari: 1g dtb 3 soc: stvm8b plat: normal vari: 1gcm dtb 4 soc: stvm8b plat: normal vari: 512mcm Find match dtb: 0 vpu clk_level in dts: 3 set vpu clk: 182150000Hz, readback: 182150000Hz(0x701) Net: Meson_Ethernet init suspend firmware done. (ret:0) cvbs trimming.1.v5: 0xa0, 0x0 preboot new... check board version... bad chip version!!! efuse mac is : ac:db:da:3d:c4:e5 set ethaddr is : ac:db:da:3d:c4:e5 usid is MH0507015420365 mmc flash is used high freq info->dtbversion = 1025 boardname=stvm8b boardtype=m8b_dongle wifi=rtl8189es dtbtype=stvm8b_dongle_1g Hardware version information has been written and the check is successful hdmi tx power init mode = 8 vic = 16 set HDMI vic: 16 mode is: 8 viu chan = 1 config HPLL config HPLL done reconfig packet setting done Hit Enter key to stop autoboot -- : 1 tstc enter exit abortboot: 1 The original name was "MyGica ATV185" and each device has a Quad-Core processor (Cortex A5, 1 GHz), 1 GB RAM, 8 GB internal eMMC storage, a WIFI module, 1x USB2.0, 1x microSD slot, 1x HDMI plug and 1x microUSB as power supply. The device should be the same like the ODroid C1 Would love to participate in the process of creating a useful image for the S805 platform and especially for this piece of hardware.
  4. I'm not sure if that helps but your log says "** Unable to read "dtb.img" from mmc 0:1 **" – so the dtb cannot be read from mmc and it is using the fdt instead: "Booting using the fdt blob at 0x11800000" So maybe the hardware cannot be initialized correctly because of a wrong / missing dtb?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines