MotorWare v17 released

The MotorWare v17 release did not address some issues outlined below

1. GPIO_setPortData() was updated for F2802x/F2806x, but was missed for F2805x
2. Compiler errors due to an absolute file address instead of relative addressing used to build in projects
   1. proj_lab02c for F2805x + DRV8301 Kit Rev D
   2. proj_lab10a for F2805x + DRV8301 Kit Rev D
   3. proj_lab11e for F2802x + HV Kit Rev 1.1

3. Compiler errors in all F2806x projects with HVKIT due to an error in the hal.h file
4. An issue with usDelay() function in all hal.c and hal_2motors.c
5. CMP saturation limit value issue in HAL_WritePwmData() in all hal.h and hal_2motors.h

As such, we plan to release a MotorWare v18 revision that will address the above items, as well as include some minor fixes and enhancements. While there is no release date to be shared at this time, development of MotorWare v18 will not include any major updates or additions and should be a relatively quick release for us.

Sean

For now, we recommend these workarounds to some of the issues in the above post:

Item 2: Compiler errors due to incorrect addressing in build

• proj_lab02c for F2805x+DRV8301 Kit Rev D:
  • Change the hal.c linked resource address from "D:/ti/motorware/dmc_mw_mw17_alpha_002/sw/modules/hal/boards/drv8301kit_revD/f28x/f2805x/src/hal.c" to "MW_INSTALL_DIR\sw\modules\hal\boards\drv8301kit_revD\f28x\f2805x\src\hal.c"
• proj_lab10a for F2805x+DRV8301 Kit Rev D:
  • Change the hal.c linked resource address from "D:/ti/motorware/dmc_mw_mw17_alpha_002/sw/modules/hal/boards/drv8301kit_revD/f28x/f2805x/src/hal.c" to "MW_INSTALL_DIR\sw\modules\hal\boards\drv8301kit_revD\f28x\f2805x\src\hal.c"
  • Change the spi.c linked resource address from "D:\ti\motorware\dmc_mw_mw17_alpha_002\sw\drivers\spi\src\32b\f28x\f2805x\spi.c" to "MW_INSTALL_DIR\sw\drivers\spi\src\32b\f28x\f2805x\spi.c"
• proj_lab11e for F2802x+HV Kit Rev 1.1
  
  • Change the EST_getIdq_pu.lib linked resource address from "D:\ti\motorware\dmc_mw_mw17_alpha_002\sw\modules\fast\lib\32b\f28x\EST_getIdq_pu.lib" to "MW_INSTALL_DIR\sw\modules\fast\lib\32b\f28x\EST_getIdq_pu.lib"

Item 3: Compiler errors in all F2806x projects with HVKIT due to an error in the hal.h file

• Please edit the following file: C:\ti\motorware_1_01_00_17\sw\modules\hal\boards\hvkit_rev1p1\f28x\f2806x\src\hal.h
• At the hal.h original lines 166-173, change the source code to reflect the following:

#else
//! \brief Enumeration for the Hall GPIO numbers
//!
typedef enum
{
  HAL_HallGpio_A=GPIO_Number_24,  //!< GPIO pin number for Hall Sensor A
  HAL_HallGpio_B=GPIO_Number_13,  //!< GPIO pin number for Hall Sensor B
  HAL_HallGpio_C=GPIO_Number_14   //!< GPIO pin number for Hall Sensor C
} HAL_HallGpio_e;
#endif

Sean

Sean: I just asked about MotorWare 18 ETA & the regression of MotorWare v17 with CCS 6.2.0 in another forum - please advise

Jim

Jim,

We do not currently have an ETA for MotorWare 18, but are hopeful that we can provide the release before 2017. Please elaborate on what you mean of regression of MotorWare 17 with CCS 6.2.0? I have not experienced any issues using MotorWare 17 on that platform. If you want to provide a link to the thread that would be useful.

Sean

Sean:
1) glad we have the motorWare 17 regression with CC 6.2.0 in play, so that is not the issue.
2) We know CCS 7.0 is coming next month (on another thread) - the question then becomes if anyone on the MotorWare team ensuring any version 17 regression is occuring with the pre-release of CCS v 7.0?
3) The follow-on question would be on what versions on CCS will MotorWare 18 be regression tested upon? I know asking for Motorware 18 to be tested with CCS v 7.0 is a stretch next month.

thanks
Jim

Jim,

We plan to support all versions of CCS from v5 onwards, save for v6.1.3. The issue with v6.1.3 was not an issue on our end, but instead an issue with floating point compilation for that install. We do not foresee any issues on any other versions going forward and will do our best to test the MotorWare platform on the major releases of CCS

Sean

Sean:

 that's a prudent move to not support CCS 6.1.3 with Motorware due to the floating point issue.

I'll also say that I had seen multiple crashes with ver 6.1.2 & backwards due to the older Eclipse Framework implementation interactions with

newer Oracle Java JSE/JRE releases.

We are baselining our Piccolo work here with CCS 6.2 with MotorWare 17 for now.

As long as TI follows the same deprecation claims by the CCS team consistently with not regression testing on unsupported Winodws versions, I'm fine with that.

(adieu, Windows XP)

thanks

Jim

Am migrating our s/w from Motorware 14 to MotorWare 17 libraries, etc. and currently using CCS version 6.1.3.00034.

Does the problem noted above with version 6.1.3 apply to all 6.1.3.xxxxx versions?

If so, what is the best CCS version to use with MotorWare 17?

Thank you,

Allan

Allan,

We do not have a preferred install of CCS, although most of the MW17 release was tested on CCSv6 (aside from v6.1.3). Please have a try of any install besides this one from http://processors.wiki.ti.com/index.php/Download_CCS

I personally use 6.2.0.00050 with no issues

Sean

Thanks Sean. Any project to run two sensorless ACIMs on the LAUNCHXL-F28069M?