Re: [ECOS] Hello_eCos_World on iPAQ.

Re: [ECOS] Hello_eCos_World on iPAQ.

[Gary Thomas]

Note: email which is not sent to the discussion list (or at least copied to it)
will be automatically discarded from now on.  Please use the list.

On 24-Apr-2001 Victor Tarasov wrote:
> Thank you very much for the attention.
> 
> Gary Thomas wrote:
> 
>> This is probably not what you really wanted to do.  You'll need to build
>> a separate configuration just for the 'hello' program, like this (in a
>> directory just for this):
>>   % mkdir /tmp/ipaq_ecos
>>   % cd /tmp/ipaq_ecos
>>   % ecosconfig new ipaq
>>   % ecosconfig tree
>>   % make
> 
> I tried this sequence also. During the compilation of the libraries it looks for:
>>packages/devs/touch/arm/ipaq/current/src/ipaq_ts.c:57: cyg/fileio/fileio.h: No
> such file or directory
> 
> The only fileio.h that I found in the CVS distribution is
> packages/io/fileio/current/include/fileio.h,
> so, I added it manually to the install directory, but afterwards it looks for
> pkgconf/io_fileio.h
> That one, I have not found in the CVS distribution.
> 

Yes, there was a problem here.  This can be fixed by adding the command
  % ecosconfig add fileio
just before the 'ecosconfig tree' line.

> 
>> > PS: How can I recompile RedBoot for iPAQ?
>> > "RedBoot" template with the imported configuration
>> > $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
>> > (also redboot_rom.ecm)
>> > gives the binaries that are not working on the iPAQ.
>> > The templates "all", "default" and "stubs" give the error during
>> > compilation.
>>
>> Why do you want to recompile RedBoot?
> 
> It's  some kind of  desparate action:
> before to dive deeply into the investigation of eCos and its configuration options
> ,
> I would like to have something  that was compiled and is working on iPAQ.
> (That's why I was asking you for the configuration for the building of  the
> ipaq_Compaq.bin,
> that you sent me recently. In the CVS the ECMs for ipaq were not updated.)

There were no changes required to that file for the fixes I made.  Here's how
to build that file:
  % ecosconfig new ipaq redboot
  % ecosconfig import $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
  % ecosconfig tree
  % make
The resulting file 'install/bin/redboot.bin' is what is distributed as "redboot.Compaq".

Re: [ECOS] Hello_eCos_World on iPAQ.

[Jonathan Larmour]

Gary Thomas wrote:
> > I would like to have something  that was compiled and is working on iPAQ.
> > (That's why I was asking you for the configuration for the building of  the
> > ipaq_Compaq.bin,
> > that you sent me recently. In the CVS the ECMs for ipaq were not updated.)
> 
> There were no changes required to that file for the fixes I made.  Here's how
> to build that file:
>   % ecosconfig new ipaq redboot
>   % ecosconfig import $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
>   % ecosconfig tree
>   % make
> The resulting file 'install/bin/redboot.bin' is what is distributed as "redboot.Compaq".

I think the issue is that anon CVS is not uptodate with respect to those
changes. I was going to do it last Friday, but timed out. Ditto Monday,
ditto today :-|. Tomorrow for sure.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] Hello_eCos_World on iPAQ.

[Victor Tarasov]

> I think the issue is that anon CVS is not uptodate with respect to those
> changes. I was going to do it last Friday, but timed out. Ditto Monday,
> ditto today :-|. Tomorrow for sure.

Thank you, now I can recompile redboot and seems it works properly on the iPAQ.


Another question:
I try to debug Hello application through the unique serial port of iPAQ.

Could you suggest any reason why writing to the /dev/ttydiag or to the /dev/haldiag kills the target
>19        printf("Hello, eCos world %i!\n",i);
>(gdb) step
>Sending packet: $m20558,4#d1...Ack
>Packet received: 1730a0e3
>...........................
>Sending packet: $c#63...Ack
After that, I can get back RedBoot only reset of iPAQ.


