Part Number: BOOSTXL-DRV8323RS and BOOSTXL-DRV8323RH

We are not planning to revise MotorWare from the current v18. However, many of our customers are evaluating and designing with the latest DRV832x Motor Drivers, so we are providing a solution for how to support with our existing InstaSPIN enabled LaunchPads and v18 of MotorWare.

BOOSTXL-DRV8323RS and BOOSTXL-DRV8323RH evaluation module (EVM) can be mounted on the LAUNCHXL-F28069M or LAUNCHXL-F28027F.

This document shows how to use BOOSTXL-DRV8323RS or BOOSTXL-DRV8323RH EVM with LaunchPadXL-C2000 to implement the evaluation or development in the latest MotorWare software.

Attached a quick user guide and 6 example lab projects.

qsg_hw_boostxl-drv8323rs_reva.pdfboostxldrv8323_package_mw.zip

Question:  Where can I find information to get started with software?  Where are the peripheral examples, Math, DSP, or DigitalPower examples?

Part Number: TMS320F28035

In looking at the F2803x datasheet, I'm trying to determine two things:

1. What are all the strategies that can be deployed for ADC calibration, including steps necessary to implement them?
   1. self-recalibration
   2. offset calibration (if self-recalibration is occuring, is there nothing else that can improve this?)
   3. two point gain calibration
   4. temperature compensation
   5. etc...
2. After deploying all the necessary ADC calibration, what is the resulting total unadjusted error?

Let's assume that periodic self-recalibration occurs.  It appears as though the INL and DNL are not additive.  This would leave INL as the worst of the two at 4 counts.  What I don't understand is whether what other errors are additive:

1. Channel-to-Channel offset and gain variation does not appear to be an absolute error added to the total unadjusted error of a given channel.
2. gain error appears to be additive, and the total unadjusted error added would be a factor of the accuracy of a two point gain calibration reference.
   1. If gain calibration happens on only one channel, does the channel-to-channel variation come back into play?
3. The temperature coefficient would appear to be additive to the total unadjusted error.  It could to some extent be compensated for with a temperature measurement.
   1. How much of the temperature coefficient is accounted for in the periodic self-recalibration?

In summary, I'm trying to understand what all goes into determining the absolute worst case total unadjusted error, and what strategies can be deployed to minimize it?

Thanks,

Stuart

Motorware v18 has officially been released. Find some of the changes enumerated below:

• HAL_setTrigger() change to fix issue where when USER_NUM_PWM_TICKS_PER_ISR_TICK was set to 2 or 3, and ISR execution time was less than half of ISR period, ADC trigger would sometimes be missed
• Fixed issue in GPIO_setPortData() for F2805x that had incorrect parameter data width
• Fixed usDelay() issues in all hal.c files, replaced with US_TO_CNT() macro
• Fixed CMP saturation limit in HAL_WritePwmData() in hal.h for F2805x only, changed lower limit from _IQ(0.0) to 1
• Update PWM_setSocAPulseSrc() in all pwm.c
• Remove OVM functions in lab5h and remove svgen_current.c file in project
• Fixed compiler error in hal.h for 06x projects with HVKit due to an error in #ifdef statement for HALL GPIO pin numbers
• Fixed LED blinking timing error in main_ISR() for all FOC and MOTION files that have toggle led code (New Enhancement)
• Changed the argument of CPU_USAGE_setParams() to variable instead of fixed timer period since timer period was changed in hal.c in MW17. Affects labs: 03b, 07, 11a, and 11b (these labs use the legacy CPU_USAGE module)
• Changed the argument of FEM_setParams() to variable instead of fixed timer period since timer period was changed in hal.c in MW17. Affects labs: 03b, 07
• Changed motor definition to resolve compiler error when using IPD projects in the below user.h files:
  • \boostxldrv8305_revA\28x\f2806xF\src\user_j1.h
  • \boostxldrv8305_revA\28x\f2806xF\src\user_j5.h

• All functions running in main_ISR() in lab11x were added to “ramfunc” for reducing cycle time (New Enhancement)
• Added lab07 and lab09 project for BoostXL-DRV8305 + F2806x  "boostxldrv8305_revA\f28x\f2806xF\projects\ccs"
• Added Volt/Hertz module in modules/vs_freq/src directory. This module generates an output command voltage for a specific input command frequency according to the specified volts/hertz profile.
• Added Angle Generator module in modules/angle_gen/src directory. This module generates angle output for a specific input command frequency.
• Added proj_01b project for all kits and controllers.
• Added proj_01c project for all kits and controllers.
• Added gMotorVars[HAL_MTR2].CtrlVersion = version; to lab10d for bug fix
• Relocated CLK_disableTbClockSync() to before timebase, compare control, action qualifier, dead band and trip zone initialization loops. This was done to fix issue where PWM sync could sometimes be lost when hard-resetting MCU
• Changed RsRecalc functionality to have initial value of USER_MOTOR_Rs instead of 0, which will allow quicker settling time
• Offsets removed from user_2motors.h to avoid issue where current/voltage offsets were defined in two separate header files
• Added definition for updateRsOnLine() for lab11a, takes EST_Handle parameter instead of CTRL_Handle parameter as expected by runRsOnLine() in lab07
• Added spi.c and drv8301.c source files to all F2802xF LaunchPad projects that were designed for DRV8301 BoosterPack

