Closed mj-sakellaropoulos closed 3 years ago
I pleasantly surprised someone other than me would be interested in this device. I don't own too many devices, but I can already tell that this one is special.
I have not checked out the 4.4 kernel + dtb. Thanks for pointing that out.
Aside from mainline kernel, I have tried 3.0.21, 3.0.31, 3.0.72, 3.4.48 downstream kernels. All of which have framebuffer + LCD backlight + touchscreen support. In addition, I was able to get WIFI working with 3.0.X kernels. I originally started my documentation two years ago (privately) on the downstream kernels, but when I figured out how to boot mainline kernels with device tree blobs, I wanted to share my progress.
I actually do remember trying the debian rootfs from XDA from years ago, but was not heavily involved in that project nor do I even have the rootfs backed up. Even so, there is no point in returning to that specific rootfs since the packages are outdated. In fact, I currently use a postmarketOS rootfs which allows me to install and run the latest tools and packages :).
I haven't managed to get the mainline booting yet with my builroot system, I'm going to try out your defconfig and dts. Also by the way, what voltage is the UART / what adapter are you using?
UART setup: Logic Level Converter Sparkfun FT232RL breakout Note that a resistor has to be swapped out for the logic level converter (as shown below).
I am getting some recognizable text, but its mangled, what are your port settings ?
115200n8 at 1V8
Ah, looks like I'm going to need that 1.8v adapter then. Thanks!
USB (gadget) serial works, but UART is still recommended
Yeah, I'm pretty sure the kernel is crashing somewhere, because its not enumerating as an ethernet or serial gadget - or anything at all. UART definitely a must.
Not to mention, with UART, you get access to U-Boot console which is something you can't get with USB.
If you have not already, recompile Hashcode's 2014 u-boot port with device tree enabled. My fork can be summarized by the following changes: https://github.com/hansemro/kf_u-boot/commit/9f990c0fd608fe2e449f1fee9f1f596e0cc78ee1 https://github.com/hansemro/kf_u-boot/commit/3415e83bcb963a15ef75527677cc6ac2897a0263
Note: I don't believe it was necessary to change the machine type.
If you have not already, recompile Hashcode's 2014 u-boot port with device tree enabled.
Huh, according to the forum post, I though devicetree was already supported. Thanks.
Right now i'm using the uboot from the debian project until I can properly backup my mmc. Ive dumped it with dd, but i dont know if i will be able to reapply the image later
I think we are the only two people in the world left working on this. It's a nice, well-built device with fairly beefy OMAP, would surely benefit from an updated linux!
I will update this if I find anything else useful