> > It
> > does not support any of msp430x extensions (opcodes and addressing),
> > because it's not subject to patch, it's just a slitely different
> > architecture. hovether, the person named Oscar here in this maillist,
is
> > working on msp430x support for whole toolchain.
> Oh glad to know. I'd like to hear about Oscar progress.
Hi there,
I've finished up my work, except for two problems:
- the linker scripts are the default ones, for the 64K memory. It
will probably have a .text2 section, or something. This can be done
manually by anyone, so it wasn't that important.
- loading code above the 64K level (I heard msp430-jtag worked,
but couldn't have it running... still working on it).
I've sent the patches to Steve Underwood, and I'm waiting for him to reply
and see what the next steps are.
If anyone would like to have those patches, just drop me an email in
private (using the address aoszkar_at_gmail.com), and I'll send them to
you.
Regards,
Oszkar
P.S. Again, about what I've done:
- calla (immediate, register and indexed addressing mode), reta and bra
(immediate adressing mode)
- it is a separate project, since normal msp430 cannot be used, since the
compiler generates calla, reta and bra instructions.
