fabiobassa
-
Posts
212 -
Joined
-
Last visited
Everything posted by fabiobassa
-
@zero48 ......... night is made for sleeping for mostly people on the earth, but not for tecnicians ajajajajaj
-
@zero48 well you have 2 possibilities: method 1 : @jock method of shorten emmc and boot from multitool method 2 : flash the original android rom that will set up again the original u-boot and trust-os and once the board is started and you have android on video, shut-off and boot again from sd card and multiboot, this TIME NO NEED TO SHORT emmc because you have original android boot sequence in place . You need original rom and a male - male usb cable and this tool AndroidTool_Release_v2.67.zip ( search on net ) In both manners you need the multitool for flashing a new image on emmc, with second method if android starts you are also sure that no physical or less damages occurred to emmc before you try to flash a new armbian image
-
But with the sd-multitool have you at least a try-to-boot ? Those boards are UNBRICKABLE because the real bootstrap is in the soc itself. I have many with broken nand or emmc that I desoldered and they boot flawlessly from SD of course with right ddrbin U-Boot and the hellish trust-os. Later if is phisically broken the sdcard reader, well YES it died with honor LOL ( And.... ... There still is last thing to try but the process is long)
-
@zero48 well also could be physical damage of EMMC or bad bga chip solder In that case you could try to start with multitool , press exit to shell ( menu 4 ? ) , do a list block lsblk and try to manually mount the emmc or nand somewhere ( under /mnt or under /tmp) and inspect it
-
@zero48 Please zero48 really no needed to short pins . The concept of multitool is booting WHATEVER is in the board ( android, other linux, whatever) and flash in the EMMC or NAND " something" that will boot later , when multitool has set GPT, boot environment ( u-boot and trust os) and root file system. As you can see the ddrbin ( the very first first first part ) is booting, it says to you that you have a ddr 3 at 600 Mhz and also is booting u-boot 2020.04 After this no more messages from uart ! Well some scenarios: 1) the uart speed in the beginning is different after u-boot start (EXAMPLE : ddrbin at 1500000 and then u-boot at 115200 ) 2) something went wrong in flashing image SOLUTIONS ( maybe... ) 1) set 115200 FROM BEGINNING : you will see some wrong characters and then correct booting or set from beginning 1500000 2) flash another armbian may be more recent as @jock already suggested EDIT post scriptum where did you downloaded this image?
-
@Maker39 not more than yesterday, in private chat @jock and me we were saying that this 3ad is SUPER because many others users, such as you actively help people. This is right spirit of a forum
-
@Flávio Lima hello Flavio it depends what scope you have for this box, I can say even 1gb of ram is okay Wait if @jock has some mirror for older versions
-
@zero48 I said it: this box WILL WORK !!! Congrats
-
@zero48 yes @jock is absolutely right , you havent a NAND since the multitool IS NOT offering you the choice of nand. you have an emmc so follow other instructions
-
@zero48 Well remember to use LEGACY IMAGES since main line kernel HAS NOT drivers for nand. Those board are so many different each from other that is always a jungle to decide the right thing to burn on it rk3228a or 3228b.. maybe 3229...ddr 2 or perhaps ddr3, emmc instead of nand , ssv6051 as wifi or better rtl8189 and why not an 8188, trust os or better trust_with_ta or the last trust you tested But once the picture is complete I can only say you those board work quite well p.s calcutating the time shift.. you did at 4 in the morning ( madrugada ??) ?? If yes ,well nerd people are egual in every part of the world ahahahahaahh
-
@zero48 Check your private messages Cesar. Anyway regarding your bootlogs, still something wrong because strange symbols appear . Please check ground connection to uart or even better solder it. I have pl 2303 and it goes both on 115200 and 1500000 The board is booting and booting fine Cesar !!!!!
-
@zero48 que diablura es esa? qual brujeria tiene esta board, ajajajaaj Let's go back at english that is official and common language here, but let me say you live in my 3rd house : Italy, Cuba, Santo domingo !! Ok back to board, definetly a speed issue or may be wrong pins, you just swapped tx and rx ? Ground = black I suppose is in right position , first on right But I am also sure you already tried to swap them The speed in normal android is 1 million 5 hundred thousand 1500000 did you check this ? may be missing a zero ?
-
@jock Based on our previous experiences with china producers ( 4 giga of ram, 64 gb of storage and the 2/16 really , or even worst..) would you put your hand on fire that really is android 10 inside ?
-
@zero48 No way Cesar, it will work... it MUST work, now the problem is watch WHO will win, the board itself or ourselves !!!! Ok ttl TIME. connect the converter, on the board is clearly marked the tx and rx and SET the putty speed to 1500000 ( YES !! one million 500000 , thanks rockchip for this unusual speed) you will see the very early booting of ddr ( it should say ddr3 330 mhz ) and some other things such as optee Then the speed changes to usual 115200 so is bit problematic since you must close putty change speed and open back I suggest to do this : 1)start the board and grab log of putty at 1500000 until optee ( i hope you go at least to optee ) . close putty 2) set putty at 115200 reopen putty and REBOOT board. You will see initial wrong characters since wrong speed but then the speed goes to right one we need both logs one at 1500000 and the other at 115200 where you located Cesar ? EDIT: pleae grab also a full boot from Android , at 1500000
-
@megaduo Please would you be so kind to take some photos of the board ? @jock and me , we suspect one of the few we haven't tested in real environment thank you
-
@megaduo for this kind of specific problems @jock is the one !!! wait till he answers
-
@zero48 perfet is a godness you have electronic skills I suspect you have one fo the few, but very few hellish boards that use a particular trust os , so before attach any uart to ttl do this little test please: copy this trust os into your card, you will need linux thought SYNTAX is : dd if=/wheredoyouhavefile/trust-ddr2.img of=/dev/thisisyoursdcard/ seek=24576 so if for example your sd is sdc and you have this file in /home/zero48 the whole syntax will be dd if=/home/zero48/trust-ddr2.img of=/dev/sdc seek=24576 of course you must unzip first the file If this little test go wrong, well uart is our salvation trust-ddr2.zip
-
@Flávio Lima Bom Dia Flavio, yes the forum is in english please be so kind to use that language. Despite of this I understand a bit portoguese so for your question and as far as I know rk322x board DO NOT HAVE 4 gb ram, almost at actual time the maximum I have seen is 2 giga Usually shishion 5G have 2 giga of ram
-
@zero48 indeed the procedure that maker is suggesting you is correct and one of the best And really the booting sequence of those boards allow the box to boot from internal, search if exist a trustos and uboot on the card and then boot from the card if valid things are found. I guess android is working, or are you trying to boot with shorten pins and/or android erased ? If yes please revert to ideal cndition of android in place and working last question : have you sufficient skill to setup a uart converter to debug what is going on ? On that board solder a pl2303 is very easy And please guys , when you receive support is a costless thing to just put a " like ( heart icon) " , not for vanity having as many likes is possible , but because this helps the reputations and reliability of users trying to help your efforts and also strengthens the sense of community and the purpose of a forum. ty @Maker39
-
@zero48 as already @Maker39 said you don 't need nothing to start from sd but the sd itself Mee too I always use win32disk imager so first extract the content of the xz file and burn it with win32imager
-
@megaduo have you original firmware with wifi surely working? If yes can you extract the original dtb ?
-
@zero48 Your board is one on which we worked a lot, is well known and totally and well supported in armbian. It has NAND so pay attention : you have to use stePnand for internal installation ; it has DDR3 upvto 768 MHz so is one of my favourites for his speed You will be very satisfied of it !!! Thank you for photos, cheers EDIT: Those lovely China producers.. It should be a 3228 with one or two giga of ram. Look at what they say .. 4 GB ram...... Anyway you can check those infos with the efuse and with " free" command. Please read back the forum since there are many useful infos you can grab from the board with some command lines
-
@zero48 Sure follow jock's suggestions and you will hit the goal. Your photos are on drive but request authorization for watching maybe better if you can make them public even to non Gmail users . Thise photos could help someone else
-
@zero48 This sounds strange the moltitool itself is less than 200 mega so a normal sd of 4 giga should accomodate both the multitool itself and the image you want to transfer on the box. which method are you using to prepare the sd card ? balena etcher ? win32imager ? And how big is this sd card ? Cheers
-
@valik228 I am glad everything is working and don't blame on yourself but little strange things happen with those boards. Well enjoy the new Linux tvbox
