• State Accepted Answer
  • +2 person also asked this people also asked this
  • Locked Locked
  • Replies 16 replies
  • Subscribers 20 subscribers
  • Views 52284 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Juno r0 does not boot with linaro android after u-boot

seehwan

Hi, 

I am using Juno r0, and want to run android on that. 

So, I tried to work with 1) prebuilt linaro repo, 2) build from source for linaro 16.12.

However, it does not working after u-boot.

In fact, it seems like it stops in the middle of u-boot.

When I stop the boot process in the u-boot, the entire board stops in a few second. 

When it stops, u-boot terminal console does not work, and I cannot give any input to boot command to u-boot.

It seems like I am working with wrong version.

 

Please let me know whether the latest linaro version does not work with Juno r0.

In addition, if it is the case, please let me know which is the correct version I can work with.

 

Regards,

Parents Reply Children
  • 0 in reply to Mark Nicholson
    Mark,

    Thanks for your effort.
    Yesterday, I successfully boot up the android, mixing some binaries.

    The final result is as follows:
    MBbios-1.4.4
    SOFTWARE directory is from my old binary.
    (Unfortunately, I don't know where exactly it came from. It boots up with UEFI bootmgr, the old binary seems to be oe-minimal boot with UEFI.)
    Then, I overwrite the following three files in order to have Android boot up.
    -. kernel image, dtb, initrd
    I took those files from recent prebuilt binary's SOFTWARE directory;
    At the UEFI bootmgr, I set up another entry, fill in kernel bootargs, etc.


    My conclusion.
    Some of SOFTWARE directory files do not work with my board.
    If kernel works with UEFI, I would be okay.
    I hope for future kernel-firmware interface does not change.

    I have failed when I try with u-boot, so u-boot would not work with me, for now.

    Regards,
    Seehwan
  • 0 Arm Employee Badge in reply to seehwan
    OK. I'm glad you have something booting, but as we know 16.12 works on multiple r0 boards....Clearly there's something wrong here that's specific to you board/environment. Possibly something operating at the outside edge of tolerances that just happens to be exposed by a change in the SW stack. Possibly something much more mundane, but I'm unable to guess what that would be. It may even be a serial / terminal emulation specific issue. i.e. the board might have booted (and you simply fail to see I/O via serial). You could try plugging a monitor in to check. Impossible to say for sure.

    An Android environment that boots with UEFI will be based on deliverables 1 year (ish?) old.

    >I hope for future kernel-firmware interface does not change.

    Unfortunately we can't guarantee that. Nor can we guarantee that the "mixed" environment you have booting is reliable. Obviously you need to balance the desire to carry on with your work, with the delays involved in a return/repair.
    MarkN.