Part Number:SN65HVD231
Hi Sir
I saw SN65HVD231 have Vref pin ,but TI the latest TCAN33x series this pin is NC not VREF
May I know the reason? Can TCAN33x replace SN65HVD231 directly ?
Thanks
Part Number:SN65HVD231
Hi Sir
I saw SN65HVD231 have Vref pin ,but TI the latest TCAN33x series this pin is NC not VREF
May I know the reason? Can TCAN33x replace SN65HVD231 directly ?
Thanks
Part Number:TPS2557
Dear Team,
I have two question regarding "ton" below.
Q1.
"ton" turn on delay time is defined as max 9ms according to the datasheet page 6.
I can find ton is around 3.8ms at Figure 1 in datasheet page 7.
Could you let me know the reason why "ton" needs such a long term.
Q2.
When EN goes to Low just during ton term after set EN from Low to High, does TPS2557 turn on SW or keep to turn off?
Best Regards,
Hirokazu Takahash
Part Number:CC2564C
Tool/software: Linux
hi,
we want to estimate our product maximum connection distance when Bluetooth receiving power is -70 dbm(sensitivity level), but in system report is a RSSI value. how can i transform RSSI value to a real power(dbm)? we measure it at a place without any other BT or WiFi interference.
best,
kevin
Part Number:LM5117
Hi expert,
Customer is using our LM5117 in their infotainment application. Condition is 11V/9.5V/6.5V to 5V/12A. They want to tie VCC to Vin with a low pass filter to increase efficiency. Would you kindly help to verify if we can connect external VCC source to VIN? Thanks!
Best regards,
Ann Lien
Part Number:CC2640R2F
Tool/software: TI-RTOS
I started with SDK 1.40 and later I moved to 1.50. But if I try to compile my project with 2.20 and later I need to substitute
const RFCC26XX_HWAttrsV2 RFCC26XX_hwAttrs = { .hwiPriority = ~0, // Lowest HWI priority .swiPriority = 0, // Lowest SWI priority .xoscHfAlwaysNeeded = true, // Keep XOSC dependency while in standby .globalCallback = NULL, // No board specific callback .globalEventMask = 0 // No events subscribed to };
with
const RFCC26XX_HWAttrsV2 RFCC26XX_hwAttrs = {
.hwiPriority = ~0, // Lowest HWI priority
.swiPriority = 0, // Lowest SWI priority
.xoscHfAlwaysNeeded = true, // Keep XOSC dependency while in standby
.globalCallback = NULL, // No board specific callback
.globalEventMask = 0 // No events subscribed to
};
The compilation is successful but it doesn't work. First call events = (tasksArr[idx])( idx, events ); in osal.c leads to "hard fault" HWI.
How can I debug it? Can I get the sources of ble stack?
Part Number:AM3352
Tool/software: Linux
We want to containerize network boot for beaglebone black based custom board,
So basically we want to start dhcp server, nfs-kernel-server and tftp server on container and attach it to one of the interface on the ubuntu PC. ( Eventually want to make it work on Windows)
I wrote dockerfile with dhcp, nfs-kernel-server, tftpd-hpa and supervisord, all the files are available in below github link,
https://github.com/AnkurTank/bbb_dockerfile_networkboot
I built it using following command
docker build -f networkboot.dockerfile -t bbb_networkboot
When I run it using following command
docker run -it --net host --privileged bbb_networkboot
I see following errors and dhcp, nfs doesn't start.
sh-4.3# 2019-03-26 13:34:31,574 CRIT Supervisor running as root (no user in config file) 2019-03-26 13:34:31,576 INFO supervisord started with pid 8 2019-03-26 13:34:32,579 INFO spawned: 'isc-dhcp-server' with pid 12 2019-03-26 13:34:32,581 INFO spawned: 'nfs-kernel-server' with pid 13 2019-03-26 13:34:32,583 INFO spawned: 'rpcbind' with pid 14 2019-03-26 13:34:32,585 INFO spawned: 'xinetd' with pid 15 2019-03-26 13:34:32,587 INFO spawned: 'tftpd-hpa' with pid 17 2019-03-26 13:34:32,665 INFO exited: rpcbind (exit status 0; not expected) 2019-03-26 13:34:32,709 INFO exited: xinetd (exit status 0; not expected) 2019-03-26 13:34:32,741 INFO exited: tftpd-hpa (exit status 0; not expected) 2019-03-26 13:34:32,747 INFO exited: isc-dhcp-server (exit status 1; not expected) 2019-03-26 13:34:32,846 INFO exited: nfs-kernel-server (exit status 0; not expected) 2019-03-26 13:34:33,849 INFO spawned: 'isc-dhcp-server' with pid 82 2019-03-26 13:34:33,851 INFO spawned: 'nfs-kernel-server' with pid 83 2019-03-26 13:34:33,853 INFO spawned: 'rpcbind' with pid 84 2019-03-26 13:34:33,855 INFO spawned: 'xinetd' with pid 85 2019-03-26 13:34:33,857 INFO spawned: 'tftpd-hpa' with pid 86 2019-03-26 13:34:33,863 INFO exited: rpcbind (exit status 1; not expected) 2019-03-26 13:34:33,899 INFO exited: isc-dhcp-server (exit status 1; not expected) 2019-03-26 13:34:33,907 INFO exited: tftpd-hpa (exit status 0; not expected) 2019-03-26 13:34:33,917 INFO exited: xinetd (exit status 0; not expected) 2019-03-26 13:34:33,946 INFO exited: nfs-kernel-server (exit status 0; not expected) 2019-03-26 13:34:35,950 INFO spawned: 'isc-dhcp-server' with pid 145 2019-03-26 13:34:35,952 INFO spawned: 'nfs-kernel-server' with pid 146 2019-03-26 13:34:35,954 INFO spawned: 'rpcbind' with pid 147 2019-03-26 13:34:35,957 INFO spawned: 'xinetd' with pid 148 2019-03-26 13:34:35,959 INFO spawned: 'tftpd-hpa' with pid 149 2019-03-26 13:34:35,966 INFO exited: rpcbind (exit status 1; not expected) 2019-03-26 13:34:36,003 INFO exited: isc-dhcp-server (exit status 1; not expected) 2019-03-26 13:34:36,009 INFO exited: tftpd-hpa (exit status 0; not expected) 2019-03-26 13:34:36,019 INFO exited: xinetd (exit status 0; not expected) 2019-03-26 13:34:36,046 INFO exited: nfs-kernel-server (exit status 0; not expected) 2019-03-26 13:34:39,052 INFO spawned: 'isc-dhcp-server' with pid 208 2019-03-26 13:34:39,054 INFO spawned: 'nfs-kernel-server' with pid 209 2019-03-26 13:34:39,056 INFO spawned: 'rpcbind' with pid 210 2019-03-26 13:34:39,058 INFO spawned: 'xinetd' with pid 211 2019-03-26 13:34:39,061 INFO spawned: 'tftpd-hpa' with pid 212 2019-03-26 13:34:39,071 INFO exited: rpcbind (exit status 1; not expected) 2019-03-26 13:34:39,097 INFO gave up: rpcbind entered FATAL state, too many start retries too quickly 2019-03-26 13:34:39,098 INFO exited: isc-dhcp-server (exit status 1; not expected) 2019-03-26 13:34:39,099 INFO gave up: isc-dhcp-server entered FATAL state, too many start retries too quickly 2019-03-26 13:34:39,111 INFO exited: tftpd-hpa (exit status 0; not expected) 2019-03-26 13:34:39,119 INFO gave up: tftpd-hpa entered FATAL state, too many start retries too quickly 2019-03-26 13:34:39,120 INFO exited: xinetd (exit status 0; not expected) 2019-03-26 13:34:39,151 INFO gave up: xinetd entered FATAL state, too many start retries too quickly 2019-03-26 13:34:39,151 INFO exited: nfs-kernel-server (exit status 0; not expected) 2019-03-26 13:34:40,152 INFO gave up: nfs-kernel-server entered FATAL state, too many start retries too quickly
Any suggestion/pointers to this problem.
I have posted this question on docker forum at below link as well, however I have used e2e forum more and may be someone already did it for beaglebone black what I am trying to do so asking it here.
https://forums.docker.com/t/setting-up-network-boot-in-docker-container/71937
Thanks in advance!
Part Number:HD3SS6126
Hi Team,
Customer uses HD3SS6126 and switch SW2 SS_SEL and SW3 HS_SEL at the same time.
the NB and PC will not recognize the USB device.
Can you please provide your comment? I saw HD3SS6126 pin 3 is NC, how do we recommend customer to config SW3?
Here are customer experiment setup pictures and the USB viewer.
(Please visit the site to view this file)
BR,
SHH
Part Number:CC2642R
Tool/software: TI-RTOS
Hi TI BLE team,
We are checking the power consumption on FOB(peripheral device) with the below conditions.
By the way, there are no big differences between different slave latencies.
I confirmed that the response status of connection parameter update request. You can see the log data through attached log data and pictures below.
Current SW is based on TI SDK simplelink_cc26x2_sdk_2_20_00_36.
even though two devices are in a connection state, I thought that the power consumption should be different according to the slave latency.
If any, let me know.
KeyFob 1 | KeyFob 2 | ||||||||||||||||
Keyfob | No connection state | Consumption | Latency | Consumption | Latency | ||||||||||||
Scan Interval | Scan Window | Max Connected Device | PDU | Adv Interval | Con Interval | PHYs | PHY chosen | PDU | Slave Latency | Adv Report triggerred | Adv Report triggerred | ||||||
60 | 30 | 1 | Max | 30 | 100 | 1M | 1M | Max | 0 | 0.93mA | 0.94mA | ||||||
60 | 30 | 1 | Max | 100 | 100 | 1M | 1M | Max | 0 | 0.60mA | 0.59mA | ||||||
60 | 30 | 1 | Max | 500 | 100 | 1M | 1M | Max | 0 | 0.41mA | 0.42mA | ||||||
60 | 30 | 1 | Max | 1000 | 100 | 1M | 1M | Max | 0 | 0.41mA | 0.42mA | ||||||
60 | 30 | 1 | Max | 1500 | 100 | 1M | 1M | Max | 0 | 0.41mA | 0.42mA | ||||||
60 | 30 | 1 | Max | 2000 | 100 | 1M | 1M | Max | 0 | 0.41mA | 0.42mA | ||||||
Keyfob | Connection state | Consumption | Latency | Consumption | Latency | ||||||||||||
Scan Interval | Scan Window | Max Connected Device | PDU | Adv Interval | Con Interval | PHYs | PHY chosen | PDU | Slave Latency | Adv + Conn Triggerred | Adv + Conn Triggerred | ||||||
60 | 30 | 1 | Max | 30 | 7.5 | 1M | 1M | Max | 0 | 1.73mA | 1.204s | 1.72mA | 1.108s | ||||
60 | 30 | 1 | Max | 30 | 30 | 1M | 1M | Max | 0 | 0.50mA | 1.200s | 0.50mA | 1.104s | ||||
60 | 30 | 1 | Max | 30 | 100 | 1M | 1M | Max | 5 | 0.09mA | 1.196s | 0.09mA | 1.116s | ||||
60 | 30 | 1 | Max | 30 | 100 | 1M | 1M | Max | 10 | 0.08mA | 1.196s | 0.09mA | 1.116s | ||||
60 | 30 | 1 | Max | 30 | 100 | 1M | 1M | Max | 20 | 0.08mA | 1.192s | 0.09mA | 1.276s | ||||
60 | 30 | 1 | Max | 30 | 100 | 1M | 1M | Max | 50 | 0.08mA | 1.200s | 0.09mA | 1.280s |
Through analyzer, we can confirm that the slave latency operation works.
With kind regards,(Please visit the site to view this file)
Ji Won Lee
Part Number:TMS320F28069
Tool/software: Code Composer Studio
Hi there,
I came across a problem when using F28069. I connected this mcu to an external ADC chip ADS131A04 through spia. ADS131A04 indicates the ADC is done and triggers XINT2 in F28069 to retrieve data. However, during usage, sometimes the default isr ADCINT1_ISR was triggered, and I cannot find any reason. The register PieCtrlRegs.PIEIER1.bit.INTx1 = 0 and PieCtrlRegs.PIEIER10.bit.INTx1 = 0. Does anyone come across similar problem?
Thanks in advance!
Dan
Part Number:LM2662
To obtain the lowest ripple noise, is it better to use a ceramic MLCC capacitor or polymer capacitor ? Ceramics are generally recommended for their low ESR but I see polymers available with 5 mOhm at 100 kHz. Polymers are available in higher capacitance than ceramics (hundreds of uF), in relatively small size and are claimed to not vary their capacitance with voltage (although X5R also have low capacitance variation with voltage). I will operate at -5V, 150 kHz, less than 50 mA.
Steve
Part Number:LM48580
Hi Team
my customer does have a capacitive based buzzer driver (charge pump) what boosts up the 3.3 V input voltage up to ~ 10 V
Now they looking for ways to increase the tone volume oft the buzzer. One approach would be LM48580. If they could generate 15 V instead of 10 V they assume this would work out for them. Besides the tone voulume size is a very critical factor. therefor the solution size needs to be as small as possible
Ist the LM48580 able to work properley with following induktors:
Kind regards
Dierk Bronner
Part Number:BQ30Z554-R1
Hi,
Can someone tell me exactly the commands required to write/receive to the gauge in order to unseal it, because the steps listed in the technical reference do not unseal the device. Also, someone here said that unseal code for these devices would be 0x0414, 0x3672. How will be used or where should they be written in order to unseal the device?
Thank you,
Ciprian
Part Number:BOOSTXL-BUCKCONV
Hello,
I'm interested in using the Buck Converter control code with the newer processor F280049C. I understand TI will release the code for the kit later in 2019, is that correct?
Will that code still use assembly code in the ISR, or anywhere in the control code? Our goal is to have code that is easily maintained, so strongly prefer C.
Thank you.
Part Number:CC2652R
Tool/software: TI-RTOS
I have been modify BIM to implements support 512KB flash,I have do test with LED_DEBUG and green LED blink indicate spi flash work well.
Why read the "header" from newest spi flash chip first perform OTA? the spi flash is empty with new chips.
It looks like first need write full firmware to external spi flash?
if(flash_open() != 0) { //Search for a metadata header to fit the Zigbee image ExtImageInfo_t oad_imgHdrFactoryNew; //OAD binary pages required to store the binary uint8 binaryPagesLen = 0; // Read the factory new metadata page readFlash(EFL_ADDR_META_FACT_IMG, (uint8_t *)&oad_imgHdrFactoryNew, EFL_METADATA_LEN); //is a valid header if(memcmp(&oad_imgHdrFactoryNew.fixedHdr.imgID, oad_externalFLashID, sizeof(oad_externalFLashID)) != 0) { flash_close();
//this section return ABORT if perform OTA procedure //This release does not support not having the Factory New image return ZCL_STATUS_ABORT; }
Part Number:MSP430FR5972
Tool/software: Code Composer Studio
Hi !
I'm start Update my CCS 9.0
I read:
...
Some sites could not be found. See the error log for more detail.
No repository found at software-dl.ti.com/.../auto.
Unable to read repository at software-dl.ti.com/.../ccs6.0.
software-dl.ti.com/.../ccs6.0 is not a valid repository location.
No repository found at
...
Hi Team,
Do we have alt.s solution to replace EJ179?
EJ179 is doing power sink role only and it can support two PDO.
PDO0: 5V
PDO1: 5.5V.
BR,
SHH
Part Number:CC1310
Hi,
I am using the LaunchPad 1390 in my system and am running into an issue with TX power.
I am sending a packet at a specific time and then immediately going into RX mode. Here is
the code:
RF_EventMask xmitRecvPacketExactTime(uint8_t *txPkt, uint32_t pktLen, uint32_t xmitTimeRatTicks, uint8_t *rxPkt, uint8_t *recvPktLen, uint32_t recvTimeoutRatTicks) { uint32_t copyIdx; setTxDefaults(); setRxDefaults(); RF_cmdPropTx.startTrigger.triggerType = TRIG_ABSTIME; RF_cmdPropTx.startTime = xmitTimeRatTicks; RF_cmdPropTx.pktLen = pktLen; RF_cmdPropTx.pPkt = txPkt; RF_cmdPropTx.pNextOp = (rfc_radioOp_t *)&RF_cmdPropRx; // set next op which will be receive. RF_cmdPropTx.condition.rule = COND_STOP_ON_FALSE; RF_cmdPropRx.endTrigger.triggerType = TRIG_REL_PREVEND; // tmo occurs relative to cmd submit time RF_cmdPropRx.endTime = recvTimeoutRatTicks; *recvPktLen = 0; flushRxQueue(); bRxSuccess = false; updateStatsIncCounter(&(getStats()->packetsTransmitted)); paEnable(true); hgmEnable(true); lnaEnable(true); RF_EventMask terminationReason = RF_runCmd(rfHandle, (RF_Op*)&RF_cmdPropTx, RF_PriorityNormal, radioRxCallback, (RF_EventCmdDone | RF_EventRxEntryDone | RF_EventLastCmdDone)); paEnable(false); hgmEnable(false); lnaEnable(false);
I have been assuming that since I am performing both a transmit and a receive operation that both paEnable and lnaEnable (both going to the 1190 amplifier) need to be asserted.
What I see, though, is if lnaEnable is asserted, the TX power is reduced and the remote receiving device sees an RSSI of -70 whereas without the lnaEnable
asserted the receiving end sees and RSSI of -20. Somehow the lna control line is affecting the TX power. I need to have the lnaEnable asserted during receive
to get maximum receive performance when the remote device is a long distance away.
Any ideas what might be happening?
Victor
Part Number:TMS320F28379D
Tool/software: Code Composer Studio
I am trying to use the sd_card_cpu01 for f28379d control card. I can see the "SD Card Example Program" message on the UART console but when I type "help" on the uart, nothing is displayed on the screen. When I went in debug mode, the code is stuck at UARTCharGet function. It is waiting for character in the UART buffer. When I press a key on the UART console, I can see LED light on the control card which confirms that the character is being sent to the DSP. Please let me know how can I make this code running.
Thanks,
Prateek