public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: James Yates <j.yates@quartzuk.com>
Cc: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] Problems with var_mk_defs.c
Date: Wed, 15 Oct 2003 15:09:00 -0000	[thread overview]
Message-ID: <1066230547.32461.54.camel@hermes> (raw)
In-Reply-To: <CB39E7B8FC98924D85DFBED207E4CC9834420C@ip02.quartzelec.adsl.gxn.net>

On Wed, 2003-10-15 at 09:03, James Yates wrote:
> Gary,
> 
> When I compile the following is output:
> 
> make -r -C hal/sh/arch/current /ecos-d/Dev/eCos/builds/current/pc388_install/include/cyg/hal/sh_offsets.inc
> make[1]: Entering directory `/ecos-d/Dev/eCos/builds/current/pc388_build/hal/sh/arch/current'
> sh-elf-gcc -mb -m2 -O2 -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -ggdb -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority  -I/ecos-d/Dev/eCos/builds/current/pc388_install/include -I/ecos-d/ecos/ecos/packages/hal/sh/arch/current -I/ecos-d/ecos/ecos/packages/hal/sh/arch/current/src -I/ecos-d/ecos/ecos/packages/hal/sh/arch/current/tests -I. -Wp,-MD,sh_offsets.tmp -o hal_mk_defs.tmp -S /ecos-d/ecos/ecos/packages/hal/sh/arch/current/src/hal_mk_defs.c
> fgrep .equ hal_mk_defs.tmp | sed s/#// > /ecos-d/Dev/eCos/builds/current/pc388_install/include/cyg/hal/sh_offsets.inc
> make[1]: Leaving directory `/ecos-d/Dev/eCos/builds/current/pc388_build/hal/sh/arch/current'
> make -r -C hal/sh/sh2/current /ecos-d/Dev/eCos/builds/current/pc388_install/include/cyg/hal/sh2_offsets.inc
> make[1]: Entering directory `/ecos-d/Dev/eCos/builds/current/pc388_build/hal/sh/sh2/current'
> sh-elf-gcc -mb -m2 -O2 -Wall -Wpointer-arith -Wstrict-prototypes -Winline -Wundef -Woverloaded-virtual -ggdb -ffunction-sections -fdata-sections -fno-rtti -fno-exceptions -fvtable-gc -finit-priority  -I/ecos-d/Dev/eCos/builds/current/pc388_install/include -I/ecos-d/ecos/ecos/packages/hal/sh/sh2/current -I/ecos-d/ecos/ecos/packages/hal/sh/sh2/current/src -I/ecos-d/ecos/ecos/packages/hal/sh/sh2/current/tests -I. -Wp,-MD,sh2_offsets.tmp -o var_mk_defs.tmp /ecos-d/ecos/ecos/packages/hal/sh/sh2/current/src/var_mk_defs.c
> make[1]: Leaving directory `/ecos-d/Dev/eCos/builds/current/pc388_build/hal/sh/sh2/current'
> /ecos-c/temp/ccmMeZK9.s: Assembler messages:
> make: Leaving directory `/ecos-d/Dev/eCos/builds/current/pc388_build'
> /ecos-c/temp/ccmMeZK9.s:26: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:26: Warning: rest of line ignored; first ignored character is `0'
> /ecos-c/temp/ccmMeZK9.s:29: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:29: Warning: rest of line ignored; first ignored character is `0'
> /ecos-c/temp/ccmMeZK9.s:32: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:32: Warning: rest of line ignored; first ignored character is `0'
> /ecos-c/temp/ccmMeZK9.s:35: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:35: Warning: rest of line ignored; first ignored character is `6'
> /ecos-c/temp/ccmMeZK9.s:38: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:38: Warning: rest of line ignored; first ignored character is `1'
> /ecos-c/temp/ccmMeZK9.s:41: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:41: Warning: rest of line ignored; first ignored character is `8'
> /ecos-c/temp/ccmMeZK9.s:44: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:44: Warning: rest of line ignored; first ignored character is `0'
> /ecos-c/temp/ccmMeZK9.s:47: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:47: Warning: rest of line ignored; first ignored character is `3'
> /ecos-c/temp/ccmMeZK9.s:50: Error: bad expression
> /ecos-c/temp/ccmMeZK9.s:50: Warning: rest of line ignored; first ignored character is `3'
> make[1]: *** [/ecos-d/Dev/eCos/builds/current/pc388_install/include/cyg/hal/sh2_offsets.inc] Error 1
> make: *** [build] Error 2
> 

Try looking at the generated *.s file.  My guess is that it has some
spaces which the compiler/assembler doesn't like.  Some prudent changes
to your include files may fix it.

> 
> For the code in var_mk_defs.c:
> HAL_UCACHE_SIZE = 0, HAL_UCACHE_WAYS = 0, HAL_UCACHE_LINE_SIZE = 0, CYGNUM_HAL_ISR_MAX = 62 and so on.
> 
> As for my port, the processor it is for has a much larger vector table. The SH2 7044 variant I based this on has exception vectors for the custom interrupt layout going up to 93 in var_intr.h whereas the SH2 7145 hash exception vectors going up to 129. Could the size of the vector table be causing a problem.
> 
> The 7145 also has no cache so I have used another cache definition file mod_regs_cac_3.h which specifies cache sizes as 0 and all addresses. Could this also be contributing. I am pretty new to eCos and there is some funky stuff which I don't as yet understand. It has been quite hard work performing a variant and platform port for board.
> 
>    Any help greatfully received. Many thanks.
> 
> 		James
-- 
Gary Thomas <gary@mlbassoc.com>
MLB Associates


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

  reply	other threads:[~2003-10-15 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-15 15:02 James Yates
2003-10-15 15:09 ` Gary Thomas [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-16  7:55 James Yates
2003-10-16 12:04 ` Gary Thomas
2003-10-15 15:45 James Yates
2003-10-15 15:50 ` Gary Thomas
2003-10-15 14:34 James Yates
2003-10-15 14:41 ` Gary Thomas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1066230547.32461.54.camel@hermes \
    --to=gary@mlbassoc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=j.yates@quartzuk.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).