[ECOS] Re: [ Spam Mail ] [ECOS] Re: [ Spam Mail ] Re: [ECOS] How can I initial the flashs of sst29vfxxx and intel_strata at do_flash_init() ? (This message is to be blocked by code: bkfkact590) (This message is to be blocked by code: bkfkact590)

[Andrew Lunn <andrew at lunn dot ch>]

On Tue, Aug 30, 2005 at 05:00:22PM +0800, Steven_cheng wrote:
> Hi Andrew,
> 
>     Thanks for your reply.  I find that the CYGPKG_DEVS_FLASH_SST_POWERPC_PX
> does not seems  to be compiled and linked. Because I modify the
> powerpc_px_flash_sst.c
> for CYGPKG_DEVS_FLASH_SST_POWERPC_PX, this file will not be re-compiled.
> 
> Q1 : Why does the source of SST not be compiled ??
> 
> And I check the makefile at pX_build\devs\flash\sst\39vfxxx\current.
> It is as following:
> /////////////////////////////////
> pX_build\devs\flash\sst\39vfxxx\current\makefile
> ///////////////////////////////////////////////
> export REPOSITORY := /opt/ecoscvs/ecos/packages
> export PREFIX := /home/steven/Project/pX_install
> export COMMAND_PREFIX := powerpc-eabi-
> export CC := $(COMMAND_PREFIX)gcc
> export OBJCOPY := $(COMMAND_PREFIX)objcopy
> export HOST := UNIX
> export AR := $(COMMAND_PREFIX)ar
> 
> PACKAGE := devs/flash/sst/39vfxxx/current
> OBJECT_PREFIX := devs_flash_sst_39vfxxx
> CFLAGS
> := -msoft-float -mcpu=603e -Wall -Wpointer-arith -Wstrict-prototypes -Winlin
> e -Wundef -Woverloaded-virtual -g -gdwarf-2 -ffunction-sections -fdata-secti
> ons -fno-rtti -fno-exceptions -fvtable-gc -finit-priority
> LDFLAGS
> := -msoft-float -mcpu=603e -g -nostdlib -Wl,--gc-sections -Wl,-static
> VPATH := $(REPOSITORY)/$(PACKAGE)
> INCLUDE_PATH := $(INCLUDE_PATH) -I$(PREFIX)/include $(foreach
> dir,$(VPATH),-I$(dir) -I$(dir)/src -I$(dir)/tests) -I.
> MLT := $(wildcard $(REPOSITORY)/$(PACKAGE)/include/pkgconf/mlt*.ldi
> $(REPOSITORY)/$(PACKAGE)/include/pkgconf/mlt*.h)
> TESTS :=
> 
> build: headers
> 
> headers: mlt_headers $(PREFIX)/include/cyg/io/flash_sst_39vfxxx.inl
> 
> $(PREFIX)/include/cyg/io/flash_sst_39vfxxx.inl:
> $(REPOSITORY)/$(PACKAGE)/include/flash_sst_39vfxxx.inl
>  @mkdir -p $(dir $@)
>  @cp $< $@
>  @chmod u+w $@
> 
> include $(REPOSITORY)/pkgconf/rules.mak
> ////////////////////////////////////////////////////////////////////////////
> ////////////////////////////////////////////////////////////////////////////
> ///////

This looks correct. The is nothing in devs/flash/sst/39vfxxx/current
to actually compile. There is only an header file which is inlined. 

> /////////////////////////////////
> devs\flash\powerpc\px\current\cdl\flash_sst_powerpc_px.cdl
> //////////////////////////////////////
> 
> cdl_package CYGPKG_DEVS_FLASH_SST_POWERPC_PX {
>     display       "pX SST39VF040 FLASH memory support"
>     description   "FLASH memory device support for PowerPC 8245 (Alpha pX)"
> 
>     parent        CYGPKG_IO_FLASH
>     active_if   CYGPKG_IO_FLASH
>     requires   CYGPKG_HAL_POWERPC_PX
> 
>     compile       -library=libextras.a powerpc_px_flash_sst.c
> 
>     # Arguably this should do in the generic package
>     # but then there is a logic loop so you can never enable it.
>     cdl_interface CYGINT_DEVS_FLASH_SST_39VFXXX_REQUIRED {
>         display   "Generic SST 39VFxxx driver required"
>     }
> 
>     implements CYGINT_DEVS_FLASH_SST_39VFXXX_REQUIRED
> 
>     cdl_option CYGNUM_DEVS_FLASH_POWERPC_PX_SIZE {
>         display       "Flash size in Kbytes"
>         flavor        data
>         legal_values  { 512 1024 2048 }
>         default_value 512
>         description   "
>             This option specifies the size of the flash device
>             of the pX."
>     }
> }

This looks OK.

> Q2 : Does the order of the packages affect  the compiling result ??
>         The compiling order of the packages are up to down, or down to up ??

It should not make a difference. 

Could i see your  powerpc_px_flash_sst.c

        Andrew

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