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.

MSPM0L1106: Disabling BSL Error

Part Number: MSPM0L1106
Other Parts Discussed in Thread: SYSCONFIG

Hello,

We need to disable BSL while still configuring the I2C SCL Pin as PA1/NRST.

When we disable BSL in the syscfg file, the compiler throws flowing error:

How can the BSL be properly deactivated?

Thank you and best regards,
Ambroise

  • Hi Ambroise,

    BSL is enabled/disabled using Sysconfig.

  • Hi Dennis,

    Yes, that is what we have been doing.

    Whenever we disable the BSL in the syscfg, we cannot configure I2C SCL Pin as PA1/NRST and the compiler throws the error shown before. Is there a proper way to disable BSL while setting I2CC as PA1/NRST

    BBest regards,

    AAmbroise

  • I see you are using I2C?  By chance, do you have it's pinmux configuration setup to use PA1 as the SCL?

    Other things to try in the BSL pin configuration is select the ALT pins (PA11).  (this might be an issue is using PA11 for other purpose, but let's see what is causing the conflict).

  • Hi Dennis,

    Yes, we are using the PA1 for SCL. P11 is used as GPIO. We are hoping to not change the pin assignments to prevent a layout change.

    P8, P9, P10 are available though.

    Best regards,

    Ambroise

  • HI Ambroise,

    Have the customer delete the I2C configuration in sysconfig.  Then go into NONMAIN and deselect the BSL.  Last, create a new I2C configuration in sysconfig.  I think this happend to another customer a while ago and there was something with the order in which the configurations are created in sysconfig.

    Let me know if this works.

  • Hello Dennis,

    We tried your recommended steps, unfortunately the same error occurred. The moment the "Enable BSL" is disabled, the I2C SCL Pin under "BSL I2C Pin Configuration" gets reset and throws an error.

    Any thoughts on this?

    Thank you and best regards,
    Ambroise

  • Hi Ambroise,

    See if you can get the customers *.syscfg file and let me take a look at it.

  • Hi Ambroise,

    Have the customer update their SDK and Sysconfig to the latest -> SDK 1.20.0.25, Sysconfig 1.18.0.

    I tested this and it works for me.

  • Hello,

    Yes the customer updated to SDK 1.2.0.05 and Syscfg 1.18.0.
    I tested it and I also got some errors:

    subdir_rules.mk:23: recipe for target 'syscfg/ti_msp_dl_config.o' failed
    syscfg/ti_msp_dl_config.c:92:9: error: use of undeclared identifier 'IOMUX_PINCMNone'
            IOMUX_PINCMNone, IOMUX_PINCMNone, IOMUX_PINCMNone, IOMUX_PINCM5,
            ^
    syscfg/ti_msp_dl_config.c:92:26: error: use of undeclared identifier 'IOMUX_PINCMNone'
            IOMUX_PINCMNone, IOMUX_PINCMNone, IOMUX_PINCMNone, IOMUX_PINCM5,
                             ^
    syscfg/ti_msp_dl_config.c:92:43: error: use of undeclared identifier 'IOMUX_PINCMNone'
            IOMUX_PINCMNone, IOMUX_PINCMNone, IOMUX_PINCMNone, IOMUX_PINCM5,
                                              ^
    syscfg/ti_msp_dl_config.c:96:30: error: invalid application of 'sizeof' to an incomplete type 'const uint8_t[]' (aka 'const unsigned char[]')
        for(int i = 0; i < sizeof(unusedPinIndexes)/sizeof(unusedPinIndexes[0]); i++)
                                 ^~~~~~~~~~~~~~~~~~
    4 errors generated.
    gmake: *** [syscfg/ti_msp_dl_config.o] Error 1
    gmake: Target 'all' not remade because of errors.


    Disabling "Configure Unused Pins" does resolve this issue, but then BSL cannot be deactivated while defining the I2C SCL pin as PA1/NRST. So the original issue remains.

    Best regards,
    Ambroise

  • Sorry Ambroise for the hassle. 

    I'm having the SW team look into this.

    Another option would be to copy a .syscfg file from another example from latest SDK, delete this one that is causing issues, then recreate the configuration using the new .syscfg file.

  • Hello Dennis,

    Thank you for looking into this, we have built an entirely new sysconfig file from scratch with the new SDK.  We have never managed to deactivate the BSL with whatever trick. It will still not boot even with a new sysconfig file.

     Also, the current error shown with the “IOMUX_PINCMNone” issue is only due to the “set unassigned pin” setting. 

    Best regards,

    Ambroise

  • Hello Dennis,

    We were not able to properly resolve these issues so far. Have you heard back from the SW team?
    Thank you and best regards,

    Ambroise