Sean

Save design time and get into production faster with C2000 MCU’s with MathWorks solutions.

To begin you use MATLAB^® and Simulink^® to create and simulate your algorithms. Next you use Embedded Coder^® to generate production code of your algorithms. Embedded Coder support for Texas Instruments C2000 includes:

• • • • Automated build and execution

• • • • Block libraries for on-chip and on-board peripherals such as ADC, digital I/O, ePWM, SPI, I2C, and more

• • • • Real-time parameter tuning and logging using external mode

• • • • Processor optimized code including DMC and IQMath libraries

• • • • Ability to perform processor-in-the-loop (PIL) tests with execution profiling

• • • • Examples for motor control and power conversion that run on TI C2000 hardware

• • • • Support for standards: ISO 26262, IEC 61508, AUTOSAR, DO-178, and others

You can also generate code that runs on the Control Law Accelerator (CLA), a co-processor available on select TI Delfino and Piccolo processors.

For multicore systems, you can use SoC Blockset with C2000 Support for SoC Blockset to build your system architecture using processor, inter-processor communication, interrupt and I/O models, and simulate the architecture together with the algorithms. This allows you to partition algorithms between multiple cores to achieve design modularity and improve performance, and to account for issues like ADC-PWM synchronization and latency.

From within MATLAB you can access hardware support for Embedded Coder via the Add-On Explorer from the MATLAB toolstrip.

Search for C2000, and select to download and install free C2000 library blocks. You insert and configure the blocks, which include IO and various functions, in your Simulink model. Then you use Embedded Coder to generate production code of your algorithm and run it directly on your TI C2000 MCU. The library blocks include documentation, example models, and support C2000 Piccolo, Delfino, and Concerto families.

Note: Using Embedded Coder requires additional MathWorks software: MATLAB^®, Simulink^®, MATLAB Coder™, and Simulink Coder™.

You can also just generate production code of your algorithms which can be imported and integrated into an existing Code Composer Studio project.

--- ---

Here is more info including how-to videos and examples you can run with TI hardware kits:

• • How-to Videos and E2E posts:

    • YouTube: Programming TI C2000 Launchpad with Simulink (18:11)

    • YouTube: Using a TI F28069 LaunchPad with Simulink (16:32)

    • YouTube: Introduction to LAUNCHXL-F28069M Launchpad (Gautam Iyer, TI MVP)

    • YouTube: Introduction to LAUNCHXL-F28027 Launchpad (Gautam Iyer, TI MVP)

    • E2E: THE BEAST IS HERE: LAUNCHXL-F28379D (Gautam Iyer, TI MVP)

    • E2E: The Most Powerful C2000 Launchpad: LAUNCHXL-F28377S (Gautam Iyer, TI MVP)

• • Solution Overview:

    • Short videos (2-3 min): Embedded Coder Overview, Targeting TI Piccolo

    • Multicore simulation support using SoC Blockset with C2000 Support for SoC Blockset

    • Joint TI / MathWorks Sessions:

      • Motor Control with Embedded Coder and TI C2000 (F28069)

      • MATLAB Speaks Hardware: TI C2000 for Digital Power Applications (F28377S)

         

• • Details and Examples:

• • • C2000 Hardware Support webpages:

    • Delfino: F2833x, F2837xS, F2837xD, C2834x

    • Piccolo: F2802x, F2803x, F2805x, F2806x, F2807x, F28004x

    • Concerto: F28M35x, F28M36x (C28x + ARM Cortex M3)

    • Legacy: C280x, C281x, C2833x, F281x, F280x

    • C2000-Based Examples

       

• • Useful Links:

    • C2000 Support Release Notes

    • TI Wiki: MATLAB and CCS compatibility matrix

Content Updated 2020-11-02

Hi

We are working on ADC section of delphino  TMS320F28377DZWT. We are using 3 differential pair lines of 16 bit ADC and 5 single ended lines of 12 bit ADC.
A  3.3V reference is provided as reference voltage to ADC.

Can we use reference voltage from single voltage source for both 16 bit and 12 bit ADC?