Victor.

Re: [ECOS] Hello_eCos_World on iPAQ.

[Gary Thomas]

On 26-Apr-2001 Victor Tarasov wrote:
>> I think the issue is that anon CVS is not uptodate with respect to those
>> changes. I was going to do it last Friday, but timed out. Ditto Monday,
>> ditto today :-|. Tomorrow for sure.
> 
> Thank you, now I can recompile redboot and seems it works properly on the iPAQ.
> 
> 
> Another question:
> I try to debug Hello application through the unique serial port of iPAQ.
> 
> Could you suggest any reason why writing to the /dev/ttydiag or to the /dev/haldiag kills the
> target
>>19        printf("Hello, eCos world %i!\n",i);
>>(gdb) step
>>Sending packet: $m20558,4#d1...Ack
>>Packet received: 1730a0e3
>>...........................
>>Sending packet: $c#63...Ack
> After that, I can get back RedBoot only reset of iPAQ.

Tell us more about this, how you built it, which version of RedBoot you
are using etc.  AFAIK we do this all the time.

Re: [ECOS] Hello_eCos_World on iPAQ.

[Victor Tarasov]

Gary Thomas wrote:

> On 26-Apr-2001 Victor Tarasov wrote:
> > Another question:
> > I try to debug Hello application through the unique serial port of iPAQ.
> >
> > Could you suggest any reason why writing to the /dev/ttydiag or to the /dev/haldiag kills the
> > target
> >>19        printf("Hello, eCos world %i!\n",i);
> >>(gdb) step
> >>Sending packet: $m20558,4#d1...Ack
> >>Packet received: 1730a0e3
> >>...........................
> >>Sending packet: $c#63...Ack
> > After that, I can get back RedBoot only reset of iPAQ.
>
> Tell us more about this, how you built it, which version of RedBoot you
> are using etc.  AFAIK we do this all the time.

Host:
Linux 2.4.0 #5 Fri Mar 23 10:33:08 CET 2001 i686 unknown

ARM development tools for Linux:
GCC core 2.95.2
GCC C++ 2.95.2
ecos-gcc-2952.pat
binutils-2.10.1
GDB 5.0

I use anonymous CVS distribution version for 26.04.2001.
Install:
 % ecosconfig new ipaq
 % ecosconfig add fileio
 % ecosconfig tree
 % make

RedBoot:
 % ecosconfig new ipaq redboot
 % ecosconfig import  redboot_Compaq.ecm
 % ecosconfig tree
 % make

RedBoot version:
RedBoot(tm) bootstrap and debug environment - built 14:14:14, Apr 26 2001
Platform: Compaq iPAQ Pocket PC (StrongARM 1110)
Copyright (C) 2000, 2001, Red Hat, Inc.
RAM: 0x00000000-0x01fc0000, 0x0001f400-0x01f70000 available

Hello-application compiled with:
arm-elf-gcc -mcpu=strongarm  -c -o hello.o -g -Wall -I/redboot/tmp_ecos/install/include
-ffunction-sections -fdata-sections hello.c
arm-elf-gcc -mcpu=strongarm  -nostartfiles -L/redboot/tmp_ecos/install/lib -Wl,--gc-sections -o
hello hello.o -Ttarget.ld -nostdlib

Victor.

Re: [ECOS] Hello_eCos_World on iPAQ.

[Gary Thomas]

How does this relate to your problem?  Can you send your 'hello' application (source)?

I tried these steps with our sample 'hello' program and there had no problems.

