I tried to change the chirp idle time & frame duration of configuration in lab0003_occupancy_detection, but What was detected in the previous configuration was not detected after the change.

Does the idle time of Chirp & duration of frame affect the value of fft or hitmap ?

Existing configuration

profileCfg 0 77 250 10 40 0 0 98 1 64 2200 0 0 40

frameCfg 0 3 128 0 160 1 0

Changed configurationprofileCfg

profileCfg 0 77 110 10 40 0 0 98 1 64 2200 0 0 40

frameCfg 0 3 128 0 80 1 0

. SDK Version : sdk_02_00_00_04

Tool Box Version : mmwave_automotive_toolbox_2_4_7.

Regards

↧

TPS65084: TPS65084 for intel platform

May 22, 2019, 9:16 pm

≫ Next: TXS0104E-Q1: TXS0104 Compare to TXB0104

≪ Previous: RTOS/AWR1642BOOST: Problems due to change of idle time of Chirp

Part Number:TPS65084

Hi Sir,

Our customer old product used the TPS659842 PMIC on Braswell,

But Intel have document show the "Power delivery on board discrete VRMs. PMIC not supported",

As I know CPU PN N3060 & N3160 & N3710 & E8000 use TPS659842 fail rate over 5% for power on sequence.

Does TPS650842 have new version for this CPU? or How can I to help customer to fixed this issue?

Hugo

↧

TXS0104E-Q1: TXS0104 Compare to TXB0104

May 22, 2019, 9:20 pm

≫ Next: TCA5013: TCA5013 connect fail issue

≪ Previous: TPS65084: TPS65084 for intel platform

Part Number:TXS0104E-Q1

Dear Team,

This thread is to re-open below thread:

How do I know TXS0104-Q1 have larger capacitive load than TXB0104-Q1? Which chapter have description?

TXS0104-Q1 Layout guideline descript that the layout trace must keep short.

But we must connect the EMP device with long wire. Are there any problem?

Please kindly provide your suggestion.

Kevin

↧

TCA5013: TCA5013 connect fail issue

May 22, 2019, 9:21 pm

≫ Next: BQ25890: Using Bi-directional battery switch as discharged FET

≪ Previous: TXS0104E-Q1: TXS0104 Compare to TXB0104

Part Number:TCA5013

Dear All:

TCA5013 can not communication

TCA5013 VDDI/VDD 3.3V OK

I2C OK

sam1_vcc sam1_io3.3v OK

rest no

clk no output

the register values:(Please visit the site to view this file)

↧

BQ25890: Using Bi-directional battery switch as discharged FET

May 22, 2019, 9:25 pm

≫ Next: MSP432E401Y: Azure mqtt client example code can't get NTP time

≪ Previous: TCA5013: TCA5013 connect fail issue

Part Number:BQ25890

Hello all,

In my recent projects, I used the BQ24266 Li-Ion battery charger. this IC contains a BGATE pin which allows me to control an external FET for a low resistance path for the battery discharged current.

In my next project, I plan to use a different charger (BQ25890) which unfortunately doesn't support the BGATE feature.

I was thinking about adding an external battery switch (Vishay SiP32101) as a discharged FET, and control it by using the BQ25890 REGN pin to control the On/Off states of the switch.

The switch is active low, which means that the switch will be on when I disconnect the 5V charging cable, and off when I connect it back again:

Is this a good way to implement the solution, or does someone think that for some reason it will not work well?

Thank you all :)

Nir

↧

MSP432E401Y: Azure mqtt client example code can't get NTP time

May 22, 2019, 9:26 pm

≫ Next: TPSM84203: Question about the inductor on this module

≪ Previous: BQ25890: Using Bi-directional battery switch as discharged FET

Part Number:MSP432E401Y

Hi Team,

Customer is using MSP432E401Y in UPS communication card, but have some issue when run the Azure mqtt client example code. Could you give some comments? Thanks.

1. Customer is using Azure mqtt client example code, what they modified is only the ntp server ( change from NULL to their own ntp server ), but the example can't get ntp time. The CCS console output is as below.

[CORTEX_M4_0] Service Status: DHCPC    : Enabled :          : 000
Service Status: DHCPC    : Enabled : Running : 000
Starting the iohub_client_sample_mqtt example
Network Added: If-1:172.18.140.86
Service Status: DHCPC    : Enabled : Running : 017
startSNTP: couldn't get time (-100), will retry in 15 secs ...
startSNTP: retrying ...
startSNTP: couldn't get time (-100), will retry in 15 secs ...
startSNTP: retrying ...
startSNTP: couldn't get time (-100), will retry in 15 secs ...
startSNTP: retrying ...
startSNTP: couldn't get time (-100), will retry in 15 secs ...
startSNTP: retrying ...
startSNTP: couldn't get time (-100), will retry in 15 secs ...

