Part Number: TMS320F28069 Other Parts Discussed in Thread: SYSBIOS I am new to SYS/BIOS, mostly worked on bare-metal in the past. I am seeing an issue related to zero/low-latency interrupt ISR call for XINT1. On bare-metal I have add code to allow interrupt…
Part Number: TMS320F28069 Other Parts Discussed in Thread: LAUNCHXL-F28069M , C2000WARE Hello,
I have strange issue with GPIO32 pin toggling on the board LAUNCHXL-F28069M.
A GPIO configuration is done as described in Example_2806xGpioSetup.c of C2000Ware_4_02_00_00…
Hi ,
Can you try to force the stack to be in host mode by calling the following function after USBHCDTerm
USBStackModeSet(0, eUSBModeForceHost, ModeCallback);
Also , is this the same query as below -
https://e2e.ti.com/support/microcontrollers/c2000-microcontrollers…
Part Number: TMS320F28069 Other Parts Discussed in Thread: CONTROLSUITE I am using HRCAP_Cal() and int the TRM: TMS320x2806x Microcontrollers Technical Reference Manual (Rev. I) (ti.com) Page: 414, it is mentioned that in the function: Uint16 HRCAP_Cal(Uint16…
Part Number: TMS320F28069 Other Parts Discussed in Thread: TCAN1042-Q1 Dear Experts,
I have noticed a strange behavior of the CAN module in my application when the temperature drops to very low levels (-30 ~ -40°C). The CAN viewer shows a burst of CAN…
Part Number: TMS320F28069
The attached code uses PWM2 to generate some test pulses of fixed frequency,10kHz and fixed duty cycle (40%).
The pulses are read in on GPIO13. XINT1 is enabled on GPIO13 with rising edge detection ON. So whenever the PWM2 pulse…
Part Number: TMS320F28069 Dear Experts,
I would like to inquire about the operating temperature limit of TMS320F28069PZP. I utilize the internal temperature sensor on Channel A5 to monitor on-Chip temperature. In our application, the chip temperature can…
To update you on this matter
1. proper initialization can solve the issue. All Cla-to-Cpu variables need to be initialized in the CLA Task.
2. Cpu-to-Cla and DataRam can be initialized in the CPU.
3. pointer casting to Cla-to-Cpu did not cause the issue…