On Mon, 8 Dec 2014 16:55:04 + (UTC)
Grant Edwards wrote:
> On 2014-12-08, Eric Price wrote:
>
> > to me the change to the TI linker scripts simply makes no sense
>
> None at all. It seems to be assuming that an MSP430 is running some
> sort of OS with some sort of external non-volatile st
On 2014-12-08, Eric Price wrote:
> to me the change to the TI linker scripts simply makes no sense
None at all. It seems to be assuming that an MSP430 is running some
sort of OS with some sort of external non-volatile storage from which
it loads/runs programs.
--
Grant Edwards g
On 2014-12-08, Peter Bigot wrote:
> Unfortunately this list doesn't support attachments. Perhaps somebody
> could put it on E2E and add a pointer.
>
> Interesting that TI proposed a solution that doesn't work for ROM
> resident applications, which are all but the most infinitesimal
> subset of th
On 2014-12-08, Nicholas Clifton wrote:
> Hi Peter,
>
>> Nick: Are you saying that the linker scripts are changing so that a global
>> variable definition like this:
>>
>> int myvar = 43;
>>
>> will result in myvar being stored in RAM, and no initialization of it so
>> the value of myvar when main
On Mon, 08 Dec 2014 14:33:15 +
Nicholas Clifton wrote:
> ...
> Previously there was an implicit
> assumption that the executable would be stored in the ROM of the
> system and that at program startup there would have to be an explicit
> copying of data from the ROM image into RAM. With the c
On Mon, Dec 8, 2014 at 9:01 AM, Paul Sokolovsky wrote:
> Hello,
>
> On Mon, 8 Dec 2014 08:42:28 -0600
> Peter Bigot wrote:
>
> > Unfortunately this list doesn't support attachments. Perhaps somebody
> > could put it on E2E and add a pointer.
>
> Or maybe RedHat even has version control system,
Hello,
On Mon, 8 Dec 2014 08:42:28 -0600
Peter Bigot wrote:
> Unfortunately this list doesn't support attachments. Perhaps somebody
> could put it on E2E and add a pointer.
Or maybe RedHat even has version control system, maybe even with web
interface?
>
> Interesting that TI proposed a sol
Unfortunately this list doesn't support attachments. Perhaps somebody
could put it on E2E and add a pointer.
Interesting that TI proposed a solution that doesn't work for ROM resident
applications, which are all but the most infinitesimal subset of the
applications that use an MSP430. (It's so i
Hi Guys,
I have attached a patch which will restore the old "movedata"
functionality to the toolchain.
Strange - the attachment disappeared. Here it is again.
Cheers
Nick
--
Download BIRT iHub F-Type - The Free
Hi Peter,
> Nick: Are you saying that the linker scripts are changing so that a global
> variable definition like this:
>
> int myvar = 43;
>
> will result in myvar being stored in RAM, and no initialization of it so
> the value of myvar when main starts is not 43?
No. I am saying that myvar wil
Hi Guys,
I have attached a patch which will restore the old "movedata"
functionality to the toolchain. It updates the assembler and the crt0
code so you will need to recompile and relink any binaries that were
causing you problems.
Note - this patch does not move the .data section back
Hi,
I found a workaround for the .data initialization problem
that does not require a custom patch to the compiler.
1. Change the linker scripts back like they were in the old compiler -
to place .data initialization in ROM, and runtime data in RAM
example:
>
--- msp430f5437a.ld.ram 2014-12-0
Nick: Are you saying that the linker scripts are changing so that a global
variable definition like this:
int myvar = 43;
will result in myvar being stored in RAM, and no initialization of it so
the value of myvar when main starts is not 43?
What you wrote seems to imply this, and it matches wha
Hi Olivier,
> When porting some programs to the latest MSPGCC version from RedHat/TI, I
> noticed that ALL initialized global variables in my C code are not
> initialized by the crt0 code.
Are you using your own linker script or a linker script from an older
release ?
The problem is that MSP430
This is a place to report these; other places would be the TI forums; see
http://e2e.ti.com/support/development_tools/compiler/f/343/t/384148
It'd help if you provide a standalone program with the sort of
initialization expressions that aren't working for you, along with the
exact command line you
Hi all,
I just want to start a new thread regarding another issue I mentioned in an
earlier mail.
When porting some programs to the latest MSPGCC version from RedHat/TI, I
noticed that ALL initialized global variables in my C code are not
initialized by the crt0 code.
After looking around in the
16 matches
Mail list logo