Notes that they checked the ntp server works well with their old network card, and also checked it works OK with following command line.

2. Based on Azure mqtt client example, they modified the code from ethernet connection to wifi connection (MSP432E401 + CC3120mod plugin in AP mode).

They find there is no issue with ntp server connection, and they saw good messages “IoTHubClient_LL_SendEventAsync accepted message [x] for transmission to IoT Hub.” But after about 3 minutes, ndk report server alert “Service Status: DHCPC : Enabled : Fault : 002”. And they do not see good values from their Azure cloud.

[CORTEX_M4_0] Template object created successfully. 


create dataJsonObjHandle
Error: -101  , Couldn't create json object 

Template object created successfully. 


create logJsonObjHandle
Json object created successfully. 


Template object created successfully. 


create identJsonObjHandle
Json object created successfully. 


Template object created successfully. 


create devInfoJsonObjHandle
Json object created successfully. 


Service Status: DHCPC    : Enabled  :          : 000
Service Status: DHCPC    : Enabled  : Running  : 000
Starting the iohub_client_sample_mqtt example
initWiFi
before sl_Start
sl_Start mode=0
sl_Start OK mode=0
sl_WlanPolicySet OK response=0
sl_NetCfgSet response=0
setStationMode
wlanConnect=126777
deviceConnected=0, ipAcquired=0
deviceConnected=0, ipAcquired=0
deviceConnected=0, ipAcquired=0
deviceConnected=1, ipAcquired=0
deviceConnected=1, ipAcquired=0
deviceConnected=1, ipAcquired=0
deviceConnected=1, ipAcquired=0
deviceConnected=1, ipAcquired=1
Current time: Tue May 21 12:34:18 2019

CC32XX has connected to AP and acquired an IP address.
IP Address: 172.20.10.8
IoTHubClient_LL_SetMessageCallback...successful.
msgText = {"realtimes":[{"c":"590","t":1558442058,"v":"0101"},{"c":"260","t":1558442058,"v":"4321"}]}
IoTHubClient_LL_SendEventAsync accepted message [0] for transmission to IoT Hub.
msgText = {"realtimes":[{"c":"590","t":1558442062,"v":"0101"},{"c":"260","t":1558442062,"v":"4321"}]}
IoTHubClient_LL_SendEventAsync accepted message [1] for transmission to IoT Hub.
msgText = {"realtimes":[{"c":"590","t":1558442066,"v":"0101"},{"c":"260","t":1558442066,"v":"4321"}]}
IoTHubClient_LL_SendEventAsync accepted message [2] for transmission to IoT Hub.
msgText = {"realtimes":[{"c":"590","t":1558442069,"v":"0101"},{"c":"260","t":1558442069,"v":"4321"}]}
IoTHubClient_LL_SendEventAsync accepted message [3] for transmission to IoT Hub.
msgText = {"realtimes":[{"c":"590","t":1558442073,"v":"0101"},{"c":"260","t":1558442073,"v":"4321"}]}
IoTHubClient_LL_SendEventAsync accepted message [4] for transmission to IoT Hub.
Service Status: DHCPC    : Enabled  : Fault    : 002

↧

TPSM84203: Question about the inductor on this module

May 22, 2019, 9:40 pm

≫ Next: TDC1000-TDC7200EVM: set msp430 bsl entry failed

≪ Previous: MSP432E401Y: Azure mqtt client example code can't get NTP time

Part Number:TPSM84203

Hi,

Looking at the picture that I can see on TPSM84203 product folder, it seems using open magnetic inductor.

Is there any problem with it?

Sincerely,

↧

TDC1000-TDC7200EVM: set msp430 bsl entry failed

May 22, 2019, 9:41 pm

≫ Next: CC2640R2F-Q1: VOH(MIN), VOL(MAX), VIH(MIN), VIL(MAX) Values for supply voltage 3.3V

≪ Previous: TPSM84203: Question about the inductor on this module

Part Number:TDC1000-TDC7200EVM

I am trying to update the firmware as noted on pg 24 of the user guide. After pressing update firmware and selecting okay when prompted to update MSP430 nothing happens. Step 3 does not occur “The MSP430 USB Firmware Upgrade windows pops up. Click Next to proceed on the first prompt; read and accept the license agreement and click Next to continue.”.

The bottom of the GUI states. “set msp430 bsl entry failed”. What might I do?

↧

CC2640R2F-Q1: VOH(MIN), VOL(MAX), VIH(MIN), VIL(MAX) Values for supply voltage 3.3V

