TMS320F280049C: InstaSpin GUI

The R/W commands exist in the target and target does read all the DRV8320RS registers on Xrsn pushed.

The dead time on the NexFETS default 100ns but these NFET have 36ns dead time, 50ns would produce finer granular results. The GUI commands sent to target below don't seem to work so we can't easily reduce NFET dead time via the GUI. I'd make 50ns the minimum dead time for this BoostXL kit. We actully use 180ns with other NFETS but that is for 6 step commutation modulation.

    // Manual read from the DRV8320
    if(drv8320SPIVars->manReadCmd)
    {
        // Custom Read
        drvRegAddr = (DRV8320_Address_e)(drv8320SPIVars->manReadAddr << 11);
        drvDataNew = DRV8320_readSPI(handle, drvRegAddr);
        drv8320SPIVars->manReadData = drvDataNew;

        drv8320SPIVars->manReadCmd = false;
    }

    // Manual write to the DRV8320
    if(drv8320SPIVars->manWriteCmd)
    {
        // Custom Write
        drvRegAddr = (DRV8320_Address_e)(drv8320SPIVars->manWriteAddr << 11);
        drvDataNew = drv8320SPIVars->manWriteData;
        DRV8320_writeSPI(handle, drvRegAddr, drvDataNew);

        drv8320SPIVars->manWriteCmd = false;
    }

Hi Whitney,

Whitney Dewey said:

Do you see an error on the GUI  next to the read/write interface items too?

No error but it also silently updates XDS110 frimware too and CCS9.1 debug states firmware is again out of date each time I run the GUI v1.0.0.

Whitney Dewey said:

Can you try importing the GUI into the GUI Composer editor and correcting them? Once they're fixed, save and run and see if the updates work.

The GUI is configured for standalone local mode. I don't have GC v2,0 runtime editor and was told they are now all built in the cloud, has that changed? 

Yes, you'll need to use GC v2.0 on dev.ti.com. Are you accessing the GUI from the Gallery? From the Gallery there's a button your can hit to bring the project into the GC editor and from there you'll be able to click on the read/write buttons and the manual read/write text boxes to fix their variable bindings.

Whitney

Whitney Dewey said:

Are you accessing the GUI from the Gallery?

No not yet as I just tried to import the SDK GUI into the Cloud GC and get invalid signature error for the project file, index.json or project.json

InstaSpin GUI was installed from SDK 2.01.00.00 so it should be up to date with the cloud GC.

Whitney Dewey said:

Yes, you'll need to use GC v2.0 on dev.ti.com.

 I believe it was updated recently v2.19.12, perhaps reason for signature error any attempt to import existing GUI project. 

Whitney Dewey said:

. Are you accessing the GUI from the Gallery?

Is the gallery AKA - CCS application center GUI composer?  I don't see the C2000Ware_MotorControl page icons your showing above in the application center. That takes me into the cloud to compose new or import existing GUI. The GUI Help read me only brings up the warning page about lab is05. There is no gallery menu item in CCS-9.1 view tab.

I was easier to simply edit the index.json file for the above changes. Like to import the GUI to change a few things at a later date. 

Hi Whitney,

The patch of existing commands to index.json did not fix the GUI Read/Write function buttons. Searching each one to replace the single letter via notepad.

Now seems to read/write ok after replacing the *.out file in target folder. 

Thanks Whitney!

Great. Thanks for confirming that that took care of it. Like I said, I've filed a bug to get this fixed in a future GUI update too.

Whitney

Well it seemed to be working from the GUI point of view anyway. After forcing dead band time to 50ns via application, read of drv8320 data into CCS variables window shows 100ns was still set after InitDrv8320(). The nFault flag in the faults flags variable was tripped 1, all others were 0. Any forced faults of Trip zone sub module fail to set flags. It don't surprise me either Tz2 was set (nFault), cleared flag to 0 via debug. Last week I also opened a forum case for the Trip zone sub module ignoring forced faults from the 3 CMP's. 

There is no indicator in the GUI of faults status, might be a good thing to add in the next update.