Actions
Forum Thread Details
  • Replies 1 reply
  • Subscribers 21 subscribers
  • Views 251 views
  • Users 0 members are here
Related

Installed Android on board. Now Terminal not working... ??

mubase

Hi all. image

I recently re-installed Android onto my board to see whether my monitor converter worked. It works with Linux.

The monitor didn't work at first and I was getting a message on the screen saying "display mode not supported" so I changed the environment settings to this:

setenv bootargs console=ttymxc1,115200 init=/init nosmp video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32 video=mxcfb1:off fbmem=10M vmalloc=400M androidboot.console=ttymxc1 androidboot.hardware=freescale

 

and the Android logo came up (although a a bit big) and so did the android screen. It looks different than the one seen on other pictures though... The HDMI sound also works.

One problem that has occured is with the Terminal. When the board is reset I see the boot info come up and the 3 second countdown.. after the 3 second countdown the screen fills up with mainlt garbage and it stays like that..

Anyone have the same problem or know whats going on??

  • You'll get that effect if the baud rate the linux console is set to is different from the u-boot console. Usually they're both set to 115200 and it all just works. Your bootargs line looks fine, so I don't see why it would be a problem.

    After you changes bootargs, did you run saveenv ?

     

    You can also check what u-boot thinks bootargs is by pressing the key to break into the u-boot shell and typing printenv.

     

    Saving the u-boot environment may or may not survive a reflash between linux and android, but a linux env on an android boot (and vice versa) may not give good results.