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,
Hi Seehwan, Serial UART setting are documented in www.community.arm.com/.../using-linaros-deliverables-on-juno (as long as flow control is OFF that looks correct) Yes even without a USB stick, you should see some moans about the missing ramdisk after the autoboot countdown. This should happen after a couple of seconds. ** You didn't confirm you'd erased the board's flash? ** ** Also (if you didn't already) you must erase the whole contents of the MMC card & copy across the entire contents of /juno-lsk-android-uboot (So that's the MB, SITE1, SOFTWARE and the 3 top level text files) not just the SOFTWARE directory - as per instructions. ** But... If neither of these things help, I'm afraid we will need to arrange for you to return the board. To do this 1. email juno-support@arm.com with a brief summary (essentially reference this Community thread). 2. Fill in & attach this fault form to the email: infocenter.arm.com/.../ka4138.html Note we can't do anything to progress a repair without the information in the fault form. MarkN.
Hi, >Is firmware, bootloader source available? How can I get >the custom build? With each release we may also update the motherboard BIOS code, along with various other elements of proprietary software. So it's expected that the versions vary. This is why it's critical to update the whole contents of the recovery image (as per my last mail) rather than just the SOFTWARE directory. There might be dependencies. We don't release this motherboard code and you shouldn't need it. >recompile and booting with new firmware as >Jerome suggested For every release the binaries (and sources) are tested and should work "as is". We know the binaries work as supplied on our Juno r0 (and various others in ARM). Of course it is possible problems are only exposed on specific boards. Regardless, recompiling with different upstream sources (in this scenario) doesn't seem likely to be profitable unless we know there's a problem to be fixed. But, you are free to try. You can also download the older binaries manually as zip archives if you want to experiment. Simply edit the YY.MM suffix using: releases.linaro.org/.../ It would definitely be interesting to know if there's a point where things start/stop working for you. >Thankfully, still binary is updated; if I update binary >with UEFI-sth, the uboot does not show up, and UEFI >shell-like command appears. >However UEFI shell also seems to fail at some >moment. It does not take input, and stops to print >message at some point. Sorry I'm confused about what exactly you have tried. you wrote: >My old binary boots up the board... You mean.. you can boot all the way to a Linux command prompt? (Which release is this binary from)? >However UEFI shell also seems to fail at >some moment. It does not take input, >and stops to print message at some point. You mean you tried the 16.12 (UEFI) based binaries & these freeze? I'll double check with a wider (Juno r0 using) audience internally at ARM to see if anyone else has had similar problems. But, it's likely a return is the only way forward (ARM can provide) if I don't hear anything useful.