May 22, 2019, 9:49 pm

≫ Next: TPS548B22: Question about RSP and VOSNS Relationship

≪ Previous: TDC1000-TDC7200EVM: set msp430 bsl entry failed

Part Number:CC2640R2F-Q1

Hello,

Kindly share details of VOH(MIN), VOL(MAX), VIH(MIN), VIL(MAX) Values for supply voltage 3.3V for CC2640R2FTWRGZRQ1

Regards,

Grace

↧

TPS548B22: Question about RSP and VOSNS Relationship

May 22, 2019, 9:50 pm

≫ Next: CCS/MSP432E401Y: unable to import msp projet to workspace

≪ Previous: CC2640R2F-Q1: VOH(MIN), VOL(MAX), VIH(MIN), VIL(MAX) Values for supply voltage 3.3V

Part Number:TPS548B22

Hi Team,

Recently, we built a board using the TPS548B22 as a regulator to take a 12V supply down to 1.1V. In a recent revision, we attempted to move the RSP line to the load location rather than directly after the output of the TPS548B22. During this update, we neglected to move the VOSNS line, which is still shorted to the output of the regulator. Between the TPS548B22 output and our load, we have a current shunt monitor (INA250A1) to sense the current on the supply rail, so RSP is connected after the shunt monitor output, while VOSNS remains between the regulator output and current shunt monitor input.

We are currently observing that the 1.1V regulator output does not come up unless we blue-wire to short RSP and VOSNS together at the output of the regulator so that they share the V1P1 net, rather than RSP connecting to V1P1_0 (after current shunt monitor) and VOSNS connecting to V1P1 (before current shunt monitor). Is there a mechanism in the TPS548B22 that could be preventing the 1.1V regulator output in this configuration? The current shunt monitor should only be presenting approximately 0.1-Ohm resistance, i.e. virtually the same voltage.

Any thoughts or explanation about the behavior we're seeing would be helpful as we debug!

Thanks,

Michael

↧

CCS/MSP432E401Y: unable to import msp projet to workspace

May 22, 2019, 9:50 pm

≫ Next: CCS/LAUNCHXL-CC1352R1: Code Composer Studio™ forum

≪ Previous: TPS548B22: Question about RSP and VOSNS Relationship

Part Number:MSP432E401Y

Tool/software: Code Composer Studio

hi,

am not able to import simplelink MSP432 SDK watson IoT plugin

am getting error as

See details below...
watson_mqttclient_MSP_EXP432E401Y_tirtos_ccs
Project-spec import cannot be resolved: ${COM_TI_SIMPLELINK_MSP432E4_SDK_INSTALL_DIR}/kernel/tirtos/builds/MSP_EXP432E401Y/release/ccs/tirtos_builds_MSP_EXP432E401Y_release_ccs.projectspec!

how can i import and use that project

↧

CCS/LAUNCHXL-CC1352R1: Code Composer Studio™ forum

May 22, 2019, 9:50 pm

≫ Next: OPT3002: I2C standard mode timing requirement

≪ Previous: CCS/MSP432E401Y: unable to import msp projet to workspace

Part Number:LAUNCHXL-CC1352R1

Tool/software: Code Composer Studio

1. The LauchXL boards (two of them) worked fine out of the box: I was able to test the Bluetooth Project Zero by connecting to the board form my Androind phone, as described in the page (Out of the Box Experiemce):

http://dev.ti.com/tirex/explore/node?node=ADuSIrFg2kUHlTd9Kp0MqQ__pTTHBmu__LATEST

2. Then I wanted to try out the Zigbee Project Zero described in the page. I used Unifash to clear existing firmware on two boards and loaded the coordinator and end device firmware.

http://dev.ti.com/tirex/explore/node?node=AIHpFUnGAZPCyIyMVNwlJA__pTTHBmu__LATEST

3. However, I ran into trouble connecting to either board using putty. So I tried to restore the firmware to factory setting (using the right button and the reset button). I also tried to flash the hex file of the ble5stack projectzero from

C:\ti\simplelink_cc13x2_26x2_sdk_3_10_00_53\source\ti\ble5stack\hexfiles\cc13x2r1\ble5_project_zero_cc13x2p2lp_app_FlashROM_Release_unsecure.hex.

4. But the Android app does not seem to recognize the launchpads as BLE devices. My suspicion is that the firmware erase step in the Zigbee Project Zero 9( Step 0) instructions may have erased ket firmware sectors that should not have been erased.

How do I set the boards to their factory setting so that the Bluetooth Out of the Box ProjectZero works?

Thanks,

Siva

↧

Latest Images