On 30-Apr-2001 Victor Tarasov wrote:
> 
> Gary Thomas wrote:
> 
>> On 26-Apr-2001 Victor Tarasov wrote:
>> > Another question:
>> > I try to debug Hello application through the unique serial port of iPAQ.
>> >
>> > Could you suggest any reason why writing to the /dev/ttydiag or to the /dev/haldiag kills the
>> > target
>> >>19        printf("Hello, eCos world %i!\n",i);
>> >>(gdb) step
>> >>Sending packet: $m20558,4#d1...Ack
>> >>Packet received: 1730a0e3
>> >>...........................
>> >>Sending packet: $c#63...Ack
>> > After that, I can get back RedBoot only reset of iPAQ.
>>
>> Tell us more about this, how you built it, which version of RedBoot you
>> are using etc.  AFAIK we do this all the time.
> 
> Host:
> Linux 2.4.0 #5 Fri Mar 23 10:33:08 CET 2001 i686 unknown
> 
> ARM development tools for Linux:
> GCC core 2.95.2
> GCC C++ 2.95.2
> ecos-gcc-2952.pat
> binutils-2.10.1
> GDB 5.0
> 
> I use anonymous CVS distribution version for 26.04.2001.
> Install:
>  % ecosconfig new ipaq
>  % ecosconfig add fileio
>  % ecosconfig tree
>  % make
> 
> RedBoot:
>  % ecosconfig new ipaq redboot
>  % ecosconfig import  redboot_Compaq.ecm
>  % ecosconfig tree
>  % make
> 
> RedBoot version:
> RedBoot(tm) bootstrap and debug environment - built 14:14:14, Apr 26 2001
> Platform: Compaq iPAQ Pocket PC (StrongARM 1110)
> Copyright (C) 2000, 2001, Red Hat, Inc.
> RAM: 0x00000000-0x01fc0000, 0x0001f400-0x01f70000 available
> 
> Hello-application compiled with:
> arm-elf-gcc -mcpu=strongarm  -c -o hello.o -g -Wall -I/redboot/tmp_ecos/install/include
> -ffunction-sections -fdata-sections hello.c
> arm-elf-gcc -mcpu=strongarm  -nostartfiles -L/redboot/tmp_ecos/install/lib -Wl,--gc-sections -o
> hello hello.o -Ttarget.ld -nostdlib
> 
> Victor.
> 
> 

Re: [ECOS] Hello_eCos_World on iPAQ.

[Victor Tarasov]

Gary Thomas wrote:

> How does this relate to your problem?  Can you send your 'hello' application (source)?
>
> I tried these steps with our sample 'hello' program and there had no problems.
>

Here is my 'hello':
#include <stdio.h>

int main(void)
{
  int i=23;
  printf("Hello, eCos world! %i\n",++i);
  ++i;
  return 0;
}


It seems that target console output do not pass through 'mangler'.
With the diagnostics output directed to the channel 0, the "$O..#" message, can be seen on the host.


#include <stdio.h>
#include <cyg/hal/hal_arch.h>           /* CYGNUM_HAL_STACK_SIZE_TYPICAL */
#include <cyg/hal/hal_if.h>

const char test_string[] = "$O5468697320697320612074657374206d657373616765210d0a#12";

int main(void)
{
  int i=23, cur;

  cur = CYGACC_CALL_IF_SET_CONSOLE_COMM(CYGNUM_CALL_IF_SET_COMM_ID_QUERY_CURRENT);
  CYGACC_CALL_IF_SET_CONSOLE_COMM(0);
  printf("%s\n",test_string);
  CYGACC_CALL_IF_SET_CONSOLE_COMM(cur);
  printf("%s\n",test_string);
  i++;
  return 0;
}
Target dies after the second printf.


