Re: [Mspgcc-users] MSP430X core support in binutils

[Sergey A. B. <sb...@us...>]

Sergey A. Borshch wrote:
> Hi everyone.
> 
>   I almost finished patch, that adds full MSP430X support to binutils 2.18. 
patch commited to cvs repository (packaging/patches/binutils-2.18-430X.patch).
430X instructions patch for gdb/insight (packaging/patches/gdb-6.8-430X.patch) 
commited too.

> Now I have some problems I can't resolve myself, without collective discussion.
> 
> Problem #1:
>    ld not supports splitted text output section with "hole" for vectors. So we 
> need to link all contents with addresses above 0x10000 to separate output 
> section and memory region. They needs name. Which names we chose for them 
> (fartext, farflash, extflash, maybe other)? The same question about section name 
> for constants in extended address space. The second approach I see is to place 
> .vectors input section into .text output section and discard memory region 
> "vectors" from ld script. I don't know which solution is better and tested only 
> the first one.
fartext memory region and .fartext sections added to linker scripts of 430X CPUs.

> Problem #2:
>    Extension word for register mode has "Repetition count" field.
.rpt #N pseudo-op added.

> Problem #3:
>    MSP430, MSP430X(241x, 26x, 46xx) and MSP430X2(5xxx) cores have different 
> instruction timings.
timing calculation completely removed from binutils and gdb disassembling 
routines, as it's result wasn't used.

   Sergey