On 21 Aug 2011, at 00:35, John Clymer wrote:

> DIFF attached for comment and review.  Provides the following features / 
> difference:
> 
> 1) Switched operation of cpuinfo.pas - there is still a SET containing the 
> ct_ constants, but that now indexes an array of structures rather than a 
> collection of arrays.  The array contains the info from the old arrays, PLUS 
> FLASH, SRAM and EPROM memory definitions i.e. BASE and SIZE for each.
> NOTE:  Switched for both ARM and AVR.  AVR changes will compile the cross 
> compiler, but choke while building the RTL  (complaining about a function 
> being too complex). However, the SVN and daily build exhibit the same 
> behaviour - so I do not believe I have broken the AVR any further than it was 
> broken.
> 
> 2) Added LM3FURY controller unit file - this will be built up into a base 
> unit file for all the Fury class Stellaris controllers.
> 
> 3) I intend to leave the "Stellaris" controller class with the intention that 
> those that don't want a full set of system defines can use this class and 
> will receive nothing more than the bare minimum to boot a chip into 
> PASCALMAIN.  The Flash and SRAM sizes will be set very large - so caveat 
> emptor to the user if, as they will need to ensure the programs do not 
> require more resources than their chip require.

It actually renders it unusable if the ram size is bigger than that in the 
device you are using as the stack top will be set outside the available ram. It 
has only ever worked before with the correct ram/flash sizes as I pointed out 
to you. It should be for specific known combinations, the ct_stellaris was 
incorrect before you diff'ed it, and now you have introduced another error 
(stack_top=0x20fffc?).

Personally, as somebody using this compiler on real projects, I think there are 
too many changes proposed here in one hit, completely untested.

festina lente

_______________________________________________
fpc-devel maillist  -  [email protected]
http://lists.freepascal.org/mailman/listinfo/fpc-devel

Reply via email to