• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 508 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Sys/Bios Porting On MSP430F67641

Nipam Bhavsar
Intellectual 620 points
Other Parts Discussed in Thread: MSP430F67641, MSP430F6736

Hello,

We are developing a product in which we used MSP430F67641 controller. To achieve multiple Tasks Functionality, we are planning to use Sys/Bios in this controller. But after installing Sys/Bios, we found that Sys/Bios does not support this controller. We are using CCS version 6.0.1.

Is there any porting guide available that describes the steps for non-supported devices? 

What are the changes needed to build Sys/Bios for MSP430F67641 controller? 

Can we use example application of other controller that nearly compatible to this controller? If yes, then what other changes are required to compile that application successfully? If no, then please suggest us another options.

Any help in this case is appreciated.

Thanks,

Nipam

  • 0
    TI__Mastermind 21645 points

    Hi Nipam,

    I have filed a bug against SYS/BIOS to add support for MSP430F67641. Here's a link to the bug report:

    https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&entityID=SDOCM00114473&entityDefName=IncidentReport&username=readonly&password=readonly

    The other MSP430F676x devices we support unfortunately have slightly different interrupt vector addresses (Timer A1 and A2 interrupt numbers are different) and therefore you will not be able to build the app for those devices and run it on F67641.

    How urgently do you need SYS/BIOS support on this device ? I believe we have a SYS/BIOS release planned for sometime next month and can try to add support for this device in that release.

    Best,

    Ashish

  • 0 in reply to Ashish Kapania
    Intellectual 620 points
    Hello Ashish,

    Thanks for your kind response.

    We tried to import LED task demo application of MSP430F6736 controller and changed device MSP430F67641 in project properties. We modified LED pin configuration and compiled. It compiled successfully and after loading a program on our Hardware board(MSP430F67641), it executes perfectly on our board. I can see my LED blinking on every 1 second. Can we use this approach to build my application using SYS/BIOS?

    How urgently do you need SYS/BIOS support on this device ?
    Actually we have to freeze our application in this month's end. But if SYS/BIOS next release will be in next month, then we can wait for this release.

    Thanks again.

    Thanks,
    Nipam
  • 0 in reply to Nipam Bhavsar
    TI__Mastermind 21645 points
    Hi Nipam,

    I compared the datasheet for MSP430F67641 with the peripheral settings we have for MSP430F6736 and it looks like the base addresses and interrupt numbers that SYS/BIOS uses are the same. So, I would say it should be ok for you to use MSP430F6736 as the device name.

    The next SYS/BIOS release is planned for somewhere between last week of Jan and first week of Feb. We have committed this bug (to add F67641 support) to that release.

    Best,
    Ashish
  • 0 in reply to Ashish Kapania
    Intellectual 620 points

    Hello Ashish,

    Thanks for your kind response.

    It is really good to hear that we can go to implement our application using MSP430F6736 settings. So after new release of SYS/BIOS, we just need to change MSP430F6736 settings to F67641 settings.


    Thanks for clearing our doubt.

    Thanks,

    Nipam