Part Number:TMS320C6678
Tool/software: TI-RTOS
Hi,
I am trying to use assert statement for debugging purpose for an SYSBIOS project on C6678 processor. Can someone point me to a basic example please..? Also any good references for debugging a multicore programs would be really appreciated. Thanks in advance.
Environment: Linux/Windows (I use both OSs).
Processor: C6678
Additional packages: SYS BIOS (V 6.46.4.53)
Thank you.
Part Number:TPS2379
The data sheet in Table 1 gives the classification resistor possibilities as 63.4 Ohms, 90.9 Ohms, !37 Ohms, 243 Ohms or 1270 Ohms. The EVM datasheet says in section 3 that a shunt on J7 can be added to give 45.2 Ohms. But that is not one of the possible classification resistors. It seems to be a contradiction.
Part Number:TLV320AIC3106-Q1
e2e,
Would you please recommend me an audio codec that can detect weather a CTIA or OMTP headset is inserted into and audio jack and support both types of headsets?
I would also like this device to be automotive Q1 qualified.
Thank you,
Adam
Part Number:LMX2595
We recently purchased the LMX2595EVM board and when doing a phase noise analysis we received results that were far worse than expected. The phase noise chart generated by our ESA was about 30dB worse across the nearly the entire range. Is there anything that we are doing wrong? I've attached the PLL settings we used from TICS Pro along with the chart generated. We were testing at 15GHz and using the default settings, which I believed the EVM's loop filter was optimized for. Thanks
Part Number:LM25118
Hello!
I am using the LM25118 in my design. And a question arose as to the connection of the 8 - FB and 9 - Comp pins, since they are different in the schematic reference of the datasheet and compared with the schematic contained in the Evaluation Board (SNVA614B).
Which link should I consider correct to follow with my design? What is contained in the datasheet or what is in the Evaluation Board documentation?
Attached is the print of the circuit difference for a better understanding.
Other information on my design.
Vin = 3.3V at 4.2V.
Vout = 5V
Iout = 2A
EVALUATION BOARD SCHEMATIC
DATASHEET TYPICAL APPLICATION SCHEMATIC
I thank you and I'm waiting!
hi TI professor，
1、There are errno = ICall_wait(ICALL_TIMEOUT_FOREVER) in SimpleBLEPeripheral_taskFxn function. I wanner know what event will trigger SimpleBLEPeripheral_taskFxn function to run.
2、There are Util_constructClock(&periodicClock, SimpleBLEPeripheral_clockHandler,SBP_PERIODIC_EVT_PERIOD, 0, false, SBP_PERIODIC_EVT) in SimpleBLEPeripheral_init function. The timer state is false to wait.So what condition will run to
if (events & SBP_PERIODIC_EVT)
{
events &= ~SBP_PERIODIC_EVT;
Util_startClock(&periodicClock);
// Perform periodic application task
SimpleBLEPeripheral_performPeriodicTask();
}
Part Number:SN65HVD234
Is there a minimum termination resistance value (across CANH and CANL) to guarantee that the R output will correctly duplicate the data sent on the D input? We have a problem with our power control software, which depends on the data received on the R pin being the same as the data transmitted on the D pin. The R pin data will be corrupted if the CAN bus is not terminated, but we do not want to include a 120 ohm resistor inside our equipment. Experimentally, about 2K ohms seems to do the trick, but I wonder if there is a minimum value I can rely on.
Part Number:BQ34110
Hi,
I'm using the BQ34110 with 5 series NiMH cells (nominal voltage 1.2V/cell), and I'm trying to follow the procedure to generate the GPC logs so I can get the correct CEDV parameters. However, I'm running into two issues:
1) I'm having a hard time getting the FC bit to set after a full charge, so when I try to run the GPC Cycle, it's stuck waiting for FC=1 forever. It seems setting this bit is somewhat dependent on the current EDV thresholds (the default values for which seem like they're for a Li-Ion cell), so do I need to change these values in order to make the chip realize there has been a qualified charge?
2) I am able to calibrate the voltage measurement, but I'm seeing huge measurement error the further away I get from the voltage at which I calibrated. I am using 1% resistors for my external divider at the moment, but I have ordered 0.1% values as a precaution. That being said, it seems odd the voltage measurement is off by so much.
Thanks for your help!
Kyle
Part Number:UCD9081
Hi Team,
My customer is surveying UCD9081 and has some questions, please could team help to comment on this.
1. Can UCD9081's I2C interface connect to other devices with PMBUS interface?
2. How to configure the enable pin's output polarity?
3. Is there any example of commend setting can be shared with customer?
Thanks very much.
Vincent Chen
Part Number:AM3358
Tool/software: Linux
Hello,
We finally have our first AM3358 board. I'm trying to bring it up using USB RNDIS boot. The SYSBOOT pin strapping matches the beaglebone black.
When I power on the AM3358 board, it comes up in lsusb as:
Bus 001 Device 062: ID 0451:6141 Texas Instruments, Inc.
Running tcpdump on the USB ethernet interface, I see:
tcpdump -n -i $(ifconfig | grep enp0s20 | awk '{print $1}') port 67 or port 68 or port 69
08:53:47.197009 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 74:e1:82:96:9c:b4, length 364
08:53:47.200006 IP 192.168.2.1.67 > 192.168.2.2.68: BOOTP/DHCP, Reply, length 300
08:54:06.729362 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 74:e1:82:96:9c:b4, length 364
08:54:06.731799 IP 192.168.2.1.67 > 192.168.2.2.68: BOOTP/DHCP, Reply, length 300
08:54:30.167931 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 74:e1:82:96:9c:b4, length 364
08:54:30.189133 IP 192.168.2.1.67 > 192.168.2.2.68: BOOTP/DHCP, Reply, length 300
08:55:16.672206 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 74:e1:82:96:9c:b4, length 364
08:55:16.673394 IP 192.168.2.1.67 > 192.168.2.2.68: BOOTP/DHCP, Reply, length 300
One time, I actually saw the TFTP request for u-boot-spl.bin, but haven't been able to get it to happen again.
To validate my laptop configuration, if I wipe the eMMC of a beaglebone and plug in the USB, I see this:
08:57:51.275150 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 74:e1:82:74:1f:37, length 364
08:57:51.277373 IP 192.168.2.1.67 > 192.168.2.2.68: BOOTP/DHCP, Reply, length 300
08:57:51.280269 IP 192.168.2.2.1234 > 192.168.2.1.69: 34 RRQ "u-boot-spl.bin" octet
08:57:54.472525 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 74:e1:82:74:1f:39, length 300
08:57:54.718783 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 300
08:57:54.719429 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 74:e1:82:74:1f:39, length 300
08:57:54.722467 IP 192.168.2.1.67 > 192.168.2.3.68: BOOTP/DHCP, Reply, length 300
08:57:54.742590 IP 192.168.2.3.4022 > 192.168.2.1.69: 53 RRQ "u-boot.img" octet timeout 5 blksize 1468
So I'm pretty confident that my laptop is configured properly for RNDIS boot.
How can I debug this issue? Would connecting JTAG give me any feedback from the Boot ROM if it is encountering some error that prevents making the TFTP request? Is there somewhere I can find the source code for the boot rom?
Thanks,
Matt
Part Number:BQ51003
Hi,
I have following setup: the charger is made up of the bq500511A/bq50002A combination and the receiver is a bq51003 followed by a bq25100 for charging a Li-Ion battery. Initially I was OK with the LED on the charger always blinking when the wireless connection is established (if there are no faults), but now I am looking to have End of Charge (EOC) indication on the LED as well (constant on instead of blinking). Therefor we are looking at using the bq25101 instead of the bq25100 to feed the CHGn pin back to the bq51003 TS/CTRL pin using the top half of a tri-state driver. Since the CHGn pin is inverted (low when charging), we inverted the signal first using a simple nMOS. I put the pull-up resistor for the CHGn to the output of the bq51003 = the input of the bq25101. The problem now is that the input of the bq25101 comes up a little bit faster than the CHGn pin can react (this is at least what I understand from the datasheet under 8.4.2: Power-Up), causing the nMOS to conduct, leading to an immediate EOC message back to the transmitter. When I put the RX coil on the TX coil, I notice that the LED on the charger is blinking (indicating charging), but the battery itself is not charging (current measurement is not negative). The battery voltage is 3.85V, so there should be enough headroom to charge further still. I have included screenshots from the TS/CTRL pin (with the square pulses) and the CHGn (with the tails).
Is my whole idea of using bq25101 and feeding the information from pin CHGn back to the TS/CTRL pin something that is possible (and perhaps already done before)? And if so, could you see something wrong with my design?
If there is anything that is still unclear or if you don't have the complete information, please let me know.
Best regards,
Wout
Part Number:AMC1203
Hi,
I have several questions about the AMC1203. Can you help me to explain them ASAP?
1. Whether the OSR in the AMC1203 document is the same concept as the decimation ratio in the sinc3 filter?With 256?
2. Is the decimation ratio the divider factor of MCLK clock?
3. Combining the ADS1202 with an FPGA Digital Filter for Current Measurement in Motor Control Applications
In this document, the Sinc3's filter(designed by FPGA) bus output bandwidth is 25 bits. The question is how is the result of the final output corresponding to a 16-bit sampling resolution (AMC1203 written document is a 16-bit resolution)?
About the third question, in the document Combining the ADS1202 with an FPGA Digital Filter for Current Measurement in Motor Control Applications, the final output data CN5 is 25(which can be found in VHDL program), but in the recent VHDL (slac055) download file, CN5 is 24.
In slac055 : When the decimation ratio is 256, pick the higher 16 bits as the output value, so I want to ask what we should choose for CN5.25 bits or 24 bits?
Best regards
Part Number:CC1350
After programming the host_test_cc1350lp_app I get the following message when trying to communicate with the cc1350 board.
Please advise.
1] : <Info> - 10:10:50.574
Port opened at 7/16/2018 10:10:50 AM
--------------------------------------------------------------------
[2] : <Tx> - 10:10:51.963
-Type : 0x01 (Command)
-OpCode : 0x0C03 (HCI_Reset)
-Data Length : 0x00 (0) byte(s)
Dump(Tx):
0000:01 03 0C 00 ....
--------------------------------------------------------------------
[3] : <Error> - 10:10:53.988
Message Response Timeout
Name = HCI_Reset
OpCode = 0x0C03
Tx Time = 10:10:51.963
--------------------------------------------------------------------
[4] : <Warning> - 10:10:54.014
Device Reset Timeout
Device May Not Function Properly
--------------------------------------------------------------------
Part Number:LAUNCHXL-CC1350
After programming the host_test_cc1350lp_app I get the following message when trying to communicate with the cc1350 board.
Please advise.
1] : <Info> - 10:10:50.574
Port opened at 7/16/2018 10:10:50 AM
--------------------------------------------------------------------
[2] : <Tx> - 10:10:51.963
-Type : 0x01 (Command)
-OpCode : 0x0C03 (HCI_Reset)
-Data Length : 0x00 (0) byte(s)
Dump(Tx):
0000:01 03 0C 00 ....
--------------------------------------------------------------------
[3] : <Error> - 10:10:53.988
Message Response Timeout
Name = HCI_Reset
OpCode = 0x0C03
Tx Time = 10:10:51.963
--------------------------------------------------------------------
[4] : <Warning> - 10:10:54.014
Device Reset Timeout
Device May Not Function Properly
--------------------------------------------------------------------
Part Number:CC1352R
Hello,
I'd like to know if it is possible to run Tx or Rx radio commands before starting Bios ?
Indeed, it seems that Rx or Tx commands sent before runtime do not work (and "RF_runCmd" generates an exception).
I need to implement an OTA update which works without scheduler.
Thank you for your help
Environment
sdk 2.10.00.48
2.4Ghz IEEE 802.15.4
Part Number:TMS570LC4357
I have the following request from a customer:
Can TI give an example circuit that meets ISO13849 PLd Category 3 using Hercules and Safety PMIC (TPS65381Q1)?
This customer is planning to use the TMS570LC4357.
Let me know if more information is needed.
Part Number:ADC34J44
Hi
I am interested in the ADC34J44EVM and/or ADC32J44EVM and was wondering if there is a way to operate the quad channel ADC at a rate lesser than 125MSPS and how. I already have a TSW14J56 with me.
I installed the GUI for the above EVMs and I was only able to see config1.cfg and config2.cfg files in the relevant directory and was not able to find any other cfg files mentioned in the user's guide
Part Number:WL1837MOD
Hello,
We have a customer who used our WL1837MOD based devices in their network. The customer has a specific request to understand how the WL1837MOD based Wi-Fi module can fit in their existing network config. Below is the information about the customer site:
Their wireless controllers are Cisco flexconnect and their access points run in Flex Connect mode. All the traffic is locally switched out the local access point vs sending out from a centralized controller. They can't enable multicast or broadcast per AP as it's problematic. Our server sits in a different VLAN segment, that means they have to allow multicast / broadcast between segments which can cause storm issues when running in router on a stick mode.
Part Number:CC3220MODA
Hello everyone! After successful software development and testing on CC3220SF Launchpad, we are ready to test in on "bare" MCU. We have chosen CC3220MODASF. As programmer, we use XDS110 Debug Probe's AUX ports for UART.. We followed typical connection scheme from data sheet. Here's how it all is connected:
As mentioned in this post GPIO01 and GPIO02 are UART0 TX and RX. Uniflash session is started with following params:
When I try to read memory, green mark appears close to "Cortex_M4_0". And it stucks on Loading. When I click "Erase flash" I have the following output:
[7/16/2018, 4:26:17 PM] [INFO] Cortex_M4_0: GEL Output: Memory Map Initialization Complete [7/16/2018, 4:26:17 PM] [ERROR] IcePick_C: Error connecting to the target: (Error -267 @ 0x0) The controller could not detect valid target supply. Check target JTAG connection and/or connection setting specifying voltage level. (Emulation package 8.0.27.9)
It would be great for TI to publish some guide describing MCU programming and flashing. Any help would be appreciated.