• Join
  • Sign In with my.TI Login
Texas Instruments
  • Products
  • Applications
  • Tools & Software
  • Support & Community
  • Sample & Buy
  • About TI
Sample & Purchase Cart Sample & Purchase Cart
  • Search
  • Advanced
TI E2E™ Community
  • Support Forums
  • Blogs
  • Groups
  • Videos
  • 简体中文
  • More ...
TI Home » TI E2E Community » Support Forums » Microcontrollers » MSP430™ Microcontrollers » MSP430 Ultra-Low Power 16-bit Microcontroller Forum » USB ROM bsl enumeration
Share
MSP430™ Microcontrollers
  • Forum
  • Announcements
  • E2E Wiki
Options
  • Subscribe via RSS
MSP430 Resources
  • MSP430 Product Folder
  • MSP-EXP430G2 - MSP430 LaunchPad Value Line Development kit
  • MSP430 Getting Started Guide
  • MSP430 Microcontroller Projects
  • More Resources >
  • Forums

    USB ROM bsl enumeration

    This question is answered
    Dan-o
    Posted by Dan-o
    on Sep 20 2012 12:37 PM
    Intellectual795 points

    I cannot get the USB ROM bsl to enumerate.

    msp430f5529, XT2 24Mhz

    I have a combination CDC / HID interface that communicates with a host running linux. the msp430 is always connected to the bus. There is no VBUS.  I have modified the usb api to work without needed VBUS.

    when the msp430 receives a "firmware update" command, it should jump to the ROM BSL. right now all I am trying to do is get into the BSL and show up on the host. here's the code I've been playing with

        // ------------------------------------------------------------------------------        
    case eFIRMWAREUPDATE:
        // disconnect and disable usb
        __delay_cycles(USB_MCLK_FREQ);           // wait a sec
        __disable_interrupt();

        ADC12CTL0 = 0;
        ADC12CTL1 = 0;
       
        TA0CTL = TACLR;
        TA1CTL = TACLR;
        TA2CTL = TACLR;
        TB0CTL = TBCLR;

        UCA0CTL1 = UCSWRST;
        UCA0CTL0 = 0;                        
        UCA1CTL1 = UCSWRST;
        UCA1CTL0 = 0;            
        UCB0CTL1 = UCSWRST;
        UCB0CTL0 = 0;

        // init FLL per ERRATA USB8
        // use REFO for FLL and ACLK
    //                        UCSCTL3 = (UCSCTL3 & ~(SELREF_7)) | (SELREF__REFOCLK);
    //                        UCSCTL4 = (UCSCTL4 & ~(SELA_7)) | (SELA__REFOCLK);                 
    //                        Init_FLL_Settle(USB_MCLK_FREQ / 1000, USB_MCLK_FREQ / 32768, 0);   //Start the FLL, dont use it to drive MCLK & SMCLK yet                        
    //                        UCSCTL4 = (UCSCTL4 & ~(SELS_7)) | (SELS__DCOCLK);
    //                            UCSCTL4 = (UCSCTL4 & ~(SELM_7)) | (SELM__DCOCLK);
    //                            UCSCTL4 = (UCSCTL4 & ~(SELM_7)) | (SELM__XT2CLK);                        
        __delay_cycles(USB_MCLK_FREQ);           // wait a sec
        
        USB_disconnect();
        USB_disable();

        __delay_cycles(USB_MCLK_FREQ);           // wait a sec
        __delay_cycles(USB_MCLK_FREQ);           // wait a sec
        // jump to ROM BSL
        ((void (*)())0x1000)();
        break;
        // ------------------------------------------------------------------------------    

    I do not use the DCO for anything in my system and had to follow the UBS8 errata workaround to allow the usb pll to initialize. After that, I disable the FLL and dont use the DCO. I have all the FLL code here because I thought I might need to redo the workaround before jumping to the BSL. During init that code works fine but when I put it here I always get DCOFFG faults. anyways here's some questions

    1) does the ROM BSL care about VBUS if you enter it by jumping to 0x1000?

    2) does the USB8 errata apply to the ROM bsl?

    3) should I call BOTH USB_disconnect() and USB_disable() before the jump?

    msp430f5529 usb bsl
    Report Abuse
    • Reply
    You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    All Replies
    • old_cow_yellow
      Posted by old_cow_yellow
      on Sep 20 2012 15:53 PM
      Guru25715 points

      I do not know much about F5529. But my impression is that there is no ROM BSL. There may be a factory loaded BSL code in the so-called BSL-Flash. Are you sure the chip you are using has working BSL code in its BSL-Flash?

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    • Dan-o
      Posted by Dan-o
      on Sep 20 2012 15:59 PM
      Verified Answer
      Verified by Dan-o
      Intellectual795 points

      ROM / FLASH whats in a name? I throw them around casually lol.

      I figured out the problem - VBUS. The TI usb BSL requires VBUS to be there even if you use the jump to 0x1000 method. I'm kicking myself for not including VBUS :(

      Report Abuse
      • Reply
      You have posted to a forum that requires a moderator to approve posts before they are publicly available.
    TI E2E™ Community
    • Support Forums
    • Blogs
    • Videos
    • Groups
    • Site Support & Feedback
    • Settings
    TI E2E™ Community Groups
    • TI University Program
    • Make the Switch
    • Microcontroller Projects
    • Motor Drive & Control
    Other Communities
    • Deyisupport
    • Designsomething.org
    • beagleboard.org
    • TI on Element 14
    • TI on TechXchangeSM
    Other Technical & Support Resources
    • WEBENCH® Design Center
    • Product Information Centers
    • Technical Documents
    • TI Design Network
    • TI Technical Articles
    • TI Training

    All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.

    Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI, its suppliers and providers of content reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.

    Follow Us Texas Instruments on Facebook Texas Instruments on Twitter Texas Instruments on LinkedIn Texas Instruments on Google+
    TI Worldwide | Contact Us | my.TI Login | Site Map | Corporate Citizenship | mobile m.ti.com (Mobile Version)

    TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs and
    embedded processors, along with software, tools and the industry’s largest sales/support staff.

    © Copyright 1995-2013 Texas Instruments Incorporated. All rights reserved.
    Trademarks | Privacy Policy | Terms of Use