>
> On 30-Apr-2001 Victor Tarasov wrote:
> >
> > Gary Thomas wrote:
> >
> >> On 26-Apr-2001 Victor Tarasov wrote:
> >> > Another question:
> >> > I try to debug Hello application through the unique serial port of iPAQ.
> >> >
> >> > Could you suggest any reason why writing to the /dev/ttydiag or to the /dev/haldiag kills the
> >> > target
> >> >>19        printf("Hello, eCos world %i!\n",i);
> >> >>(gdb) step
> >> >>Sending packet: $m20558,4#d1...Ack
> >> >>Packet received: 1730a0e3
> >> >>...........................
> >> >>Sending packet: $c#63...Ack
> >> > After that, I can get back RedBoot only reset of iPAQ.
> >>
> >> Tell us more about this, how you built it, which version of RedBoot you
> >> are using etc.  AFAIK we do this all the time.
> >
> > Host:
> > Linux 2.4.0 #5 Fri Mar 23 10:33:08 CET 2001 i686 unknown
> >
> > ARM development tools for Linux:
> > GCC core 2.95.2
> > GCC C++ 2.95.2
> > ecos-gcc-2952.pat
> > binutils-2.10.1
> > GDB 5.0
> >
> > I use anonymous CVS distribution version for 26.04.2001.
> > Install:
> >  % ecosconfig new ipaq
> >  % ecosconfig add fileio
> >  % ecosconfig tree
> >  % make
> >
> > RedBoot:
> >  % ecosconfig new ipaq redboot
> >  % ecosconfig import  redboot_Compaq.ecm
> >  % ecosconfig tree
> >  % make
> >
> > RedBoot version:
> > RedBoot(tm) bootstrap and debug environment - built 14:14:14, Apr 26 2001
> > Platform: Compaq iPAQ Pocket PC (StrongARM 1110)
> > Copyright (C) 2000, 2001, Red Hat, Inc.
> > RAM: 0x00000000-0x01fc0000, 0x0001f400-0x01f70000 available
> >
> > Hello-application compiled with:
> > arm-elf-gcc -mcpu=strongarm  -c -o hello.o -g -Wall -I/redboot/tmp_ecos/install/include
> > -ffunction-sections -fdata-sections hello.c
> > arm-elf-gcc -mcpu=strongarm  -nostartfiles -L/redboot/tmp_ecos/install/lib -Wl,--gc-sections -o
> > hello hello.o -Ttarget.ld -nostdlib
> >
> > Victor.
> >
> >

[ECOS] Hello_eCos_World on iPAQ.

[Victor Tarasov]

Hi,
It seems that I am not so intelligent to run alone my first RedBoot
application on iPAQ.
Can you help me, please?

Package installation was made by:
>ecosconfig new ipaq redboot
>ecosconfig import redboot_RAM.ecm
>ecosconfig resolve
>ecosconfig tree
>make

Hello_eCos was compiled with:
>arm-elf-gcc -mcpu=strongarm                      -c -o hello.o -g -Wall
-I/redboot/ecos-ram/install/include -ffunction-sections -fdata-sections
hello.c
>arm-elf-gcc -mcpu=strongarm                      -nostartfiles
-L/redboot/ecos-ram/install/lib -Wl,--gc-sections -o hello hello.o
-Ttarget.ld -nostdlib /redboot/ecos-ram/install/lib/version.o

Then GDB:
>arm-elf-gdb  -nw  hello

(gdb) set remotebaud 38400
Remote debugging using /dev/ttyS1
0x50105890 in ?? ()
(    After several attempts  another version of gdb answer at this
stage:
     Remote debugging using /dev/ttyS1
     0x25748 in _breakinst () at
/opt/ecos/ecos_massiot/packages/hal/arm/arch/current/src/hal_misc.c:220
     220         HAL_BREAKPOINT(_breakinst);
)

(gdb) load
Loading section .rom_vectors, size 0x40 lma 0x20000
Loading section .text, size 0x18adc lma 0x20040
Loading section .rodata, size 0xbacc lma 0x38b1c
Loading section .data, size 0x17e4 lma 0x445e8
Start address 0x20040 , load size 155084
Transfer rate: 26971 bits/sec, 305 bytes/write.

(gdb) break main
Function "main" not defined.

(gdb) continue
Continuing.

Nothing happens after.

Victor.

PS: How can I recompile RedBoot for iPAQ?
"RedBoot" template with the imported configuration
$ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
(also redboot_rom.ecm)
gives the binaries that are not working on the iPAQ.
The templates "all", "default" and "stubs" give the error during
compilation.

RE: [ECOS] Hello_eCos_World on iPAQ.

[Gary Thomas]

On 23-Apr-2001 Victor Tarasov wrote:
> Hi,
> It seems that I am not so intelligent to run alone my first RedBoot
> application on iPAQ.
> Can you help me, please?
> 
> Package installation was made by:
>>ecosconfig new ipaq redboot
>>ecosconfig import redboot_RAM.ecm
>>ecosconfig resolve
>>ecosconfig tree
>>make
> 
> Hello_eCos was compiled with:
>>arm-elf-gcc -mcpu=strongarm                      -c -o hello.o -g -Wall
> -I/redboot/ecos-ram/install/include -ffunction-sections -fdata-sections
> hello.c
>>arm-elf-gcc -mcpu=strongarm                      -nostartfiles
> -L/redboot/ecos-ram/install/lib -Wl,--gc-sections -o hello hello.o
> -Ttarget.ld -nostdlib /redboot/ecos-ram/install/lib/version.o
> 

This is probably not what you really wanted to do.  You'll need to build
a separate configuration just for the 'hello' program, like this (in a
directory just for this):
  % mkdir /tmp/ipaq_ecos
  % cd /tmp/ipaq_ecos
  % ecosconfig new ipaq
  % ecosconfig tree
  % make

Then re-do your commands, but use /tmp/ipaq_ecos instead of /redboot/ecos-ram
  <<snip>>

> 
> PS: How can I recompile RedBoot for iPAQ?
> "RedBoot" template with the imported configuration
> $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
> (also redboot_rom.ecm)
> gives the binaries that are not working on the iPAQ.
> The templates "all", "default" and "stubs" give the error during
> compilation.

Why do you want to recompile RedBoot?

Re: [ECOS] Hello_eCos_World on iPAQ.

[Jonathan Larmour]

Victor Tarasov wrote:
> 
> Hi,
> It seems that I am not so intelligent to run alone my first RedBoot
> application on iPAQ.
> Can you help me, please?

Are you using the precompiled binaries available from 
http://sources.redhat.com/ecos/boards/ipaq.html ?

Once you know you've got something working, then you will probably find it
easier to rebuild and be sure there aren't any problems with e.g. your
tools etc.

> Package installation was made by:
> >ecosconfig new ipaq redboot
> >ecosconfig import redboot_RAM.ecm
> >ecosconfig resolve
> >ecosconfig tree
> >make
> 
> Hello_eCos was compiled with:
> >arm-elf-gcc -mcpu=strongarm                      -c -o hello.o -g -Wall
> -I/redboot/ecos-ram/install/include -ffunction-sections -fdata-sections
> hello.c
> >arm-elf-gcc -mcpu=strongarm                      -nostartfiles
> -L/redboot/ecos-ram/install/lib -Wl,--gc-sections -o hello hello.o
> -Ttarget.ld -nostdlib /redboot/ecos-ram/install/lib/version.o
> 
> Then GDB:
> >arm-elf-gdb  -nw  hello

It looks what you are describing is that you are using the build tree
configured with "ecosconfig new ipaq redboot" to build your applications.
This isn't right - the redboot template is used solely for building redboot
itself. Instead start with a new clean build tree and just use a default
configuration like:

ecosconfig new ipaq
ecosconfig tree
make

In fact then do:

make tests

which will build some test applications under install/tests/ which you can
try out on the board, which may help avoid any pilot error in building the
hello world example.

> PS: How can I recompile RedBoot for iPAQ?
> "RedBoot" template with the imported configuration
> $ECOS_REPOSITORY/packages/hal/arm/sa11x0/ipaq/current/misc/redboot_Compaq.ecm
> (also redboot_rom.ecm)
> gives the binaries that are not working on the iPAQ.
> The templates "all", "default" and "stubs" give the error during
> compilation.

Do recompile RedBoot you must use the redboot template only. Make sure you
are using a new clean build tree when you build for a different template. 

I take it you are following the instructions in the RedBoot user's guide on
installing for the ipaq, of course.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine