Announcement

Collapse
No announcement yet.

Does anyone understand AML-AUTOSCRIPT?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

    #61
    Stane I always wondered what the SPI thing was about. What is a SPI chip?

    When I unzip a SPI update it has uboot and recovery but this file env_MX.img.

    Looking at that with a hex editor it has this inside. Looks like a DTD in some way?

    a9_clk_max=1512000000 batfull_threshold=98 batlow_threshold=10 baudrate=115200 boardname=stvmx bootcmd=run nandboot bootdelay=1 bootfile=uImage burnspi=mmcinfo;fatload mmc 0:1 82000000 ${spifile};sf probe 2;sf erase 0 400000;sf write 82000000 0 400000 cecconfig=false chipname=8726m6 console=ttyS0,115200n8 cvbscheck=setenv outputtemp ${outputmode};if test ${outputmode} = 480i; then if test ${cvbsenable} = true; then setenv outputtemp 480cvbs;fi;fi; if test ${outputmode} = 576i; then if test ${cvbsenable} = true; then setenv outputtemp 576cvbs;fi;fi cvbsenable=false display_bpp=24 display_color_bg=0 display_color_fg=0xffff display_color_format_index=24 display_height=480 display_layer=osd1 display_width=720 emac=efuse ethact=Meson_Ethernet ethaddr=00:01:02:03:04:06 fb_addr=0x84900000 gatewayip=192.168.1.1 hdmicecswitch=false hostname=stvmx ipaddr=192.168.1.2 loadaddr=0x82000000 loadaddr_misc=0x83000000 loadlogoaddr=0x84100000 logo_name=logo logo_size=0x400000 logo_start=0 machid=4e27 memsize=1024M mmcargs=setenv bootargs console=${console} root=/dev/cardblksd2 rw rootfstype=ext3 rootwait init=/init logo=osd1,0x84100000,${outputmode} androidboot.resolution=${outputmode} nohlt mem=${memsize} vmalloc=256m mac=${ethaddr} nandargs=run cvbscheck; run readlogo;setenv bootargs console=${console} a9_clk_max=${a9_clk_max} logo=osd1,0x84100000,${outputtemp},full androidboot.resolution=${outputmode} nohlt mem=${memsize} vmalloc=256m mac=${ethaddr} verhw=${verhw} subverhw=${subverhw} hdmitx=${cecconfig} nandboot=echo Booting from nand ...; nand read ${normal_name} ${loadaddr} ${normal_start} ${normal_size}; run nandargs; bootm ${loadaddr} netmask=255.255.255.0 normal_name=boot normal_size=0x800000 normal_start=0 outputmode=720p outputtemp=720p preboot=get_rebootmode; clear_rebootmode; echo reboot_mode=${reboot_mode}; if test ${reboot_mode} = usb_burning; then tiny_usbtool 20000; fi; run upgrade_check; echo updatekeytype=${updatekeytype}; if test ${updatekeytype} = gpio; then run updategpiokey_or_not;else run updatekey_or_not; fi; run switch_bootmode readlogo=nand read ${logo_name} ${loadlogoaddr} ${logo_start} ${logo_size} recovery=run recoveryboot recoveryargs=run readlogo;setenv bootargs console=${console} verhw=${verhw} subverhw=${subverhw} logo=osd1,0x84100000,${outputtemp},full nohlt mem=${memsize} vmalloc=256m mac=${ethaddr} recoveryboot=echo Enter Recovery mode ...; led recovery; sf probe 2; sf read ${loadaddr} 60000 3A0000; run nandargs;bootm ${loadaddr}; run recoverymmc recoverymmc=echo Enter MMC Recovery mode ...; led recovery; mmcinfo;fatload mmc 0 ${loadaddr} uImage_recovery; run nandargs;bootm ${loadaddr} serverip=192.168.1.5 sleep_threshold=20 spifile=spi_mx.bin switch_bootmode=if test ${reboot_mode} = factory_reset; then run recovery;fi; led normal testaddr=0x82400000 update=if mmcinfo; then if fatload mmc 0 ${loadaddr} factory_update_param.ubt; then autoscr ${loadaddr}; fi;fi;run recovery updategpiokey_or_not=if getupdatekey; then msleep 500; if getupdatekey; then run update; fi; fi updatekey_or_not=saradc open 4;if saradc get_in_range 0x0 0x50 ;then msleep 500;if saradc get_in_range 0x0 0x50; then run update; fi; fi upgrade_check=if itest ${upgrade_step} == 1; then setenv upgrade_step 2; save; run recovery; fi upgrade_count=8 upgrade_step=2 usbtty=cdc_acm video_dev=tvout 720poutputx=25 720poutputy=14 720poutputwidth=1224 720poutputheight=692 1080poutputx=42 1080poutputy=22 1080poutputwidth=1832 1080poutputheight=1034 480poutputx=14 480poutputy=8 480poutputwidth=688 480poutputheight=462 480ioutputx=14 480ioutputy=8 480ioutputwidth=688 480ioutputheight=462 576ioutputx=14 576ioutputy=10 576ioutputwidth=688 576ioutputheight=554 576poutputx=14 576poutputy=12 576poutputwidth=688 576poutputheight=552 1080ioutputx=42 1080ioutputy=20 1080ioutputwidth=1834 1080ioutputheight=1042



    Bob
    "Pzebacz im, bo nie wiedzą, co czynią"
    "Прости им, они не ведают, что творят"
    "Perdona loro perché non sanno quello che fanno"
    "Vergib ihnen, denn sie wissen nicht, was sie tun"
    "Vergeef hen want ze weten niet wat ze doen"
    "Pardonne-leur car ils ne savent pas ce qu'ils font"
    "Perdónalos porque no saben que lo que hacen"
    "Oprosti im, jer ne znaju što čine"
    "Forgive them as they know not what they do"





    Comment


      #62
      Hey Chris: The PCB does not look like g18ref/mx2ref...
      Have you taken a look at the picture Stan?

      Sent from my TF300T using Tapatalk

      Comment


        #63
        Originally posted by stane1983 View Post
        No, Matricom played dirty and encrypted their .zip file using openssl. .
        Oh brother! Why the hell would they do that. Sheesh

        OK I get it.

        Bob
        "Pzebacz im, bo nie wiedzą, co czynią"
        "Прости им, они не ведают, что творят"
        "Perdona loro perché non sanno quello che fanno"
        "Vergib ihnen, denn sie wissen nicht, was sie tun"
        "Vergeef hen want ze weten niet wat ze doen"
        "Pardonne-leur car ils ne savent pas ce qu'ils font"
        "Perdónalos porque no saben que lo que hacen"
        "Oprosti im, jer ne znaju što čine"
        "Forgive them as they know not what they do"





        Comment


          #64
          Originally posted by Finless View Post
          Stane I always wondered what the SPI thing was about. What is a SPI chip?

          When I unzip a SPI update it has uboot and recovery but this file env_MX.img.

          Looking at that with a hex editor it has this inside. Looks like a DTD in some way?

          a9_clk_max=1512000000 batfull_threshold=98 batlow_threshold=10 baudrate=115200 boardname=stvmx bootcmd=run nandboot bootdelay=1 bootfile=uImage burnspi=mmcinfo;fatload mmc 0:1 82000000 ${spifile};sf probe 2;sf erase 0 400000;sf write 82000000 0 400000 cecconfig=false chipname=8726m6 console=ttyS0,115200n8 cvbscheck=setenv outputtemp ${outputmode};if test ${outputmode} = 480i; then if test ${cvbsenable} = true; then setenv outputtemp 480cvbs;fi;fi; if test ${outputmode} = 576i; then if test ${cvbsenable} = true; then setenv outputtemp 576cvbs;fi;fi cvbsenable=false display_bpp=24 display_color_bg=0 display_color_fg=0xffff display_color_format_index=24 display_height=480 display_layer=osd1 display_width=720 emac=efuse ethact=Meson_Ethernet ethaddr=00:01:02:03:04:06 fb_addr=0x84900000 gatewayip=192.168.1.1 hdmicecswitch=false hostname=stvmx ipaddr=192.168.1.2 loadaddr=0x82000000 loadaddr_misc=0x83000000 loadlogoaddr=0x84100000 logo_name=logo logo_size=0x400000 logo_start=0 machid=4e27 memsize=1024M mmcargs=setenv bootargs console=${console} root=/dev/cardblksd2 rw rootfstype=ext3 rootwait init=/init logo=osd1,0x84100000,${outputmode} androidboot.resolution=${outputmode} nohlt mem=${memsize} vmalloc=256m mac=${ethaddr} nandargs=run cvbscheck; run readlogo;setenv bootargs console=${console} a9_clk_max=${a9_clk_max} logo=osd1,0x84100000,${outputtemp},full androidboot.resolution=${outputmode} nohlt mem=${memsize} vmalloc=256m mac=${ethaddr} verhw=${verhw} subverhw=${subverhw} hdmitx=${cecconfig} nandboot=echo Booting from nand ...; nand read ${normal_name} ${loadaddr} ${normal_start} ${normal_size}; run nandargs; bootm ${loadaddr} netmask=255.255.255.0 normal_name=boot normal_size=0x800000 normal_start=0 outputmode=720p outputtemp=720p preboot=get_rebootmode; clear_rebootmode; echo reboot_mode=${reboot_mode}; if test ${reboot_mode} = usb_burning; then tiny_usbtool 20000; fi; run upgrade_check; echo updatekeytype=${updatekeytype}; if test ${updatekeytype} = gpio; then run updategpiokey_or_not;else run updatekey_or_not; fi; run switch_bootmode readlogo=nand read ${logo_name} ${loadlogoaddr} ${logo_start} ${logo_size} recovery=run recoveryboot recoveryargs=run readlogo;setenv bootargs console=${console} verhw=${verhw} subverhw=${subverhw} logo=osd1,0x84100000,${outputtemp},full nohlt mem=${memsize} vmalloc=256m mac=${ethaddr} recoveryboot=echo Enter Recovery mode ...; led recovery; sf probe 2; sf read ${loadaddr} 60000 3A0000; run nandargs;bootm ${loadaddr}; run recoverymmc recoverymmc=echo Enter MMC Recovery mode ...; led recovery; mmcinfo;fatload mmc 0 ${loadaddr} uImage_recovery; run nandargs;bootm ${loadaddr} serverip=192.168.1.5 sleep_threshold=20 spifile=spi_mx.bin switch_bootmode=if test ${reboot_mode} = factory_reset; then run recovery;fi; led normal testaddr=0x82400000 update=if mmcinfo; then if fatload mmc 0 ${loadaddr} factory_update_param.ubt; then autoscr ${loadaddr}; fi;fi;run recovery updategpiokey_or_not=if getupdatekey; then msleep 500; if getupdatekey; then run update; fi; fi updatekey_or_not=saradc open 4;if saradc get_in_range 0x0 0x50 ;then msleep 500;if saradc get_in_range 0x0 0x50; then run update; fi; fi upgrade_check=if itest ${upgrade_step} == 1; then setenv upgrade_step 2; save; run recovery; fi upgrade_count=8 upgrade_step=2 usbtty=cdc_acm video_dev=tvout 720poutputx=25 720poutputy=14 720poutputwidth=1224 720poutputheight=692 1080poutputx=42 1080poutputy=22 1080poutputwidth=1832 1080poutputheight=1034 480poutputx=14 480poutputy=8 480poutputwidth=688 480poutputheight=462 480ioutputx=14 480ioutputy=8 480ioutputwidth=688 480ioutputheight=462 576ioutputx=14 576ioutputy=10 576ioutputwidth=688 576ioutputheight=554 576poutputx=14 576poutputy=12 576poutputwidth=688 576poutputheight=552 1080ioutputx=42 1080ioutputy=20 1080ioutputwidth=1834 1080ioutputheight=1042



          Bob
          No, it's defenv of U-Boot. Uboot have predefined environment variables. Take this for example. These are default env variables for m3 MBX device. On newer boards and MX/M8 ubootenv is larger with more values and commands, what to do etc...
          If you find my work useful, buy me a beer
          Homepage: http://www.stane1983.com

          Comment


            #65
            Originally posted by stane1983 View Post

            If you do modifications to decrypted file, resign and encrypt it using same algorithm and key.
            OK so why not use a different recovery and put matricom kernel in that recovery? That way you could make update.zip not encrypted?

            Bob
            "Pzebacz im, bo nie wiedzą, co czynią"
            "Прости им, они не ведают, что творят"
            "Perdona loro perché non sanno quello che fanno"
            "Vergib ihnen, denn sie wissen nicht, was sie tun"
            "Vergeef hen want ze weten niet wat ze doen"
            "Pardonne-leur car ils ne savent pas ce qu'ils font"
            "Perdónalos porque no saben que lo que hacen"
            "Oprosti im, jer ne znaju što čine"
            "Forgive them as they know not what they do"





            Comment


              #66
              Originally posted by stane1983 View Post
              No, it's defenv of U-Boot. Uboot have predefined environment variables. Take this for example. These are default env variables for m3 MBX device. On newer boards and MX/M8 ubootenv is larger with more values and commands, what to do etc...
              OK so it's uboot instruction file. What is a SPI chip though? You said SPI chip and I never heard of that.

              Bob
              "Pzebacz im, bo nie wiedzą, co czynią"
              "Прости им, они не ведают, что творят"
              "Perdona loro perché non sanno quello che fanno"
              "Vergib ihnen, denn sie wissen nicht, was sie tun"
              "Vergeef hen want ze weten niet wat ze doen"
              "Pardonne-leur car ils ne savent pas ce qu'ils font"
              "Perdónalos porque no saben que lo que hacen"
              "Oprosti im, jer ne znaju što čine"
              "Forgive them as they know not what they do"





              Comment


                #67
                Originally posted by Finless View Post
                OK so it's uboot instruction file. What is a SPI chip though? You said SPI chip and I never heard of that.

                Bob
                Wiki definition is here.

                Amlogic platform uses several types of booting their boards.

                On most boxes, usual way for storing bootloader and uboot environment variables is SPI chip, separated from NAND. On MID devices is opposite, most MID solutions from Amlogic are using booting from nand option (same as mx2 box). 3rd boot option is booting from eMMC.
                If you find my work useful, buy me a beer
                Homepage: http://www.stane1983.com

                Comment


                  #68
                  Originally posted by stane1983 View Post
                  Wiki definition is here.

                  Amlogic platform uses several types of booting their boards.

                  On most boxes, usual way for storing bootloader and uboot environment variables is SPI chip, separated from NAND. On MID devices is opposite, most MID solutions from Amlogic are using booting from nand option (same as mx2 box). 3rd boot option is booting from eMMC.
                  Yes Minix is eMMC so that I got. Not so different from NAND though. DTD is different of course.

                  Up until I got that Jynxbox M6, I had never seen a SPI.img before. I get it now thanks!

                  Bob
                  "Pzebacz im, bo nie wiedzą, co czynią"
                  "Прости им, они не ведают, что творят"
                  "Perdona loro perché non sanno quello che fanno"
                  "Vergib ihnen, denn sie wissen nicht, was sie tun"
                  "Vergeef hen want ze weten niet wat ze doen"
                  "Pardonne-leur car ils ne savent pas ce qu'ils font"
                  "Perdónalos porque no saben que lo que hacen"
                  "Oprosti im, jer ne znaju što čine"
                  "Forgive them as they know not what they do"





                  Comment


                    #69
                    Originally posted by kozmo2k4 View Post
                    Hey Chris: The PCB does not look like g18ref/mx2ref...
                    Have you taken a look at the picture Stan?

                    Sent from my TF300T using Tapatalk
                    https://dl.dropboxusercontent.com/co...GuQmqe58AT22SO
                    Back to the...
                    I think so too and if I remember correctly this PCB was discussed some threads past as incompatible....
                    RK3288 Devices
                    - Overview BOX (LINK !)
                    - Overview STICK (Dongle) (LINK !)

                    MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
                    UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
                    Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
                    Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

                    RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
                    Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

                    Comment


                      #70
                      Ouch, sounds like it could be the end of the road for my little black box then? Never mind, it runs 13.1 Gotham quite nicely to be fair but it's just a wast of time for pretty much anything else and annoyingly slow on times.

                      Does anyone have any advice on who to buy from next time? Is there a particular board that is worth looking out for?

                      Thanks again
                      Chris

                      Comment


                        #71
                        Originally posted by dairug View Post
                        Ouch, sounds like it could be the end of the road for my little black box then? Never mind, it runs 13.1 Gotham quite nicely to be fair but it's just a wast of time for pretty much anything else and annoyingly slow on times.

                        Does anyone have any advice on who to buy from next time? Is there a particular board that is worth looking out for?

                        Thanks again
                        Chris
                        If I had this box to test porting ROMs for you, I bet I could do a great ROM. But with the clones and everything.... well.... it's getting untrackable!

                        Bob
                        "Pzebacz im, bo nie wiedzą, co czynią"
                        "Прости им, они не ведают, что творят"
                        "Perdona loro perché non sanno quello che fanno"
                        "Vergib ihnen, denn sie wissen nicht, was sie tun"
                        "Vergeef hen want ze weten niet wat ze doen"
                        "Pardonne-leur car ils ne savent pas ce qu'ils font"
                        "Perdónalos porque no saben que lo que hacen"
                        "Oprosti im, jer ne znaju što čine"
                        "Forgive them as they know not what they do"





                        Comment


                          #72
                          If you were down the road I'd have had it posted to you already! Never mind, perhaps the moral of the story is to buy a Matricom product? Presumably they'll accept most of the Rom images out there at present?

                          Thanks
                          Chris

                          Comment


                            #73
                            I ended up with 14 of these boxes. The seller was Shenzen ******. I had previously bought about 40 boxes from them and they had the regular 2.2 boards.

                            I am guessing these things are going to end up screwing up the market.

                            Wanted to get OPENELEC on these things, guess we are screwed?

                            How did you get to install XBMC gotham? it comes with an XBMC 12.3 that even if i uninstall and reboots it pops back up! cant seem to get rid of it and any other xbmc i put in data/app folder seems to be ignored.
                            Last edited by rojxxx; 08-02-2014, 09:51.

                            Comment


                              #74
                              Hi

                              Sorry,only just seen this. I had mine from same manufacturer. I had four not working and sent them back and demanded a proper board and they have sent me one that I have managed to get Openelec running on.

                              If you ask ****** for access to their 115.com account they have a section of files. In there is a thread called MX2 files for Chris.

                              The files including gotham 13.1 are on there.

                              I found the 12.3 xvmc image on the box was unusable, you couldn't even watch a anything in 720p. The software they supplied fixes this and the box becomes bearable - just!

                              Let me know if you need anything else!

                              Chris

                              Comment


                                #75
                                Re: Does anyone understand AML-AUTOSCRIPT?

                                Originally posted by dairug View Post
                                Hi

                                Sorry,only just seen this. I had mine from same manufacturer. I had four not working and sent them back and demanded a proper board and they have sent me one that I have managed to get Openelec running on.

                                If you ask ****** for access to their 115.com account they have a section of files. In there is a thread called MX2 files for Chris.

                                The files including gotham 13.1 are on there.

                                I found the 12.3 xvmc image on the box was unusable, you couldn't even watch a anything in 720p. The software they supplied fixes this and the box becomes bearable - just!

                                Let me know if you need anything else!

                                Chris
                                @dairug : could you share the 13.1 apk file?

                                Sent from my NookColor using Tapatalk

                                Comment

                                Working...
                                X