Hello Tarun, Thanks for reaching out. Glad to hear the internal loopback mode is working as expected. Can you describe the test setup you are using? At least one other operating CAN node must be present for non-internal loopback mode configurations to properly communicate data on the CAN bus. Best Regards, Zackary Fleenor
↧
Forum Post: RE: AM263P4-Q1: MCAN Mode Issue with canfd_external_read_write example from the AM263Px MCU+SDK (Version 10.01.00.31)
↧
Forum Post: RE: TMS320F28P550SJ: ADC samples Read problem in TMS320F28P550SJ9 controller
Hi Rakesh, Probabaly i think the below Function bit is not getting configured in the above code (It enables TS out to ADC). ASysCtl_enableTemperatureSensor(); This is there in Sysconfig example correctly. Adding the Below line above "// Set ADCCLK divider to /4" line in code should make it work. "AnalogSubsysRegs.TSNSCTL.bit.ENABLE=1;" BR, Nilesh
↧
↧
Forum Post: RE: AM263P4-Q1: Issues with MCAN Peripheral on AM263Px CC: Extended CAN ID Transmission and Reception
[quote userid="628873" url="~/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1462915/am263p4-q1-issues-with-mcan-peripheral-on-am263px-cc-extended-can-id-transmission-and-reception/5618087#5618087"]The issue is that there are no specific receive functions or their initializations in the mcan.c and mcan.h files. Whenever I attempt to write any of the functions, I encounter the error shown in the attached screenshot.[/quote] This issue has been resolved correct?
↧
Forum Post: LAUNCHXL-F280039C: Launchpad debugger not responding
Part Number: LAUNCHXL-F280039C Tool/software: Hi, I am providing a training session on digital control for power converters using LAUNCHXL-F280039C boards. Some of the boards are brand new, and on first attempt at programming the controller, participants were asked to update the debugger. There might have been some clicking without reading, and some of the participants were not connected to the internet, or with a bad connection. In the end, some of them ended up with debuggers refusing to do their jobs. The error is similar to this post . Something probably went wrong during the update, and the debuggers don't show up in the peripheral managers, and are not detected by xdsdfu. Unlike this post, I have not tried anything with any TDO pin, though. Hopefully there is something I can do so that the training can resume tomorrow ... Thanks in advance, Adrien
↧
Forum Post: AM2432: modbus end of frame detection and IRQ
Part Number: AM2432 Tool/software: Hi Sitara champs, Is it possible to detect automatically a modbus end of frame to generate an interruption ? Thank you! Best, Guillaume
↧
↧
Forum Post: RE: TMS320F280041C: C2000Ware MotorControl SDK 5_03 Lab04 problem
Are you using your own board? Or the supported TI EVM kit? Please check if the current sensing configuration is correct if you are using own board.
↧
Forum Post: RE: AM2434: tiny-USB Module Application affect the others IRQ trig timing
Both, Rich AM64 system interconnect contains two types of end points: VBUSP vs VBUSM. VBUSM interface supports multiple transactions in flight while VBUSP interface only support a single transaction. When multiple transactions are sent to the same end points, it will cause temporally stall. If there is an inflight write transaction, the bus will stall until both the write command and write data are completed. For read transaction, the VBUSP interface will be blocked until the read data is returned back and bus is free of any in flight transactions. So the temporally stall caused by read transaction from a VBUSP interface depends on how soon the read data can be returned back. It is typical that a group of VBUSP end points are behind a single VBUSP. If you are accessing a peripheral in your ISR which is shared with the USB, and due to noise USB reads/writes take longer, then there will be a temporal stall in the shared VBUSP interface leading to a stall in the ISR processing. Note the ISR trigger would remain unaffected as this would be via a different path than the shared VBUSP. Assuming that GPIO is being used in the ISR, the access to GPIO may be stalled due to a stall in USB register access (due to noise). Due to stalling of GPIO access, the ISR processing may take more time. This is just an example, but something similar may be happening in your system. I'm attaching a snippet from the AM64 topology, will share the full document with Rich. The blue box is the vbusp you are interested in and red box is the usb registers. This shows you the peripherals which are under the same 32b VBUSP interface. Any of these peripherals being used in the ISR will lead to ISR processing taking more time in cases when there are stalls in USB processing due to noise. Additional note on the use of USB in high noise environments. USB was designed as a low-cost consumer electronics interface where fail-safe is not a requirement. The design of the connectors and the 2.0 cable actually make the interface very susceptible to noise coupling. The TI SoC USB function is designed, implemented, tested, and functionally/electrically validated to meet the requirements of the USB2.0 Standard but the limitations of the interface will typically preclude it being used in a mission critical infrastructure. Hence in such systems, usage of USB in high noise environments is not recommended. Regards Karan
↧
Forum Post: RE: TMS320F28069M: C2000 InstaSPIN Universal GUI Connecting to LaunchXL-F28069M
Yes. You have to use C2000 InstaSPIN Universal GUI if you want to make any changes. You need to change the GUI as well if you change any variables in the object struct in the project. Yes. It's for F280049C project, you can refer to it to change the C2000 InstaSPIN Universal GUI for F28069M. If you just want to develop or evaluate the lab, you may run and debug the project within CCS, without using GUI.
↧
Forum Post: RE: MSP430FR2475: Regarding MSP430 MCU firmware upgrade
The BSL startup sequence includes an MCU reset via the RST pin, so it can get control even if there is firmware running. The reset sequence (standard, then BSL) is described in FRAM BSL Guide (SLAU550AB) Sec 3.3.2. For the BSL, the TEST pin is wiggled in a particular pattern during the RST sequence. As I recall, BSL Scripter only issues this sequence when you ask for it. However, the act of connecting the wires could (conceivably) cause glitches which might imitate one of the RST sequences.
↧
↧
Forum Post: RE: MSPM0C1104: GPIO Read Operation failing when using the driver generated by Sysconfig
Hi Yogesh, I see on line 79,80 you are using the GPIO interrupt, correct? I also see on line #78 you selected rising edge, which based on the button connected to PA16, and you are using internal pull ups, you won't detect when the button is pressed because it is going from high->low. But it should when you release the button low->high. You might also try this: if (DL_GPIO_readPins(GPIO_LEDS_PORT ,LEDS_InputPin_PIN) != ~LEDS_InputPin_PIN)
↧
Forum Post: RE: TMS320F28379D: Software Continuous Forced Action on EPWM
Hello, Disable action for Continuous SW force is not done using logic gates which would make action to happen immediately when called. But it's tied to Action Qualifier action which happens at the event, in this case event counter zero event. That's why the waveform is like shown in blue.
↧
Forum Post: MSP430F5359: I've noticed that there are undocumented qualifiers to the CGT cl430 compiler
Part Number: MSP430F5359 Tool/software: I was looking at some of the interlisted .asm files produced by the cl430 compiler and I noticed in the header lines that it makes reference to two sets of qualifiers that are undocumented: --mem_model:code={large|small} --mem_model:data={large,small,huge} --mem_model:code is pretty obviously a direct synonym for the --code_model={large|small} qualifier which IS documented. --mem_model:data looks like it's a near-synonym for the --data_model={restricted,small,huge} qualier (with the model types in that order). I mention this only because: If you really want them to be undocumented, you should probably make the listing files use the documented versions of the qualifiers so the undocumented versions stay hidden - or - If the listing files are going to keep showing these versions, you should probably document them in SLAU132Y, the MSP430 Optimizing C/C++ Compiler (v21.6.0.LTS) User’s Guide.
↧
Forum Post: RE: MSPM0G3519: MSPM0G3519 - BOR check
Hi John, I recommend reading the BOR Supervisor section of the TRM , currently section 2.2.3.2 Brownout Reset (BOR) Supervisor in the Rev B version. BOR level 3 is what you would want for 3V. You can check the NMI for the BOR. What I would do in the NMI is clear the BOR status, wait a bit then check the raw status to see if the BOR is still there, if the BOR is gone then I'd exit the loop and return to main. Relevant registers - BORTHRESHOLD and BORCLRCMD in SYSCTL, then the BORLVL interrupt. Regards, Luke
↧
↧
Forum Post: RE: LAUNCHXL-F280039C: Launchpad debugger not responding
Hi Adrien, You are getting what is known as a "Host Connection Error". Basically, the debugger is unable to communicate with the debug probe. Error 260 is described in the Debugging JTAG page below, together with tips to fix this issue (search for the error number): https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html Hope this helps, Matt
↧
Forum Post: RE: TM4C129ENCPDT: NDK_Send blocking - using a mailbox within the tcpEcho example
Hi Noah, Does the processor reach the Task_sleep(GetSleepTickCount())? The RTOS ticks is 1ms by default. Did you somehow change the tick rate? If you use the default 1ms, you cannot do 500uSec sleep. Why don't you try a longer delay with several mS to see if it makes a difference.
↧
Forum Post: RE: TMS320F280039-Q1: Mem Map file
Hi, It sounds like you are trying to change the memory allocation for specific code sections. Is that correct? If so, you will want to modify the linker command file (.cmd) to specify where you want to partition the memory and use PRAGMAs to allocate code functions to these sections of memory. Below is a document that explains the memory partition on the device. https://software-dl.ti.com/ccs/esd/documents/c2000_c28x-compiler-understanding-linking.html Regards, Ozino
↧
Forum Post: RE: LP-MSPM0L2228: I2C stop condition enable/disable
Hi Daniele, Bruce's solution should help you fix this stop condition. I also recommend downloading and installing the latest version of the SDK. Best Regards, Diego Abad
↧
↧
Forum Post: RE: MSPM0-ANALOG-CONFIGURATOR: MSPM0 Analog Configurator - How to ADC with OPAmp?
Hi James, Remove the jumper on the bottom right J18. Regards, Luke
↧
Forum Post: RE: MSPM0G3507: A high-frequency sound is heard while the motor is running.
Hi Donguk, Are you using a TI board or a custom board for your tests? Regards, Luke
↧
Forum Post: RE: TM4C129ENCPDT: NDK_Send blocking - using a mailbox within the tcpEcho example
Good suggestion. I'll give this a try. FYI - I am using this function to change the tick //============================================================================= /** @return - int32_t: positive values means pass; negative values means error Calculates and assigns the sleep tick value, and it is set to 10 mSec (currently). */ static int32_t CalculateSleepTick ( uint32_t* val ///< value of sleep ticks by reference ) { int32_t returnVal = -1; if (val) { returnVal = 1; /* We want to sleep for macro-defined microseconds */ *(val) = TASK_SLEEP_TIME_MICROSECS / Clock_tickPeriod; } return returnVal; } #define TASK_SLEEP_TIME_MICROSECS 10000u
↧