<whoMAN>
Then on the boot partition, I edited the extlinux.conf to point the root uuid to the ext4 partition.
<whoMAN>
I do not beleive I have corretly written the U-boot to the SD card, because the tvbox boots straight to android.
<whoMAN>
As a test, I downloaded the ROCK64 SD image, used Disk Image Writer on ubuntu to write to my SD.
<whoMAN>
When I use this ROCK64 image, my tvbox does not boot (as expected since the U-boot is for rk3288), but it does not boot into android either, it just hangs at a black screen.
<whoMAN>
This suggests that the tvbox does not see my 'rk3229-etb' SD card's U-boot (if it did, it would either hang at a black screen or boot into debian)
<whoMAN>
2 questions:
<whoMAN>
1. is the 'rk3229-etb' argument the correct way to build the U-boot and kernel for this rk3229 tvbox?
<whoMAN>
2. am I writing the U-boot correctly to the SD, with the above mentioned dd commands?
lurchi_ has joined #linux-rockchip
lurchi__ has quit [Ping timeout: 256 seconds]
vstehle has joined #linux-rockchip
Easyfab has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
xerpi has joined #linux-rockchip
<whoMAN>
sorry typo... I mean 'rk2339-evb'
<whoMAN>
okay so I found the loader scripts... I ran these 2 commands to create my system.img and then to write to the SD card... same result
<whoMAN>
build/mk-image.sh -c rk322x -t system -r rk-rootfs-build/linaro-rootfs.img
<whoMAN>
build/flash_tool.sh -c rk322x -d /dev/sdc -p system -i out/system.img
<whoMAN>
There's a pinhole on the bottom of the device. I thought perhaps that was for maskrom mode, but when I hold it down and boot, it goes into "android recovery", and at the bottom is says:
<whoMAN>
E:failed to mount /mnt/external_sd (no such device)
<whoMAN>
although if I boot into android, it does see the SD within android settings
Aussie_matt has joined #linux-rockchip
Aussie_matt has quit [Remote host closed the connection]
afaerber has joined #linux-rockchip
<mmind00>
whoMAN: for maskrom, generic tv boxes most often have test points somewhere next to emmc ... btw. first things first ... is it nand of emmc?
cnxsoft has quit [Remote host closed the connection]
wzyy2 has joined #linux-rockchip
chen has joined #linux-rockchip
chen is now known as Guest93527
aalm has joined #linux-rockchip
wzyy2 has quit [Ping timeout: 240 seconds]
Guest93527 has quit [Ping timeout: 240 seconds]
Jabader has joined #linux-rockchip
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
xerpi has quit [Quit: Leaving]
lurchi_ is now known as lurchi__
lurchi__ is now known as lurchi_
clone147 has joined #linux-rockchip
mrueg has quit [Ping timeout: 240 seconds]
aalm has quit [Ping timeout: 240 seconds]
BenG83 has quit [Ping timeout: 276 seconds]
clone147 has quit [Quit: Page closed]
mrueg has joined #linux-rockchip
BenG83 has joined #linux-rockchip
whoMAN has joined #linux-rockchip
<whoMAN>
mmind00: Thank you for the info. It's nand. So when I short the pins on the NAND, it does not boot up at all. It just goes to a black screen, and then eventually the display goes to sleep.
<whoMAN>
I would be willing to try flashing to NAND however this box doesn't have an OTG port.
<whoMAN>
If the U-boot was successfully found and the kernel image loaded, would I see a spash screen? or would this happen after it finds the rootfs? I'm just wondering if it's seeing my U-Boot on the SD at all
<mmind00>
WHOman: you'll definitly need a serial console when working at this level
<mmind00>
aka Display stuff is coming at the very end, if everything else works already
<mmind00>
and if you shorting nand pins you end up in maskrom, which doesn't output anything on the serial console ... but one of your usb-a ports will most likely connected to the otg controller, you just need a USB A-A cable
<whoMAN>
mmind00: Ahhh I didn't realize that. So I can either solder and rs232 connector to the serial pinouts, or I can use USB A to A cable to flash to NAND.
<whoMAN>
mmind00: my question is, once I get into a serial console, what steps are necessary to get HDMI working? I haven't seen any info regarding this, and just assumed that the kernel/rootfs would boot with HDMI
<whoMAN>
mmind00: I'm trying to determine if I would be easier to solder an rs232 connector, or to just flash my image to the NAND with USB A to A cable in maskrom mode
mrueg has quit [Ping timeout: 240 seconds]
<whoMAN>
or I suppose I would need the serial console regardless of SD card or NAND, correct?
mrueg has joined #linux-rockchip
<mmind00>
exactly :-)
<mmind00>
WHOman: display stuff is always the last thing you'll get working, and before that a million tiny things can fail, so when working on bootloader+kernel you'll nearly always need a serial console
<mmind00>
WHOman: just to mention ... serial pins are TTL level, so no real rs232
<whoMAN>
mmind00: ahh okay. I'm wondering Since I'm only interested in testing the Rockchip GST plugins on debian, maybe it would be simpler to just purchase a tvbox with rk3288, and use images from ROCK64. I've seen posts where specific boxes don't need maskrom to boot to SD.
<whoMAN>
mmind00: Do you think that would be the simpler route, or would I end up with the same situation needing a serial console as well?
<mmind00>
WHOman: may be easier (and work) for your case ... but a serial console is always good to have
<beeble>
or maybe just buy a rock64 if you are planning to use the rock64 image anyway?
<whoMAN>
beeble: That was my original consideration, but the only reason I'm hesitant to do that is I'm interested in eventually getting WiFi working as well.
<beeble>
get a usb wifi adapter for a few bucks and then it's pretty painless
<beeble>
but i would also recommend to get a serial cable no matter what route you choose
<whoMAN>
Okay will do. Thanks much mmind00 and beeble for the info and advice
<BenG83>
if you use SDIO wifi on RK3328 you loose the gmac
<BenG83>
that's why you see a lot of TV boxes with wifi and only FE
lurchi_ is now known as lurchi__
mrueg has quit [Ping timeout: 256 seconds]
mrueg has joined #linux-rockchip
aalm has joined #linux-rockchip
mrueg has quit [Ping timeout: 256 seconds]
mrueg has joined #linux-rockchip
mrueg has quit [Ping timeout: 240 seconds]
mrueg has joined #linux-rockchip
Easyfab has quit [Quit: Leaving]
matthias_bgg has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
xerpi has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
Fuzzy_ has joined #linux-rockchip
Aussie_matt has joined #linux-rockchip
<Fuzzy_>
Hi guys, I have a silly question, how come the GPU and VPU work on 4.4 but not on 4.14?
<mmind00>
Fuzzy_: that's easy ... vpu stuff is still work in progress (especially regarding the mainline kernel) and the mali gpu uses a binary-userspace, so the (also quite crappy) kernel-part is not acceptable
<mmind00>
Fuzzy_: gpu also depends on your soc ... aka for Mali400 we have seen quite a bit of progress on the revived lima driver and the Malis in rk3288+rk3399 may get a free driver at some later point, as the panfrost project is still quite young
<Fuzzy_>
thanks mmind00
<Fuzzy_>
is there a website I can refer to?
<Fuzzy_>
ie. the mainline effort page for the RK33xx VPU/GPU?