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.

LAUNCHXL-F280049C: Running LaunchXL-F280049C with BoostXL-DRV8301

Part Number: LAUNCHXL-F280049C
Other Parts Discussed in Thread: BOOSTXL-DRV8301, , DRV8301, DRV8320, BOOSTXL-DRV8320RS

Hello,

I would like to use the BoostXL-DRV8301 (Rev B) on a LaunchXL-F280049C (Rev B).

In the software, I can see switches for the DRV8301, but I could not
find any information in the user guide for the LaunchXL-F280049C
telling which predefined swiches need to be set in order to run.

So, first question. Has the software been prepared for use with the
BoostXL-DRV8301?

And second question. If yes to #1, what predefinded switches do I
need to set in order to use this combination?

Greetins,

John

P.S. In the enumeration Board_Kit_e, one of the elements is BOARD_DRV8301_REVD.
Is this maybe the right switch for the BoostXL-DRV8301.

  • Hi John,

    So, first question. Has the software been prepared for use with the
    BoostXL-DRV8301?

    Hardware wise the LAUNCHXL-F280049C does support the BoostXL-DRV8301. However software wise we don't have specific InstaSPIN FOC sample code supporting DRV8301 in the Motor Control SDK (MCSDK). You can refer to the example code for DRV8320RS in the SDK instead and change some configurations in hal.c and user.h accordingly by yourself.

    Best,

    Kevin

  • Hello Kevin,

    thank you for your suggestion. You mention that there is no sample code for the DRV8301, however in the sample code for the DRV8320, I find traces referring to the DRV8301, such as BOARD_DRV8301_REVD for the board kit (if this is not the BoostXL-DRV8301, what board is this?) or the predefine DRV8301_SPI in labs.h. Does this means that the software structure in the sample code would work with the DRV8301, but it is not completed? Please explain?

    Regards,

    John

  • Hi John,

    The code below does not actually affect the software configuration. They're only for showing which board is being used.

    #ifdef _HVKIT_REV1p1_
        motorVars.boardKit = BOARD_HVMTRPFC_REV1P1;
    #endif // _HVKIT_REV1p1_
    
    #ifdef _DRV8301_KIT_REVD_
        motorVars.boardKit = BOARD_DRV8301_REVD;
    #endif  // _DRV8301_KIT_REVD_
    
    #ifdef _BOOSTXL_8320RS_REVA_
        motorVars.boardKit = BOARD_BSXL8320RS_REVA;
    #endif  // _BOOSTXL_8320RS_REVA_

    You will need to change the hal.c, hal.h, and user.h files according to the board being used. Also, BOOSTXL-DRV8320RS utilizes the F280049C device's internal PGAs. It may be more straightforward to use the BOOSXL-DRV8320RS directly instead, since software support already exists for the F280049C device.

    Alternatively you could look at the HW support and solutions in the universal lab below and port from F28002x to F28004x, which shouldn't be difficult.

    https://www.ti.com/lit/spruj26

    Best,

    Kevin

  • Hello Kevin,

    okay, I understand what you mean with the use of the PGAs, which would require a HW modification on the BoostXL board. This is an option, but maybe not the best.

    I took a look at your suggestion with the universal lab and see it is build for the F280025. However, there is a section on adapting to the F280049C and also a section on adapting for custom hardware. It seems straight forward enough and I would be willing to give it a try, but the devil is often in the details. The F280049C ist still a "new" processor for me and I have no experience with the F280025. What kind of support can you guys offer if I get stuck or am I on my own?

    Cheers,

    John

  • Hi John,

    I think that's a better plan.

    What kind of support can you guys offer if I get stuck or am I on my own?

    If you get stuck and have questions while porting the code you can ask on this E2E thread or start a new one. The more specific you can make / narrow-down the question the better we'll be able to assist usually..

    Best,

    Kevin

  • Hello Kevin,

    I am giving it a go and will close the tread here. At a note, one place where I am not quite clear is in adapting the linker file, but I will put this in a new thread as you suggested. On this topic the users guide instructs the use of templates in the SDK as reference, but there seems to be a specific structure for the sections which is not described in the user guide. Is there perhaps further documentation on TI's concepts behind the linker script and the universal lab project in addition to the user guide?

    https://www.ti.com/lit/spruj26

    Greetings,

    John