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

Thanks Adam, I will try to figure out it and inform you about the last
status. Your guess can be true, but I have to find out too what drivers are
missing. As you mentioned, firstly I have to see what is going on.

Cem

Cem Akpolat

On Mon, Nov 3, 2014 at 11:41 PM, Adam Lackorzynski <
[email protected]> wrote:

> On Mon Nov 03, 2014 at 10:50:05 +0100, cem akpolat wrote:
> > On Sat, Nov 1, 2014 at 10:21 AM, Adam Lackorzynski <
> > [email protected]> 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@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.
>
> The process of fastboot looks ok to me.
>
> > 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.
>
> It will be stuck somewhere. For this case you need the UART (or JTAG) to
> see what's going on. Further, to see something on the display, there
> need to be proper drivers for this particular device. I'd guess those
> are not there?
>
>
>
>
> Adam
> --
> Adam                 [email protected]
>   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
>
> _______________________________________________
> l4-hackers mailing list
> [email protected]
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>

_______________________________________________
l4-hackers mailing list
[email protected]
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers