headers
ariga masahiro | 4 Feb 2008 02:48
Picon

Re: Re: Wrongfully compiled code

Hello Dave and others,

To Mr.Dave Lawrence,
I have studied a little bit about building sh-elf-gcc.
As I know nothing about Python,I made my shell scripts from it.
I append contents of these shell scripts below.
I could not find out what configure.patch is and how to do it,
so I did not do anything about it.
Perhaps this is the cause of trouble but I explain later.

I decided the directory to hold newly built files to be
/usr/local/sh-elf/bin.

I downloaded next sources into /usr/local/sh-elf
and decompressed them.

binutils-2.16.tar.bz2
gcc-4.1.1.tar.bz2
newlib-1.14.0.tar.gz

After that newly directory looks like below.
/usr
  `-- local
         `-- sh-elf
                 |-- binutils-2.16
                 |-- newlib-1.14.0
                 |-- gcc-4.1.1
                 |-- bin
                 |
(Continue reading)

Permalink | Reply | 3 comments |
headers
Dave Lawrence | 4 Feb 2008 12:37
Picon

Re: Wrongfully compiled code

ariga masahiro wrote:
> Hello Dave and others,
> 
> To Mr.Dave Lawrence,
> I have studied a little bit about building sh-elf-gcc.
> As I know nothing about Python,I made my shell scripts from it.
> I append contents of these shell scripts below.
> I could not find out what configure.patch is and how to do it,
> so I did not do anything about it.
> Perhaps this is the cause of trouble but I explain later.
> 
> I decided the directory to hold newly built files to be
> /usr/local/sh-elf/bin.
> 
> I downloaded next sources into /usr/local/sh-elf
> and decompressed them.
> 
> binutils-2.16.tar.bz2
> gcc-4.1.1.tar.bz2
> newlib-1.14.0.tar.gz
> 
> After that newly directory looks like below.
> /usr
>  `-- local
>         `-- sh-elf
>                 |-- binutils-2.16
>                 |-- newlib-1.14.0
>                 |-- gcc-4.1.1
>                 |-- bin
>                 |
(Continue reading)

Permalink | Reply | 2 comments |
headers
Antonello Lombardinilo | 4 Feb 2008 13:51
Picon

Redboot v2.04, IXP4XX and Flash v2

Hi all, 

I developed board based on Intel IXP435 Multi-Service
Residential Gateway Reference Platform (KIXRP435). 

Main difference is that my board have a 2 flash chip:
a 512 Kbytes boot flash and 16 Mbytes NAND flash. 

I succesfully ported Redboot v.2.04 with boot flash and
npe support on my board.
Now I would also manage NAND flash with FIS.
I readed about eCos/Redboot Flash V2 API, but I'am
confused because the Redboot src that I use are from
RedHat ftp source and not from ecos repository. 

Can someone suggest me how go ahead ? 

 Antonello

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Permalink | Reply | 12 comments |
headers
Tom Deconinck | 4 Feb 2008 14:01
Picon

Re: Redboot v2.04, IXP4XX and Flash v2

Hi,

The eCos Flash v2 code is in a separate repository. It's probably best
to start from the latest of the trunk from ecos.sourceware.org

You just have to replace the following directories with the ones from
the flash v2 branch:
io/flash
dev/flash
redboot
fs/jffs2
Using the flash v2 branch will make it possible to use 2 flashes.

Tom

On Feb 4, 2008 1:51 PM, Antonello Lombardinilo <antonello <at> kasko.it> wrote:
> Hi all,
>
> I developed board based on Intel IXP435 Multi-Service
> Residential Gateway Reference Platform (KIXRP435).
>
> Main difference is that my board have a 2 flash chip:
> a 512 Kbytes boot flash and 16 Mbytes NAND flash.
>
> I succesfully ported Redboot v.2.04 with boot flash and
> npe support on my board.
> Now I would also manage NAND flash with FIS.
> I readed about eCos/Redboot Flash V2 API, but I'am
> confused because the Redboot src that I use are from
> RedHat ftp source and not from ecos repository.
(Continue reading)

Permalink | Reply | 11 comments |
headers
Davies, Greg | 4 Feb 2008 19:19

NAN

Hi,
	I'm trying to compile a program that assigns the value NAN to
some floats to indicate that no real data has come out of a sensor yet.
My problem is that I can't find a header that defines NAN. I used math.h
when I was writing this class the first time around. I even tried using
numeric_limits<float>::quiet_NaN() from <limits> but everything I try
gives me an error along the lines of: NAN is not declared in this scope.

Could there be something I'm missing from the eCos configuration do add
a header that defines NAN? All help is greatly appreciated.

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
Permalink | Reply | 3 comments |
headers
Davies, Greg | 4 Feb 2008 21:22

RE: NAN

 Nevermind, my usual method of asking someone, the list in this case,
made the answer jump out at me. I still can't find the NAN I was using
before, but in my haste I forgot the std:: on the numeric_limits. All is
well in my tiny world now.

-----Original Message-----
From: ecos-discuss-owner <at> ecos.sourceware.org
[mailto:ecos-discuss-owner <at> ecos.sourceware.org] On Behalf Of Davies,
Greg
Sent: Monday, February 04, 2008 2:20 PM
To: ecos-discuss <at> ecos.sourceware.org
Subject: [ECOS] NAN

Hi,
	I'm trying to compile a program that assigns the value NAN to
some floats to indicate that no real data has come out of a sensor yet.
My problem is that I can't find a header that defines NAN. I used math.h
when I was writing this class the first time around. I even tried using
numeric_limits<float>::quiet_NaN() from <limits> but everything I try
gives me an error along the lines of: NAN is not declared in this scope.

Could there be something I'm missing from the eCos configuration do add
a header that defines NAN? All help is greatly appreciated.

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

--

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andrew Lunn | 4 Feb 2008 21:31
Picon

Re: NAN

On Mon, Feb 04, 2008 at 02:19:39PM -0400, Davies, Greg wrote:
> Hi,
> 	I'm trying to compile a program that assigns the value NAN to
> some floats to indicate that no real data has come out of a sensor yet.
> My problem is that I can't find a header that defines NAN. I used math.h
> when I was writing this class the first time around. I even tried using
> numeric_limits<float>::quiet_NaN() from <limits> but everything I try
> gives me an error along the lines of: NAN is not declared in this scope.
> 
> 
> Could there be something I'm missing from the eCos configuration do add
> a header that defines NAN? All help is greatly appreciated.

I could not find anywhere in the sources where NAN is
defined. Interesting isnan() is available, but it uses hard coded
values.

According to C99 it should be in <math.h>.

I wounder if the problem is to do with none-signalling NAN against
signalling NAN. NAN should have a value which does not cause a
floating point exception to be raised. But that is architecture
dependent. So maybe the HAL needs to define it. That is messy, so
maybe it has just been left out.

