On Sat, Aug 20, 2016 at 07:26:46PM -0700, Leonardo wrote: > Hi. I'm building a very minimal Linux distro to use as an embedded system > on a A20 tablet. I don't want to believe this, but I think that booting my > distro has damaged the device. The tablet came with Android. I had it > rooted so I could extract the fex file. Then I got kernel 3.4.104 and uboot > 2016.02 from GitHub, built my file system with buildroot and so on. I'm > using an SD card for now. So I tried booting my system and nothing came up > on the LCD. Then I remove my SD card, try to get back to Android and still > nothing on the screen! The device is not dead. I can access it using ssh > over the wifi, the usb port works fine. Basically I can do anything > remotely. At first I thought I might have damaged something on the PCB > while performing the tests, so I had a second tablet. Boot on Android, > display works fine. Boot on my distro, nothing on screen. Try to get back > to Android, and nothing on the screen again. By the way, the backlight > lights up as usual, so the display is not dead also. I've worked on a > similar project last year and had no problem like this at all. I have no > idea what went wrong. Is it possible that my kernel has damaged the device > somehow?
Damage, no. Ruined nand content due to different settings, yes. Thank allwinner for changing its mind on how to configure its nand controller in the middle of the A20 lifetime, while having code in its nand driver that clears the ram if it finds garbage. Luc Verhaegen. -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
