Re: [fpc-devel] Stellaris Update

2011-08-16 Thread Geoffrey Barton
On 16 Aug 2011, at 04:39, John Clymer wrote: So, after some work, I have a compiler working for the LM3S8962 board (a successful Blinking LED :-) ) However, as I was going through some of the various datasheets, I see that all the Stellaris controllers have similar memory maps. That

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread Florian Klämpfl
Am 16.08.2011 05:39, schrieb John Clymer: So, after some work, I have a compiler working for the LM3S8962 board (a successful Blinking LED :-) ) However, as I was going through some of the various datasheets, I see that all the Stellaris controllers have similar memory maps. That is: A)

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread John Clymer
provides enough power to accommodate most of the compilers potential users. John From: DaWorm daw...@gmail.com To: FPC developers' list fpc-devel@lists.freepascal.org Sent: Tue, August 16, 2011 8:49:51 AM Subject: Re: [fpc-devel] Stellaris Update STM32F103

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread John Clymer
Subject: Re: [fpc-devel] Stellaris Update Am 16.08.2011 05:39, schrieb John Clymer: So, after some work, I have a compiler working for the LM3S8962 board (a successful Blinking LED :-) ) However, as I was going through some of the various datasheets, I see that all the Stellaris controllers

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread John Clymer
To: FPC developers' list fpc-devel@lists.freepascal.org Sent: Tue, August 16, 2011 12:35:03 PM Subject: Re: [fpc-devel] Stellaris Update Am 16.08.2011 05:39, schrieb John Clymer: So, after some work, I have a compiler working for the LM3S8962 board (a successful Blinking LED :-) ) However, as I

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread Geoffrey Barton
, 2011 12:35:03 PM Subject: Re: [fpc-devel] Stellaris Update Am 16.08.2011 05:39, schrieb John Clymer: So, after some work, I have a compiler working for the LM3S8962 board (a successful Blinking LED :-) ) However, as I was going through some of the various datasheets, I see that all

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread Florian Klämpfl
Am 16.08.2011 12:24, schrieb John Clymer: Sorry, missed the second set of questions I was able to get the stellaris part setup in t_embed.pas and cpuinfo.pas, then I got build errors when I build an executable - it was missing the Controller's startup file - these are in

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread Florian Klämpfl
Am 16.08.2011 12:16, schrieb John Clymer: Stellaris ALWAYS has the Code starting at $:. STM32's do something odd where the FLASH starts at $0800:, and the memory between $: and $07FF: is mappable to either the FLASH or the built-in boot loader. (Which throws a kink

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread Florian Klämpfl
Am 16.08.2011 12:16, schrieb John Clymer: Stellaris ALWAYS has the Code starting at $:. STM32's do something odd where the FLASH starts at $0800:, and the memory between $: and $07FF: is mappable to either the FLASH or the built-in boot loader. (Which throws a kink

Re: [fpc-devel] Stellaris Update

2011-08-16 Thread John Clymer
From: Florian Klämpfl flor...@freepascal.org To: FPC developers' list fpc-devel@lists.freepascal.org Sent: Tue, August 16, 2011 2:46:06 PM Subject: Re: [fpc-devel] Stellaris Update Am 16.08.2011 12:24, schrieb John Clymer: Sorry, missed the second set of questions I was able to get

[fpc-devel] Stellaris Update

2011-08-15 Thread John Clymer
So, after some work, I have a compiler working for the LM3S8962 board (a successful Blinking LED :-) ) However, as I was going through some of the various datasheets, I see that all the Stellaris controllers have similar memory maps. That is: A) Each type of device has a specific spot in the

Re: [fpc-devel] Stellaris Update

2011-08-15 Thread DaWorm
STM32F103 and other ST Micro M3 parts have the ability to remap the vector table. You can create applications to start anywhere in memory, and use a bootloader to remap the table and jump to the new power up vector. In IAR C this is handled in the linker config file. Someone on the list thought