This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: tm_basic for edb9301


 Thanks a lot for your advice, Bart. I set some
 numeric constants in the #defines used in tm_basic
while I was waiting for someone to answer me, and the
test cases for the "net" template compiled ok. I also
changed some minor things at if_ep93xx.c, the network
interface driver (it access the flash and was misisng
some ifdefs and some constant values). 

 I didn't ran the code in target, yet. Gonna do it
monday. Hope everything goes ok.
 
 Well, the EDB93xx port (_eval board that uses EP93xx
 SoC) is "Cirrus private", since Cirrus didn't
contributed it to the source base, yet. And it's very
 hard to download it without buying the EDB93xx kits.
 
 I'll try to contact Cirrus and ask them to do it so,
 since everybody has to win with such contribution ;)
 
 Since Cirrus code is derived from GPL work, I can
 sent it to interested  people in having a look, but
eCos maintainers are waiting to put it in source base
until Cirrus agrees to do so. 

 Best regards, Daniel.
 
 (This yahoo webmail sucks.)
 
> Bart Veer <bartv@ecoscentric.com> wrote:>>>>>
> "Daniel"
> == Daniel Gomes writes:
> 
> Daniel> Hi again. :)
> Daniel> In my struggle trying to build the tests for
> the EDB9301,
> Daniel> I got a problem in tb_basic.cxx. arm-elf-gcc
> is
> Daniel> complaining about a nasty define that is
> based
> in a
> Daniel> variable-size type:
> 
> (snip)
> 
>  There is no EDB9301 support in the eCos repository.
> I
> have never seen the port and don't know who is
> responsible, but it looks like they never even built
> the testcases.
> 
>  CYGMEM_REGION_ram_SIZE should be a compile-time
> constant, so it is the
> platform HAL that is broken. If a platform may have
> varying amounts of
> memory then usually the platform HAL should default
> to
> the smallest,
> ensuring that you cannot build an application which
> won't actually run
> on the target. Then if run-time sizing detects extra
> memory this can
> be added to the heap. If you know that the
> application
> will only be
> run on a larger board and its static memory
> requirements exceed the
> minimum, there are a number of ways of addressing
> it.
> 
> For now I suggest you just hardwire
> CYGMEM_REGION_ram_SIZE to match
> your hardware.
> 
> Bart
> 
> 
> 
> 
> 
> =====
> ---
>   Daniel C. Gomes <danielcgomes@yahoo.com.br> 
>   ICQ : 2278714
>   Belo Horizonte - MG - Brasil
> 
> 
> 	
> 	
> 		
>
_______________________________________________________
> 
> Yahoo! Acesso Grátis - Internet rápida e grátis.
> Instale o discador agora!
> http://br.acesso.yahoo.com/
>  

=====
---
  Daniel C. Gomes <danielcgomes@yahoo.com.br> 
  ICQ : 2278714
  Belo Horizonte - MG - Brasil


	
	
		
_______________________________________________________ 
Yahoo! Acesso Grátis - Internet rápida e grátis. Instale o discador agora! http://br.acesso.yahoo.com/

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]