Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Type 'help' for help | Logs: -> irc.armbian.com
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
<cheakoirccloud> Vendor is asking me if a QCA9984(WMX6301) replaces QCA9880? For the ebin.
<cheakoirccloud> Again ppl have seemingly little regard for each and every digit. WMX6"4"01.
<cheakoirccloud> Are QCA9984's much more expensive? It looks intimidating with that heat sink.
<sunshavi> i have a an rk3229 tvbox. I have downloaded armbian burn to SD and it is not booting
<sunshavi> I have also downloaded multitool burned it to SD an it boots
<sunshavi> why armbian img does boot directly on tvbox is something missing?
<[TheBug]> huh?
<[TheBug]> all tvbox is CSC
<[TheBug]> so if your grabbing an image its probably something community gave
<[TheBug]> but if you take an image for another rk3229 device and try to load it on a tvbox ist isn't just going to 'work'
<[TheBug]> often hardware is very different
<[TheBug]> and would require specific uboot or dtb
<sunshavi> TheBug: ok. multitool boots
<sunshavi> and also multitool has an specific dtb
<[TheBug]> if you for example did download an image for that box and it not boot it could be that some item in your revision is differnt also
<sunshavi> perhaps what is missing is a u-boot binary
<[TheBug]> for me to give you a better guess you would have to provide what you are specifically trying to load (which image) etc
<[TheBug]> and about your device
<sunshavi> device is an rk3229
<sunshavi> armbian was gotten from this link https://www.armbian.com/rk322x-tv-box/
<sunshavi> on that web page there is an option for booting from SD. But it need erasing flash with multitool first
<[TheBug]> is it that exact box?
<sunshavi> yes
<[TheBug]> ohh I see its a generic image anyhow
<sunshavi> No it is not the exact box. Mine says 'MXQPRO 5G 4K'
<sunshavi> adb shell says it is an rk3229
<[TheBug]> is multitool the software that puts it into programming mode?
<sunshavi> multitool seems to be derived from armbian. it boots and shows a cli menu
<[TheBug]> ohh yes
<[TheBug]> so way that reads to me
<[TheBug]> if you must boot from emmc or write emmc
<sunshavi> on that cli menu you could launch a bash console
<sunshavi> So I did.
<[TheBug]> the sdcard you will write the multitool then put the armbian image on it
<[TheBug]> then it should auto program the emmc on boot
<sunshavi> mmm. I was just hoping it could boot directly from SD. But It seems that-one is not an option
<[TheBug]> here is important parts
<[TheBug]> if you are running the original firmware you need to first erase the internal eMMC; to do so download the Multitool, burn it on an SD Card, plug the SD Card and power the TV Box. Use “Backup flash” if you want to do a backup of the existing firmware, then choose “Erase flash” menu option.
<[TheBug]> Build or download your preferred Armbian image;
<[TheBug]> Uncompress and burn the Armbian image on the SD Card;
<[TheBug]> so if you want boot sdcard, you must first wipe the emmc because on this board it will always boot emmc first so if OS exists, it will boot there
<[TheBug]> if you want sdcard you have to have it empty or not have a boot loader
<[TheBug]> then it will drop to sdcard and boot
<sunshavi> ok. I would need to do all of that. But default or original-firmware has netflix working :(
<[TheBug]> yeah what I do if possible
<[TheBug]> if you can get some terminal access or enough access you can access emmc
<[TheBug]> then I would dd over netcat or ssh to another machine a copy of the image
<[TheBug]> then maybe you could use multitool to re-write again later if you need
<[TheBug]> I would not just abadon the firmware without back-up if you know it works
<[TheBug]> (thats just me)
<[TheBug]> I am not sure what options you have
<[TheBug]> if you can root android
<[TheBug]> then you can do it from terminal
<[TheBug]> standard busybox should have nc and dd
<[TheBug]> sunshavi: for me I have a whole drive full of just various images and states from original images for devices to different chnages I have made and tried
archetyp has joined #armbian
<sunshavi> I accesed it from adb shell by wifi
<sunshavi> but multitool let's You do a backup
<sunshavi> Just as I saw multitool launching from SD. I though it could be possible booting directly from SD without erasing emmc
<sunshavi> TheBug: thanks for the help
<[TheBug]> well
<[TheBug]> TBH sunshavi
<[TheBug]> you can 'cheat' some
<[TheBug]> but it still makes it 'unbootable' without some work
<[TheBug]> effectively if you remove uboot from emmc it will boot sdcard
<[TheBug]> so you can technically keep contents of the emmc and remove uboot from it
<[TheBug]> you would have to find t he offsets but you could find the uboot offset, dump it to sdcard, overwite on emmc with 0
<[TheBug]> then it would boot sdcard and still have emmc file system
<[TheBug]> it just wouldn't boot emmc without you putting uboot back or making a custom uboot on your sdcard that knows how to boot emmc
<sunshavi> That would be great
<[TheBug]> but that is a bit more comprehensive than justa beginners method
<[TheBug]> that is why it is not documented there
<[TheBug]> if you have root abd shell and busybox though you should be able to do that
<[TheBug]> but my caution is I would for sure make full back-up before you make changes if you care about it
<[TheBug]> in case you do it wrong y ou won't be freaking out
<[TheBug]> you can use their tool if you are confident inthat or you can use dd over netcat pretty easy if you have network
<[TheBug]> then you can find uboot offset in docs and then back up uboot, then dd over with 0
<[TheBug]> (/dev/zero)
<[TheBug]> then it will boot sdcard when booted
<sunshavi> I have network. I have just done a backup with multitool. I am going to launch multitool again and watch multitool having two images {Armbian and original-firmware}
<sunshavi> i am going to put armbian on emmc. boot it once. launch multitool. and restore original firmware on emmc. Just hoping for the best. Also I am going to measure time. Perhaps It is quick doing that.
CrashTestDummy2 has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 252 seconds]
<sunshavi> TheBug: I am just thinking. perhaps the multitool backup option (does a full back-up). So it is the same as having done that with dd
sams has quit [Quit: ZNC 1.7.2+deb3 - https://znc.in]
sndbg has joined #armbian
sndb has quit [Ping timeout: 272 seconds]
archetyp has quit [Quit: Leaving]
archetyp has joined #armbian
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 246 seconds]
CrashTestDummy3 has quit [Read error: Connection reset by peer]
archetyp` has joined #armbian
archetyp has quit [Ping timeout: 252 seconds]
CrashTestDummy has joined #armbian
CrashTestDummy2 has joined #armbian
CrashTestDummy has quit [Ping timeout: 252 seconds]
archetyp` has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Client Quit]
archetyp has joined #armbian
Tables has quit [Quit: Leaving]
indy has quit [Ping timeout: 246 seconds]
indy has joined #armbian
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #armbian
shoragan has quit [Ping timeout: 256 seconds]
shoragan has joined #armbian
sndbg has quit [Remote host closed the connection]
peterm6881 has joined #armbian
slacker_HD has joined #armbian
DarthGandalf has quit [Quit: Bye]
DarthGandalf has joined #armbian
slacker_HD has quit [Quit: Connection closed]
The-going has joined #armbian
nick_ has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
peterm6881 has quit [Remote host closed the connection]
peterm6881 has joined #armbian
Guest16 has joined #armbian
nick_ has quit [Quit: Leaving]
Guest16 has quit [Quit: Client closed]
CrashTestDummy3 has joined #armbian
CrashTestDummy2 has quit [Ping timeout: 246 seconds]
<peterm6881> does anybody know what bot is needed for irc logging to whitequark?
<steev> probably just use https://github.com/whitequark/irclogger?
<peterm6881> hey steev
<steev> hi
archetyp has quit [Remote host closed the connection]
<nekomancer[m]> seems JDY-33(https://www.aliexpress.com/item/4001130387437.html) not a solution for SBC console access ☹️
<Armbian-Discord> <I​gorPec> bluetooth sucks 😉
<Armbian-Discord> <I​gorPec> i have a bunch of normal ones, connected to devices
* nekomancer[m] can't push that into "AT" command mode.
<nekomancer[m]> and discover maximum transfer (not terminal) speed is 38800. not default for sbc 115200
<nekomancer[m]> why I buy it? why I hope 1$ device can replace console cable?
<Armbian-Discord> <I​gorPec> i have one around somewhere, but somehow doesn't use
<Armbian-Discord> <I​gorPec> when you have no response on console - you have just yet another level to troubleshoot
CrashTestDummy2 has joined #armbian
CrashTestDummy3 has quit [Ping timeout: 268 seconds]
BluesBoy has joined #armbian
_whitelogger has joined #armbian
peterm6881 has quit [Quit: Leaving]
peterm6881 has joined #armbian
The-going has quit [Quit: Konversation terminated!]
archetyp has joined #armbian
archetyp has quit [Remote host closed the connection]
archetyp has joined #armbian
peterm6881 has quit [Remote host closed the connection]
<stipa> haha, Trump is suing Facebook, Twitter and Google
sunshavi has quit [Ping timeout: 265 seconds]
lanefu has quit [Ping timeout: 256 seconds]
Fleck has quit [Remote host closed the connection]
Fleck has joined #armbian
crabbedhaloablut has quit [Ping timeout: 244 seconds]
crabbedhaloablut has joined #armbian