[okl4-developer] Debugging tips for a new platform

Geoffrey Lee glee at ok-labs.com
Thu Jun 19 21:07:35 EST 2008


On Thu, Jun 19, 2008 at 08:58:49PM +1000, Joshua Root wrote:
> Geoffrey Lee wrote:
>> On Thu, Jun 19, 2008 at 07:33:39PM +1000, Joshua Root wrote:
>>
>> /* snip */
>>
>>>> I got a fresh 2.1 tarball and skyeye 1.2.5 off skyeye.org and did
>>>> ./configure; make, built OKL4 with gumstix and ran that and worked fine.
>>>> To take a step back, can you at least confirm that it works on skyeye
>>>> 1.2.5 for gumstix?
>>> No, that's what I'm saying. I can't get a gumstix image to work in   
>>> anything other than the 1.2.1n build linked from the wiki. Same 
>>> result  with 2.1 and 2.1.1-fix.7.
>>
>>
>> Ah, I noticed that you are using image.sim.  Please re-try with
>> image.boot.
>
> Gumstix doesn't seem to build an image.boot.


Building for Gumstix should definitely yield an image.boot as
this is the binary used for booting hardware.  Stepping back a step,
can you confirm that with the pre-built toolchain, youc an generate
a image.boot for the gumstix platform for an unmodified 2.1 release?

Also, what command line are you using?  You should be able to do
with something like

./tools/build.py machine=gumstix project=l4test



>
> The little-endian binary is for gumstix. I'm trying it first because I  
> know it's a working image. If I can't get gumstix to work in the  
> simulator, nslu2 has no chance.
>
> Building with machine=nslu2 definitely uses the correct toolchain and  
> produces a big-endian binary.

OK, cool.

>>
>> Just to ensure that we are on the same page, can you confirm that 
>> booting image.boot when compiled in MSB mode will yield a binary that 
>> spins
>> on trying to write out via serial?
>
> I haven't yet been able to boot a big-endian image in the simulator.

I got a copy of the 2.1 release, applied your patch against the 2.1
release, and then made the changes described previously and built
using the pre-built toolchain, using 

./tools/build.py machine=nslu2 project=l4test and that yielded
a image.boot in build/images/.  Somewhere we may be doing something
different :(


>
> - Josh

	-gl




More information about the Developer mailing list