So you probably need to declare it yourself. This should help you
figure out the value:

        int isnan(double x)
{
(Continue reading)

Permalink | Reply | 1 comment |
headers
Antonello Lombardinilo | 5 Feb 2008 12:06
Picon

Re: Redboot v2.04, IXP4XX and Flash v2

Hi Tom, 

i replace io/flash, dev/flash and redboot directories
with latest flash v2 snapshot from ecoscentric ftp server.
I made some change to compile:
 - add devs/flash/arm/kixrp435 directory;
 - replace redboot/current/include/redboot.h with original file 

The compilation seems to work fine.
I try to enable FLASH_V2 support. I replace CYGPKG_DEVS_FLASH_STRATA
with CYGPKG_DEVS_FLASH_STRATA_V2 in ecos.db and
hal/arm/xscale/kixrp435/current/misc/redboot_RAM.ecm 

When I try to import configuration I get a following error:
[root <at> AntoPC001 kixrp435_npe_RAM]# ecosconfig new kixrp435_npe redboot
U CYGHWR_HAL_ARM_XSCALE_CPU, new inferred value IXP43x
U CYGSEM_HAL_USE_ROM_MONITOR, new inferred value 0
U CYGIMP_HAL_COMMON_INTERRUPTS_USE_INTERRUPT_STACK, new inferred value 0
[root <at> AntoPC001 kixrp435_npe_RAM]# ecosconfig import 
/home/antonello/projects/eCos/redboot-intel-ixp4xx-070320/packages/hal/arm/x 
scale/kixrp435/current/misc/redboot_RAM.ecm
C CYGHWR_IO_FLASH_DEVICE, "requires" constraint not satisfied:  
CYGHWR_IO_FLASH_DEVICE >= 1
C CYGPKG_DEVS_FLASH_KIXRP435, "requires" constraint not satisfied: 
CYGPKG_DEVS_FLASH_STRATA_V2
[root <at> AntoPC001 kixrp435_npe_RAM]# 

I want test flash v2 on kixrp435 board to make sure that the hardware works.
The kixrp435 board have 2 flash chips: strata flash and nand flash.
(Continue reading)

Permalink | Reply | 10 comments |
headers
Rasmus Stougaard | 5 Feb 2008 14:11
Picon

How to disable c++ exceptions, -fno-exceptions has no effect?

Hi,

How do I avoid including the code for c++ exceptions in my ecos application?

My target is at91sam7s256.

I am compiling with
arm-elf-g++ -c -o SolarController.o
-I/home/stou/ecos_workspace/myproject/ecos/install/include
-DGCONF_TARGET_ECOS_ARM7  -Wall  -g -Os -DGCONF_USE_PEG
-mcpu=arm7tdmi -Wall -Wpointer-arith -Winline -Wundef
-Woverloaded-virtual -ffunction-sections -fdata-sections -fno-rtti
-fno-exceptions

And linking with:

arm-elf-gcc  -o t80_main.elf -nostartfiles -Wall
-Wl,--Map,"mapfile.tmp" -mcpu=arm7tdmi -Wl,--gc-sections -Wl,-static
-Wl,-n -g -nostdlib
-L/home/stou/ecos_workspace/myproject/ecos/install/lib -Ttarget.ld
-fno-exceptions

However my code crashes like this:
[snip]
terminate called after throwing an instance of 'St9bad_alloc'
  what():  St9bad_alloc
[/snip]

From which I conclude that the exceptions are included although I do
not use them explicitly in my code, from what I could figure out it is
(Continue reading)

Permalink | Reply | 3 comments |
headers
Tom Deconinck | 5 Feb 2008 14:53
Picon

Re: Redboot v2.04, IXP4XX and Flash v2

Hi,

Sorry,

I forgot to mention that you'll need to add the flash v2 packages to
your ecos.db file so that they are known to the configuration system.

Also, the package that enables your flash support should implement
CYGHWR_IO_FLASH_DEVICE, this will tell eCos how many flashes are
available on your platform.
I'm not sure which package it should be for your setup since I'm not
familiar with your particular setup, maybe someone else can clarify
...

Tom

On Feb 5, 2008 12:06 PM, Antonello Lombardinilo <antonello <at> kasko.it> wrote:
> Hi Tom,
>
> i replace io/flash, dev/flash and redboot directories
> with latest flash v2 snapshot from ecoscentric ftp server.
> I made some change to compile:
>  - add devs/flash/arm/kixrp435 directory;
>  - replace redboot/current/include/redboot.h with original file
>
> The compilation seems to work fine.
> I try to enable FLASH_V2 support. I replace CYGPKG_DEVS_FLASH_STRATA
> with CYGPKG_DEVS_FLASH_STRATA_V2 in ecos.db and
> hal/arm/xscale/kixrp435/current/misc/redboot_RAM.ecm
>
(Continue reading)

Permalink | Reply | 9 comments |

Gmane