is there a way to run the compiled arm on Nexus S ?

cem akpolat akpolatcem at gmail.com
Mon Nov 3 10:50:05 CET 2014


Cem Akpolat

On Sat, Nov 1, 2014 at 10:21 AM, Adam Lackorzynski <
adam at os.inf.tu-dresden.de> wrote:

> On Thu Oct 30, 2014 at 13:11:24 +0100, cem akpolat wrote:
> > Thank you first of ally your responses.  I haven't unfortunately JTAG
> > component right now and also the equipment like Matthias mentioned. How
> > about the fastboot? Is it also possible to use fastboot for sending
> android
> > image? l4 generates bootstrap_L4LinuxARM.elf file, and we can convert
> this
> > image file into the u-boot image file as explained in [1] with the
> > following command.
>
> There's a fastboot make target, so you can just issue:
>   make fastboot E=...
> and it will load the rawimage using fastboot.
>
> I converted it but it seems that either the given address is not true or
> > this method doesn't work.
>
> Typically rawimage must be used with fastboot but there are also cases
> for uimages (use 'make fastboot_uimage' then), it depends. In your case
> it loads fine but then nothing happens on the target? If that's the case
> it's just guessing what could be the cause...
>
> I used fastboot and the message whet I try to load the image is as below

akpolat at akpolatX240:~/mysvn/arm_l4android/src/l4$ make fastboot -C
/home/akpolat/mysvn/arm_l4android/src/l4/ elfimage E=L4LinuxARM
O=/home/akpolat/mysvn/arm_l4android/src/build/l4/
make: Entering directory `/home/akpolat/mysvn/arm_l4android/src/l4'
make[1]: Entering directory
`/home/akpolat/mysvn/arm_l4android/src/l4/pkg/bootstrap/server/src'
make[2]: Entering directory
`/home/akpolat/mysvn/arm_l4android/src/build/l4/pkg/bootstrap/server/src/OBJ-arm_armv7a'
  Image size(s) in bytes:
       bootstrap_L4LinuxARM.elf:  9970040
                  bootstrap.raw:  9936896
  Start address: 0x71000000
  --> Build-Nr: 27
make[2]: Leaving directory
`/home/akpolat/mysvn/arm_l4android/src/build/l4/pkg/bootstrap/server/src/OBJ-arm_armv7a'
make[1]: Leaving directory
`/home/akpolat/mysvn/arm_l4android/src/l4/pkg/bootstrap/server/src'
creating boot image...
creating boot image - 9938944 bytes
downloading 'boot.img'...
OKAY [  1.540s]
booting...


Considering the given output, it seems that the boot.img is loaded but
booting process cannot start. I applied the same steps for uimage instead
of elfimage and the result is again the same as below.

akpolat at akpolatX240:~/mysvn/arm_l4android/src/l4$ make fastboot -C
/home/akpolat/mysvn/arm_l4android/src/l4/ uimage E=L4LinuxARM
O=/home/akpolat/mysvn/arm_l4android/src/build/l4/
make: Entering directory `/home/akpolat/mysvn/arm_l4android/src/l4'
make[1]: Entering directory
`/home/akpolat/mysvn/arm_l4android/src/l4/pkg/bootstrap/server/src'
make[2]: Entering directory
`/home/akpolat/mysvn/arm_l4android/src/build/l4/pkg/bootstrap/server/src/OBJ-arm_armv7a'
  Image size(s) in bytes:
       bootstrap_L4LinuxARM.elf:  9970040
                  bootstrap.raw:  9936896
  Start address: 0x71000000
  --> Build-Nr: 27
make[2]: Leaving directory
`/home/akpolat/mysvn/arm_l4android/src/build/l4/pkg/bootstrap/server/src/OBJ-arm_armv7a'
make[1]: Leaving directory
`/home/akpolat/mysvn/arm_l4android/src/l4/pkg/bootstrap/server/src'
creating boot image...
creating boot image - 9938944 bytes
downloading 'boot.img'...
OKAY [  1.540s]
booting...


These outputs raise of course some questions such as I really load the
image into the right address or I use the right command for the
compilation.

In all above mentioned cases, what I am see is only the Google log along
with a lock on the screen.


Thanks again for your quick reply.
Cem

>
>
> Adam
> --
> Adam                 adam at os.inf.tu-dresden.de
>   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
>
> _______________________________________________
> l4-hackers mailing list
> l4-hackers at os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://os.inf.tu-dresden.de/pipermail/l4-hackers/attachments/20141103/dde38e7c/attachment.html>


More information about the l4-hackers mailing list