• State
  • Replies 3 replies
  • Subscribers 31 subscribers
  • Views 94 views
  • Users 0 members are here
Support feedback
Options
Options
Related

MSPM0L2228: Questions about the example software "secondary_bsl_uart"

SUSUMU ONIZAWA
Prodigy 70 points

Part Number: MSPM0L2228

Hi, 

I confused a little bit about BSL and BCR for MSPM0.
Could you tell me about the following 3 questions?

 

***Q1:According the "NOTE" below described in the "readme" of  the example software "secondary_bsl_uart", the primary bootloader seems not to be able to be used in any conditions if that example was loaded to the device.
But I think "Init" that is part of the primary bootloader would be called before the secondary bootloader would be called in any cases.

 

Is it correct?

Because "User's Guide" - SLAU887 - says so in section "3.1 Design".

 

NOTE:

Hence once this image is loaded to the device, the primary Bootloader in the device can't be used. Only the secondary Bootloader will be active.

 

 

***Q2: Same as above Q1, we need to lock the flash region in which the custom Bootloader resides.
But, during our software development, we need to modify and update the custom bootloader.

So I guess that we should lock the flash region for the custom Bootloader after official software release, and a device never get locked if we uploaded it in ideal conditions - no noise, no power source disturbance and so on.

 

Is it correct?

Or are there any risks to be locked even if we use it in proper conditions?

 

 

NOTE:
While creating Custom Bootloader make sure that, 
Flash region in which the custom Bootloader resides is Static write protected in the BCR configuration. 
Otherwise there are chances for device to get locked during the Bootloading process.

 

 

***Q3: If I configured a device to "Disable BSL invoke pin Check", I think that BSL never be called but SWD_Factory_Reset command would be available.

 

Is it correct?

 

Best Regards, 

Susumu

  • 0
    TI__Genius 12200 points

    Hello Susumu,

    I will reply to your questions in details next Monday.

    BR,

    Janz Bai

  • 0 in reply to Janz Bai
    Prodigy 70 points

    Hi Janz, 

    Do you have any update?

    Best Regards, 

    Susumu

  • 0 in reply to SUSUMU ONIZAWA
    TI__Genius 12200 points

    Hello Susumu,

    Sorry for my late response. 

    About Q1:

    In "init", MCU will check the BSL configuration. Then it will check that you enable secondary BSL and set the secondary BSL address. Then it will jump to secondary BSL. Just secondary BSL is active.

    About Q2:

    This means we recommend you to do static write protection to the secondary BSL region. The reason is that if you don't do static write protection to the secondary BSL region and you send mass erase command incorrectly in BSL process, the secondary BSL region will also be erased, which will make BSL process error and maybe device locked. So if you protect the secondary BSL region after official SW release and uploaded in ideal conditions, in theory, the device won't be locked.

    About Q3:

    Yes, if you modify the configuration of the secondary BSL demo to "disable invoke pin check", BSL won't be invoked. But you also can use "SWD_Factory_Reset" because this "Factory reset" is through SWD interface.

    Because I will go home for China New Year Holiday today, so if you have any more questions, you can re-cerate a new E2E post to do discussion, Our American colleague will help you in 24hours,

    Best Regards,

    Janz Bai