look for chip datasheets and family user manuals for the specific reference
you´re using
bye
________________________________
From: vineyard
To: m...
Sent: Sunday, July 1, 2012 4:08 PM
Subject: [msp430] Looking for the #define rosetta stone
This question has probably been answered a thousand times but it's worthy
of 1001. You see these wonderful names like TACCR0 and P1DIR or WDTPW or WDTCTL
or WDTHOLD or BCSCTL1. I could go down through all the header files, find all
the #define statements and try to sort them out using the often absent comment
statements, but that doesn't make much sense. Obviously I missed something
But I don't see them in the TI literature like slau131, slau157, etc.
I'm sure most of them must be explained somewhere and conveniently
annotated, not just strewn without comment though the programming examples like
fiberglas laundry lint.
But none of the programming guides I have seen so far even have the word pin or
output, seemingly the sort of information one might desire in programming
language guide for a dedicated systems microprocessor.
Can anyone help me, please? Help! PS-For the always unhelpful few, the answer,
"there are too many of them" is a really ludicrous answer considering 99% of the
programs are written with less than 200. Sincerely, Doc K. And thanks ahead of
time.
Looking for the #define rosetta stone
Started by ●July 1, 2012
Reply by ●July 2, 20122012-07-02
Reply by ●July 9, 20122012-07-09
For a newcomer to this field, these links are very helpful!
I'm working on a board where the F2618 processor has been upgraded to F5528 processor. The i2c bus is in use, PWM signals being generated, and an SPI peripheral has been added, which I'll need to implement.
Is it wishful thinking to hope that all I'll need to do to accommodate tho processor upgrade is to change the header files? If so, are there particular items that are obviously going to need to be addressed?
Thank you.
--- In m..., "aa1ww" wrote:
>
> I probably should have posted the TI URL for the MSP430x2xx User's Guide. It's at:
> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
>
> Coop, AA1WW
>
I'm working on a board where the F2618 processor has been upgraded to F5528 processor. The i2c bus is in use, PWM signals being generated, and an SPI peripheral has been added, which I'll need to implement.
Is it wishful thinking to hope that all I'll need to do to accommodate tho processor upgrade is to change the header files? If so, are there particular items that are obviously going to need to be addressed?
Thank you.
--- In m..., "aa1ww" wrote:
>
> I probably should have posted the TI URL for the MSP430x2xx User's Guide. It's at:
> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
>
> Coop, AA1WW
>
Reply by ●July 9, 20122012-07-09
>are there particular items that are obviously going to
need to be addressed?<
Since you didn't specifically mention it, I'll ask the question: Have you compared the pinouts of the two chips?
--- In m..., "quickieaircraft" wrote:
>
> For a newcomer to this field, these links are very helpful!
>
> I'm working on a board where the F2618 processor has been upgraded to F5528 processor. The i2c bus is in use, PWM signals being generated, and an SPI peripheral has been added, which I'll need to implement.
>
> Is it wishful thinking to hope that all I'll need to do to accommodate tho processor upgrade is to change the header files? If so, are there particular items that are obviously going to need to be addressed?
>
> Thank you.
>
> --- In m..., "aa1ww" wrote:
> >
> > I probably should have posted the TI URL for the MSP430x2xx User's Guide. It's at:
> > http://www.ti.com/lit/ug/slau144i/slau144i.pdf
> >
> > Coop, AA1WW
>
Since you didn't specifically mention it, I'll ask the question: Have you compared the pinouts of the two chips?
--- In m..., "quickieaircraft" wrote:
>
> For a newcomer to this field, these links are very helpful!
>
> I'm working on a board where the F2618 processor has been upgraded to F5528 processor. The i2c bus is in use, PWM signals being generated, and an SPI peripheral has been added, which I'll need to implement.
>
> Is it wishful thinking to hope that all I'll need to do to accommodate tho processor upgrade is to change the header files? If so, are there particular items that are obviously going to need to be addressed?
>
> Thank you.
>
> --- In m..., "aa1ww" wrote:
> >
> > I probably should have posted the TI URL for the MSP430x2xx User's Guide. It's at:
> > http://www.ti.com/lit/ug/slau144i/slau144i.pdf
> >
> > Coop, AA1WW
>
Reply by ●July 9, 20122012-07-09
Well, for a start they use different clock systems, the 2618 uses the
basic clock system+, while the 5528 uses the unified clock system, but,
even more basically they have different CPU cores. The 5528 has word
wide port options, and a totally incompatible pin out, so, even if you
strip back your usage to the minimum, and the UARTs have identical
structure in terms of register and bit allocations you will still need
to be wary of shifting pins for initialising the peripherals, as well as
shifting ports, for example on the 2618 USCIA1 is split cross ports 3 &
5, whereas it resides entirely in port 4 on the 5528..
I don't know what level you program in, I assume C, but I know Ti have a
port configuration utility called GRACE (i think) i've never used it,
but that might help remove some of the drudgery.
Cheers
Al
On 10/07/2012 1:00 AM, quickieaircraft wrote:
>
> For a newcomer to this field, these links are very helpful!
>
> I'm working on a board where the F2618 processor has been upgraded to F5528 processor. The i2c bus is in use, PWM signals being generated, and an SPI peripheral has been added, which I'll need to implement.
>
> Is it wishful thinking to hope that all I'll need to do to accommodate tho processor upgrade is to change the header files? If so, are there particular items that are obviously going to need to be addressed?
>
> Thank you.
>
> --- In m..., "aa1ww" wrote:
>> I probably should have posted the TI URL for the MSP430x2xx User's Guide. It's at:
>> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
>>
>> Coop, AA1WW
>>
basic clock system+, while the 5528 uses the unified clock system, but,
even more basically they have different CPU cores. The 5528 has word
wide port options, and a totally incompatible pin out, so, even if you
strip back your usage to the minimum, and the UARTs have identical
structure in terms of register and bit allocations you will still need
to be wary of shifting pins for initialising the peripherals, as well as
shifting ports, for example on the 2618 USCIA1 is split cross ports 3 &
5, whereas it resides entirely in port 4 on the 5528..
I don't know what level you program in, I assume C, but I know Ti have a
port configuration utility called GRACE (i think) i've never used it,
but that might help remove some of the drudgery.
Cheers
Al
On 10/07/2012 1:00 AM, quickieaircraft wrote:
>
> For a newcomer to this field, these links are very helpful!
>
> I'm working on a board where the F2618 processor has been upgraded to F5528 processor. The i2c bus is in use, PWM signals being generated, and an SPI peripheral has been added, which I'll need to implement.
>
> Is it wishful thinking to hope that all I'll need to do to accommodate tho processor upgrade is to change the header files? If so, are there particular items that are obviously going to need to be addressed?
>
> Thank you.
>
> --- In m..., "aa1ww" wrote:
>> I probably should have posted the TI URL for the MSP430x2xx User's Guide. It's at:
>> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
>>
>> Coop, AA1WW
>>
Reply by ●July 9, 20122012-07-09
Hi All,
Last time I looked at Grace it could only be used with the 2x line, aka it
was made to work with the launch pad/ value line. I have personally
switched from the 2618 to the 5438a and if memory serves me correctly it
was not hard but, as Al mentioned, the clock is different and requires
different init functions. I believe the UART, SPI, etc are very similar but
even if they are not and if you program them correctly it should be easy to
change between. The only other worry I have is the ports will not line up
because that is a pretty big jump and I doubt the pins will be that nice,
but yet again you may just be that lucky.
Jake G.
On Mon, Jul 9, 2012 at 10:02 AM, Onestone wrote:
> **
> Well, for a start they use different clock systems, the 2618 uses the
> basic clock system+, while the 5528 uses the unified clock system, but,
> even more basically they have different CPU cores. The 5528 has word
> wide port options, and a totally incompatible pin out, so, even if you
> strip back your usage to the minimum, and the UARTs have identical
> structure in terms of register and bit allocations you will still need
> to be wary of shifting pins for initialising the peripherals, as well as
> shifting ports, for example on the 2618 USCIA1 is split cross ports 3 &
> 5, whereas it resides entirely in port 4 on the 5528..
>
> I don't know what level you program in, I assume C, but I know Ti have a
> port configuration utility called GRACE (i think) i've never used it,
> but that might help remove some of the drudgery.
>
> Cheers
>
> Al
> On 10/07/2012 1:00 AM, quickieaircraft wrote:
> >
> > For a newcomer to this field, these links are very helpful!
> >
> > I'm working on a board where the F2618 processor has been upgraded to
> F5528 processor. The i2c bus is in use, PWM signals being generated, and an
> SPI peripheral has been added, which I'll need to implement.
> >
> > Is it wishful thinking to hope that all I'll need to do to accommodate
> tho processor upgrade is to change the header files? If so, are there
> particular items that are obviously going to need to be addressed?
> >
> > Thank you.
> >
> > --- In m..., "aa1ww" wrote:
> >> I probably should have posted the TI URL for the MSP430x2xx User's
> Guide. It's at:
> >> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
> >>
> >> Coop, AA1WW
> >>
> >
> >
> >
> >
>
> >
> >
> >
> >
Last time I looked at Grace it could only be used with the 2x line, aka it
was made to work with the launch pad/ value line. I have personally
switched from the 2618 to the 5438a and if memory serves me correctly it
was not hard but, as Al mentioned, the clock is different and requires
different init functions. I believe the UART, SPI, etc are very similar but
even if they are not and if you program them correctly it should be easy to
change between. The only other worry I have is the ports will not line up
because that is a pretty big jump and I doubt the pins will be that nice,
but yet again you may just be that lucky.
Jake G.
On Mon, Jul 9, 2012 at 10:02 AM, Onestone wrote:
> **
> Well, for a start they use different clock systems, the 2618 uses the
> basic clock system+, while the 5528 uses the unified clock system, but,
> even more basically they have different CPU cores. The 5528 has word
> wide port options, and a totally incompatible pin out, so, even if you
> strip back your usage to the minimum, and the UARTs have identical
> structure in terms of register and bit allocations you will still need
> to be wary of shifting pins for initialising the peripherals, as well as
> shifting ports, for example on the 2618 USCIA1 is split cross ports 3 &
> 5, whereas it resides entirely in port 4 on the 5528..
>
> I don't know what level you program in, I assume C, but I know Ti have a
> port configuration utility called GRACE (i think) i've never used it,
> but that might help remove some of the drudgery.
>
> Cheers
>
> Al
> On 10/07/2012 1:00 AM, quickieaircraft wrote:
> >
> > For a newcomer to this field, these links are very helpful!
> >
> > I'm working on a board where the F2618 processor has been upgraded to
> F5528 processor. The i2c bus is in use, PWM signals being generated, and an
> SPI peripheral has been added, which I'll need to implement.
> >
> > Is it wishful thinking to hope that all I'll need to do to accommodate
> tho processor upgrade is to change the header files? If so, are there
> particular items that are obviously going to need to be addressed?
> >
> > Thank you.
> >
> > --- In m..., "aa1ww" wrote:
> >> I probably should have posted the TI URL for the MSP430x2xx User's
> Guide. It's at:
> >> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
> >>
> >> Coop, AA1WW
> >>
> >
> >
> >
> >
>
> >
> >
> >
> >
Reply by ●December 4, 20122012-12-04
Thank you, gentleman--I just wanted to follow up.
I can confirm that these are indeed exactly the issues I ran into. UCS and BCS are different. Code is obviously not portable because all the predefined constants are different. I found some UCS configuration code on a blog, which seems to have given me enough of a start.
And I have confirmed, Grace supports the 2xxx revision family. I haven't gotten SPI working yet--I'm working on that this week. I also wanted to add that the Timer configuration seems to be different between the families.
Thanks again!
--- In m..., Thomas Grajewski wrote:
>
> Hi All,
> Last time I looked at Grace it could only be used with the 2x line, aka it
> was made to work with the launch pad/ value line. I have personally
> switched from the 2618 to the 5438a and if memory serves me correctly it
> was not hard but, as Al mentioned, the clock is different and requires
> different init functions. I believe the UART, SPI, etc are very similar but
> even if they are not and if you program them correctly it should be easy to
> change between. The only other worry I have is the ports will not line up
> because that is a pretty big jump and I doubt the pins will be that nice,
> but yet again you may just be that lucky.
>
> Jake G.
>
> On Mon, Jul 9, 2012 at 10:02 AM, Onestone wrote:
>
> > **
> >
> >
> > Well, for a start they use different clock systems, the 2618 uses the
> > basic clock system+, while the 5528 uses the unified clock system, but,
> > even more basically they have different CPU cores. The 5528 has word
> > wide port options, and a totally incompatible pin out, so, even if you
> > strip back your usage to the minimum, and the UARTs have identical
> > structure in terms of register and bit allocations you will still need
> > to be wary of shifting pins for initialising the peripherals, as well as
> > shifting ports, for example on the 2618 USCIA1 is split cross ports 3 &
> > 5, whereas it resides entirely in port 4 on the 5528..
> >
> > I don't know what level you program in, I assume C, but I know Ti have a
> > port configuration utility called GRACE (i think) i've never used it,
> > but that might help remove some of the drudgery.
> >
> > Cheers
> >
> > Al
> >
> >
> > On 10/07/2012 1:00 AM, quickieaircraft wrote:
> > >
> > > For a newcomer to this field, these links are very helpful!
> > >
> > > I'm working on a board where the F2618 processor has been upgraded to
> > F5528 processor. The i2c bus is in use, PWM signals being generated, and an
> > SPI peripheral has been added, which I'll need to implement.
> > >
> > > Is it wishful thinking to hope that all I'll need to do to accommodate
> > tho processor upgrade is to change the header files? If so, are there
> > particular items that are obviously going to need to be addressed?
> > >
> > > Thank you.
> > >
> > > --- In m..., "aa1ww" wrote:
> > >> I probably should have posted the TI URL for the MSP430x2xx User's
> > Guide. It's at:
> > >> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
> > >>
> > >> Coop, AA1WW
> > >>
> > >
> > >
> > >
> > >
> >
> > >
> > >
> > >
> > >
I can confirm that these are indeed exactly the issues I ran into. UCS and BCS are different. Code is obviously not portable because all the predefined constants are different. I found some UCS configuration code on a blog, which seems to have given me enough of a start.
And I have confirmed, Grace supports the 2xxx revision family. I haven't gotten SPI working yet--I'm working on that this week. I also wanted to add that the Timer configuration seems to be different between the families.
Thanks again!
--- In m..., Thomas Grajewski wrote:
>
> Hi All,
> Last time I looked at Grace it could only be used with the 2x line, aka it
> was made to work with the launch pad/ value line. I have personally
> switched from the 2618 to the 5438a and if memory serves me correctly it
> was not hard but, as Al mentioned, the clock is different and requires
> different init functions. I believe the UART, SPI, etc are very similar but
> even if they are not and if you program them correctly it should be easy to
> change between. The only other worry I have is the ports will not line up
> because that is a pretty big jump and I doubt the pins will be that nice,
> but yet again you may just be that lucky.
>
> Jake G.
>
> On Mon, Jul 9, 2012 at 10:02 AM, Onestone wrote:
>
> > **
> >
> >
> > Well, for a start they use different clock systems, the 2618 uses the
> > basic clock system+, while the 5528 uses the unified clock system, but,
> > even more basically they have different CPU cores. The 5528 has word
> > wide port options, and a totally incompatible pin out, so, even if you
> > strip back your usage to the minimum, and the UARTs have identical
> > structure in terms of register and bit allocations you will still need
> > to be wary of shifting pins for initialising the peripherals, as well as
> > shifting ports, for example on the 2618 USCIA1 is split cross ports 3 &
> > 5, whereas it resides entirely in port 4 on the 5528..
> >
> > I don't know what level you program in, I assume C, but I know Ti have a
> > port configuration utility called GRACE (i think) i've never used it,
> > but that might help remove some of the drudgery.
> >
> > Cheers
> >
> > Al
> >
> >
> > On 10/07/2012 1:00 AM, quickieaircraft wrote:
> > >
> > > For a newcomer to this field, these links are very helpful!
> > >
> > > I'm working on a board where the F2618 processor has been upgraded to
> > F5528 processor. The i2c bus is in use, PWM signals being generated, and an
> > SPI peripheral has been added, which I'll need to implement.
> > >
> > > Is it wishful thinking to hope that all I'll need to do to accommodate
> > tho processor upgrade is to change the header files? If so, are there
> > particular items that are obviously going to need to be addressed?
> > >
> > > Thank you.
> > >
> > > --- In m..., "aa1ww" wrote:
> > >> I probably should have posted the TI URL for the MSP430x2xx User's
> > Guide. It's at:
> > >> http://www.ti.com/lit/ug/slau144i/slau144i.pdf
> > >>
> > >> Coop, AA1WW
> > >>
> > >
> > >
> > >
> > >
> >
> > >
> > >
> > >
> > >
