Quantcast
Channel: Forums - Recent Threads
Viewing all 262198 articles
Browse latest View live

AM3352: Failure rate

$
0
0

Part Number:AM3352

Hello,

We have two controller boards which is using "AM3352BZCZ80". Below is what we received from UL today Can you help provide the necessary information on failure rate or where can I find it?

"Since The Cortex A8 chips exceeds the requirements for the temp test - the junction temp is 90deg C and we measured 70 degC.(higher than 50%) - please provide calculations per MIL-STD-883E or equivalent such that a failure rate is equal to or less than 0.5 failures per million hours of operation."

Thanks,

Hemal


LP3985: LP3985-2.5 output at 3.3V (no load) on two boards.

$
0
0

Part Number:LP3985

Hi,

I am debugging a new design that uses the LP3985-2.5 to power a FPGA.  The same FPGA also has banks running on 3.3V.  I have a series 0 ohm resistor between the regulator and FPGA so I can disconnect the FPGA load leaving only the output capacitor.  There is 10 uF in parallel with 47 uF on the input of the LP and 10 uF on its output.  There's a 10 nF between bypass and ground.  I have two prototype boards.  Originally there appeared to be a short between 3.3V and 2.5V (under the FPGA, of course).  I removed and replaced the FPGA and the short is gone but I am using the same LP3985-2.5.  With its output now disconnected from the FPGA but still connected to its output capacitor, the LP input measures 3.359V and its output measures 3.216V.  I have a second board whose LP3985 output was originally attached to the FPGA and measured 3.3V, so i removed its zero ohm jumper.  Disconnected from its load the second board's LP3985-2.5 measures 3.24V with its input measuring 3.28.

So it is possible on the first board, the LP's output was being dragged above it's nominal 2.5V output value.  From the simplified block diagram, this wouldn't appear to damage the LP since it cannot sink current if the output is pulled above its regulation value.  On the second board, however, there is (and was never) a short, so it is difficult to explain how it is no longer regulating.  I have attached the schematic sheet.

Any thoughts are most appreciated.

Thanks,

Scott

AWR1243BOOST: MSB First vs LSB First Radar Post Proc

$
0
0

Part Number:AWR1243BOOST

Hello, 

I am using the AWR1243BOOST + MMWAVE DEVPACK + TSW1400 for data capture. I am using IF loopback to get some test data. 

If I use MSB first, and then analyze the data with my matlab scripts, I get the expected output. Following the guidelines, 2's complement value = HSDC Pro - 2^15.

However, when I use the LSB first settings, I do expect that there is something else that needs to be corrected for. The Radar Studio Post Proc tool seems to take that into account because the output matches the MSB first. Can you please let me know what are correction factors to use when in LSB first versus MSB first. 

Regards,

RJ 

SM73201-ARC-EV: SM73201-ARC-EV (RD-195) 3.3v circuitry short problem

$
0
0

Part Number:SM73201-ARC-EV

I am using SM73201-ARC-EV Board. 

When turned it on for the first time I set current limit on +6 Volts power supply to around (0.5 Amps) It worked fine as stated in the document I could see the status from the LEDs.

In the second attempt current limit of the supply was gradually reduced to 0 for some reason during which LEDs flickered and it stopped working.

Its in the 3.3v circuitry after removing LDO resistance between 3.3v and GND has dropped to 11 ohms.

I am not much of a Hardware person. Can you please help me figure out what could have gone wrong.

Thanks

BQ34Z653: bqEVSW download links

$
0
0

Part Number:BQ34Z653

Hello,

Could someone please post the download link(s) for the bqEVSW. I've been trying to program the BQ34Z653 using bqEVSW ver. 0.9.87, but I cannot read the Fuel Gauge percentage, and other details. Also, is there a fix for the flashing LEDs? I noticed in another post that people were having issues with it.

My current configuration is 4S2P.

Thanks

TPA3251: How to minimize Start-up Time on TPA3251

$
0
0

Part Number:TPA3251

Hi team,

I ahve a customer that is using the TPA3251 and is seeing start up times of 350ms.  Are there any tricks to help reduce the delay between power up and the power stage to start switching?

Thanks for your consideration!

EZ430-CHRONOS: Device driver installation failed

$
0
0

Part Number:EZ430-CHRONOS

I have received my eZ430-Chronos today and I followed the directions on the box (I installed chronos-setup.exe from the TI wiki), however when installing the drivers I received the error that the (usbser) Ports install failed. My RF Access Point isn't recognized when plugged in now.

TSW1405EVM: Raw data capture from AWR1642 without mmWave DevPack


CCS/MSP430F2418: MSP430F2418TPM c programmer guide

$
0
0

Part Number:MSP430F2418

Tool/software: Code Composer Studio

Hi,

I am trying to find a c programmer user guide  for the MSP430F2418TPM. 

 

Thanks,

John Hite

Dallas, TX

Former TI'er badge # 152301

TPS563219A: Output Current Limit

$
0
0

Part Number:TPS563219A

Hello,

Can someone better explain to me how the output current is calculated?

Is it all based on the inductor we pick?

Regards,

David

WEBENCH-POWER-DESIGNER: test - will delete

BOOSTXL-CC2650MA: msp432p01r: project zero. 32 bits

$
0
0

Part Number:BOOSTXL-CC2650MA

Hi!

I'm currently modifying project zero for led service. can we take 32 bits number as input instead of hex or 0x00 and 0x01?

Thanks,

Janna Razali

CCS/TDC7201-ZAX-EVM: TDC720x-ZAX-EVM having issues with both the GUI and the CCS code

$
0
0

Part Number:TDC7201-ZAX-EVM

Tool/software: Code Composer Studio

I am using a TDC720x-ZAX-EVM to determine if this is the correct TOF microchip and I am running into some issues with the evaluation module. I was able to get excellent readings on the GUI with a function generator, and then began to experiment using the code composer code that was supplied by TI in the demo_apps folder, and was unsuccessful in getting anything to work and the only thing that happened was LED102 and LED101 would light up and stay lit. I decided to plug the TDC720x-ZAX-EVM back into the function wave generator and test TDC1 again, and even though my setup had not changed, TDC1 was no longer reading any measurements. I tried the same setup with TDC2 and was able to read measurements with no problem. I altered the code to use TDC2 instead of TDC1 and then attempted to do measurements through the GUI and noted that TDC2 was no longer taking any measurements. Has anyone ran into this problem before and found a fix? 

Here is the TI code I was using. 

//******************************************************************************
//  Demo Application01 for MSP430/TDC720x Interface Code Library v1.0
//  Byte Read/ Byte Write TDC720x Registers
//
//                MSP430F5529
//             -----------------
//         /|\|              XIN|-
//          | |                 |  
//          --|RST          XOUT|-
//            |                 |
//            |    P3.0/UCB0SIMO|--> SDI 
//            |    P3.1/UCB0SOMI|<-- SDO 
//            |     P3.2/UCB0CLK|--> CLK 
//            |             P2.6|--> CSB 
//            |             P2.4| 
//            |                 | 
//            |             P1.2|
//
//   Vishy Natarajan
//   Texas Instruments Inc.
//   March 2013
//   Built with IAR Embedded Workbench Version:  5.5x
//******************************************************************************
/*  Copyright 2011-2012 Texas Instruments Incorporated. All rights reserved.

  IMPORTANT: Your use of this Software is limited to those specific rights
  granted under the terms of a software license agreement between the user who
  downloaded the software, his/her employer (which must be your employer) and
  Texas Instruments Incorporated (the "License"). You may not use this Software
  unless you agree to abide by the terms of the License. The License limits your
  use, and you acknowledge, that the Software may not be modified, copied or
  distributed unless embedded on a Texas Instruments microcontroller which is 
  integrated into your product. Other than for the foregoing purpose, you may 
  not use, reproduce, copy, prepare derivative works of, modify, distribute, 
  perform, display or sell this Software and/or its documentation for any 
  purpose.

  YOU FURTHER ACKNOWLEDGE AND AGREE THAT THE SOFTWARE AND DOCUMENTATION ARE
  PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
  INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY, TITLE,
  NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL TEXAS
  INSTRUMENTS OR ITS LICENSORS BE LIABLE OR OBLIGATED UNDER CONTRACT,
  NEGLIGENCE, STRICT LIABILITY, CONTRIBUTION, BREACH OF WARRANTY, OR OTHER LEGAL
  EQUITABLE THEORY ANY DIRECT OR INDIRECT DAMAGES OR EXPENSES INCLUDING BUT NOT
  LIMITED TO ANY INCIDENTAL, SPECIAL, INDIRECT, PUNITIVE OR CONSEQUENTIAL
  DAMAGES, LOST PROFITS OR LOST DATA, COST OF PROCUREMENT OF SUBSTITUTE GOODS,
  TECHNOLOGY, SERVICES, OR ANY CLAIMS BY THIRD PARTIES (INCLUDING BUT NOT
  LIMITED TO ANY DEFENSE THEREOF), OR OTHER SIMILAR COSTS.

  Should you have any questions regarding your right to use this Software,
  contact Texas Instruments Incorporated at www.TI.com.
*******************************************************************************/

#include <stdint.h>
#include "TI_TDC720x.h"
#include "TI_MSP430.h"
#include "TI_MSP430_hardware_board.h"
#include "TI_MSP430_spi.h"
#include "HAL_PMM.h"

void Init_Clock (void);
void InitMCU(void);


// Test TDC720x Register Read/Write & Conversion
uint32_t clk_count;
uint8_t read_val[3], all_data[TDC720x_ALL_DATA_SIZE], byte_data;
uint32_t tout = 0;

uint8_t TDC720x_Parallel_Read = 1;
//******************************************************************************
void main(void)
{
 
    
  WDTCTL = WDTPW+WDTHOLD;                                                      // Stop WDT 
  
  TI_TDC720x_GLED_PxOUT |= TI_TDC720x_GLED_PIN;                                // Set LED ON
  TI_TDC720x_GLED_PxDIR |= TI_TDC720x_GLED_PIN;                                // Set pin direction is output
  __delay_cycles(250000);
  TI_TDC720x_GLED_PxOUT ^= TI_TDC720x_GLED_PIN;
  TI_TDC720x_RLED_PxOUT &= ~TI_TDC720x_RLED_PIN;                                // Set RLED OFF
  TI_TDC720x_RLED_PxDIR |= TI_TDC720x_RLED_PIN;                                // Set pin direction
  
  TI_TDC720x_OSCENABLE_PxOUT |= TI_TDC720x_OSCENABLE_PIN;                    // Set pin high: enable afe osc
  TI_TDC720x_OSCENABLE_PxDIR |= TI_TDC720x_OSCENABLE_PIN;                    // Set pin direction is output

  
  TI_TDC720x_ENABLE1_PxOUT |= TI_TDC720x_ENABLE1_PIN;                            // Enable device
  TI_TDC720x_ENABLE1_PxDIR |= TI_TDC720x_ENABLE1_PIN;                            // Set pin direction output  

#if 0  
  TI_TDC720x_FLAG_PxOUT |= TI_TDC720x_FLAG_PIN;                                // Flag Input Pull up enable
  TI_TDC720x_FLAG_PxREN |= TI_TDC720x_FLAG_PIN;                                // Flag Input Resistor enable  
  TI_TDC720x_FLAG_PxDIR &= ~TI_TDC720x_FLAG_PIN;                               // Set pin direction input  
#endif
  
  // configure Port Pin to handle Interrupt Bar Output (INTB) from TDC720x
  TI_TDC720x_INTB_PxDIR &= ~TI_TDC720x_INTB1_PIN;                               // Set up port pin for INTB
  TI_TDC720x_INTB_PxOUT |= TI_TDC720x_INTB1_PIN;                                // INTB Input Pull up enable  
  TI_TDC720x_INTB_PxREN |= TI_TDC720x_INTB1_PIN;                                // INTB Input Resistor enable  
  TI_TDC720x_INTB_PxIES |= TI_TDC720x_INTB1_PIN;                                // Interrupt Edge Select
  TI_TDC720x_INTB_PxIFG &= ~TI_TDC720x_INTB1_PIN;                               // Clear Interrupt Flag
//  TI_TDC720x_INTB_PxIE |= TI_TDC720x_INTB1_PIN;                               // Enable Port interrupt
  
  // oscillator fail if LED keeps flashing after InitMCU     
  InitMCU();


  TI_TDC720x_SPIByteWriteReg(TI_TDC720x_CONFIG1_REG, 0x01, TDC720x_TDC2);
         
  TI_TDC720x_SPISetup();                                                       // Initilaize MSP430 SPI Block 

// Test TDC720x Register Read/Write & Conversion
  read_val[0] = TI_TDC720x_SPIByteReadReg(0x00, TDC720x_TDC2);
  read_val[1] = TI_TDC720x_SPIByteReadReg(0x01, TDC720x_TDC2);
  read_val[2] = TI_TDC720x_SPIByteReadReg(0x03, TDC720x_TDC2);
  TI_TDC720x_SPIByteWriteReg(0x01, 0x40, TDC720x_TDC2);
  read_val[0] = TI_TDC720x_SPIByteReadReg(0x00, TDC720x_TDC2);
  read_val[1] = TI_TDC720x_SPIByteReadReg(0x01, TDC720x_TDC2);
  read_val[2] = TI_TDC720x_SPIByteReadReg(0x03, TDC720x_TDC2);
#if 0
  // read config1 register
  byte_data = TI_TDC720x_SPIByteReadReg(TI_TDC720x_CONFIG1_REG, TDC720x_TDC2);
  // set mode 2 & start measurement bit
  byte_data |= 0x03;
  TI_TDC720x_SPIByteWriteReg(TI_TDC720x_CONFIG1_REG, byte_data, TDC720x_TDC2);
      
  //wait for INTB pin to go low
  tout = 0;
  while(TI_TDC720x_INTB_PxIN & TI_TDC720x_INTB2_PIN)
  {
    tout++;
    if (tout >= TIMEOUT_VALUE)
       break;
  }
  TI_TDC720x_SPIAllReadReg(all_data, TDC720x_TDC2);
  clk_count = TI_TDC720x_SPILongReadReg(0x11, TDC720x_TDC2);
#endif  


  // test if byte write/read values match
  if (read_val[1]  == 0x40)
  {
     while (1)                                                                 // no error: blink LED continuously
    {
      __delay_cycles(250000);
      __delay_cycles(250000);
      TI_TDC720x_GLED_PxOUT ^= TI_TDC720x_GLED_PIN;        
    }      
  } else
  {
    TI_TDC720x_GLED_PxOUT &= ~TI_TDC720x_GLED_PIN;                             // error: Set LED OFF  
  }
  __bis_SR_register(LPM0_bits + GIE);                                          // Enter LPM0, enable interrupts
  __no_operation();                                                            // For debugger 

}
//******************************************************************************
//******************************************************************************
/**
* @brief Function Name: Init_Clock .                                                
* @brief Description  : Initializes MSP430 clock module. 
* @param parameters   : none                                                    
* @return Value       : none                                                    
*/ 
//******************************************************************************
void Init_Clock(void)
{
//  UCSCTL3 = SELREF_2;                       // Set DCO FLL reference = REFO
//  UCSCTL4 |= SELA_2;                        // Set ACLK = REFO
  // Enable XT2 XIN/XOUT Pins
  P5SEL |= 0x0C;                            // Select XIN, XOUT on P5.3 and P5.2
  UCSCTL6 &= ~XT2OFF;                       // Enable XT2  
  UCSCTL6 |= XT2DRIVE_3; 
  
  P5SEL |= BIT4+BIT5;                       // Select XT1

  UCSCTL6 &= ~(XT1OFF);                     // XT1 On
  UCSCTL6 |= XCAP_3;                        // Internal load cap
  UCSCTL3 = 0;                              // FLL Reference Clock = XT1

  // Loop until XT1,XT2 & DCO stabilizes - In this case loop until XT1 and DCo settle
  do
  {
    UCSCTL7 &= ~(XT2OFFG + XT1LFOFFG + DCOFFG);
                                            // Clear XT2,XT1,DCO fault flags
    SFRIFG1 &= ~OFIFG;                      // Clear fault flags
    TI_TDC720x_RLED_PxOUT ^= TI_TDC720x_RLED_PIN;                              // Toggle LED
    __delay_cycles(250000);    
  }while (SFRIFG1&OFIFG);                   // Test oscillator fault flag
  
  UCSCTL6 &= ~(XT1DRIVE_3);                 // Xtal is now stable, reduce drive strength

  UCSCTL4 |= SELA_0;                        // ACLK = LFTX1 (by default)

  __bis_SR_register(SCG0);                  // Disable the FLL control loop
  UCSCTL0 = 0x0000;                         // Set lowest possible DCOx, MODx
  UCSCTL1 = DCORSEL_7;                      // Select DCO range 50MHz operation
  UCSCTL2 = FLLD_0 + 747;                   // Set DCO Multiplier(762/498) for 25MHz/16MHz
                                            // (N + 1) * FLLRef = Fdco
                                            // (762 + 1) * 32768 = 25MHz
                                            // Set FLL Div = fDCOCLK/2
  __bic_SR_register(SCG0);                  // Enable the FLL control loop

  // Worst-case settling time for the DCO when the DCO range bits have been
  // changed is n x 32 x 32 x f_MCLK / f_FLL_reference. See UCS chapter in 5xx
  // UG for optimization.
  // 32 x 32 x 25 MHz / 32,768 Hz ~ 780k MCLK cycles for DCO to settle
  __delay_cycles(782000);

  // Loop until XT1,XT2 & DCO stabilizes - In this case only DCO has to stabilize
  do
  {
    UCSCTL7 &= ~(XT2OFFG + XT1LFOFFG + DCOFFG);
                                            // Clear XT2,XT1,DCO fault flags
    SFRIFG1 &= ~OFIFG;                      // Clear fault flags
    TI_TDC720x_RLED_PxOUT ^= TI_TDC720x_RLED_PIN;                              // Toggle LED
    __delay_cycles(250000);    
  }while (SFRIFG1&OFIFG);                   // Test oscillator fault flag  
  
  UCSCTL4 = SELA__XT1CLK + SELS__DCOCLKDIV + SELM__DCOCLKDIV;                  // SMCLK=MCLK=

  // Loop until XT1,XT2 & DCO stabilizes - In this case only DCO has to stabilize
  do
  {
    UCSCTL7 &= ~(XT2OFFG + XT1LFOFFG + DCOFFG);
                                            // Clear XT2,XT1,DCO fault flags
    SFRIFG1 &= ~OFIFG;                      // Clear fault flags
    TI_TDC720x_RLED_PxOUT ^= TI_TDC720x_RLED_PIN;                              // Toggle LED
    __delay_cycles(250000);    
  }while (SFRIFG1&OFIFG);                   // Test oscillator fault flag  
     
  TI_TDC720x_RLED_PxOUT &= ~TI_TDC720x_RLED_PIN;                                // turn off red  
  
}
//******************************************************************************
/**
* @brief  Local functions.                           
*/

/**
* @brief Function Name:  InitMCU.                                                
* @brief Description  :  Initializes the MSP430 peripherals and modules.
* @param parameters   :  none                                                   
* @return Value       :  none                                                   
*/   
//******************************************************************************
void InitMCU(void)
{
  
  __disable_interrupt();                                                       // Disable global interrupts 
    SetVCore(3);
    Init_Clock();                                                              //Init clocks	
  __enable_interrupt();                                                        // enable global interrupts

}
//******************************************************************************

the only thing altered is TDC2 is selected and used rather than TDC1. 

CC2652R: reference design for cc2652+cc2592

CC1350: Migration from CC1110 to CC1350 in my project

$
0
0

Part Number:CC1350

Dear users

I have a project based on CC1110 chip and I want to migrate to the new CC1350, mostly because of BLE and 915Mhz on the same chip.

Currenly I have a following configuratin for RF part:

SYNC1     = 0xFF; // sync word, high byte
SYNC0     = 0x00; // sync word, low byte
PKTLEN    = 0xFF; // packet length
PKTCTRL1  = 0x00; // packet automation control
PKTCTRL0  = 0x00; // packet automation control
ADDR      = 0x00;
CHANNR    = 0x02; // channel number
FSCTRL1   = 0x06; // frequency synthesizer control
FSCTRL0   = 0x00;
FREQ2     = 0x26; // frequency control word, high byte
FREQ1     = 0x2F; // frequency control word, middle byte
FREQ0     = 0xE4; // frequency control word, low byte
MDMCFG4   = 0xB9; // modem configuration
MDMCFG3   = 0x66; // modem configuration
MDMCFG2   = 0x33; // modem configuration
MDMCFG1   = 0x61; // modem configuration
MDMCFG0   = 0xe6; // modem configuration
DEVIATN   = 0x15; // modem deviation setting
MCSM2     = 0x07;
MCSM1     = 0x30;
MCSM0     = 0x18; // main radio control state machine configuration
FOCCFG    = 0x17; // frequency offset compensation configuration
BSCFG     = 0x6C;
FREND1    = 0x56; // front end tx configuration
FREND0    = 0x11; // front end tx configuration
FSCAL3    = 0xE9; // frequency synthesizer calibration
FSCAL2    = 0x2A; // frequency synthesizer calibration
FSCAL1    = 0x00; // frequency synthesizer calibration
FSCAL0    = 0x1F; // frequency synthesizer calibration
TEST1     = 0x31; // various test settings
TEST0     = 0x09; // various test settings
PA_TABLE0 = 0x00; // needs to be explicitly set!
PA_TABLE1 = 0x57; // pa power setting 0 dBm

I'm worried if I can use the same RF settings for the new cс1350.


DLPDLCR2000EVM: Control Individual Micro-mirrors?

$
0
0

Part Number:DLPDLCR2000EVM

I have successfully gotten the dlp2000 evm + beaglebone black combination to work. Now, I would like to be able to control the individual micro-mirrors of the DMD chip at a very low level if possible. I'm not super familiar with the technology but I'm guessing that each micro-mirror is voltage/current controlled and has an addressable location in the array, no? Could someone point me in a good direction? I've read through the programmer's guide, but I don't need to display video. I just want to show predefined black/white patterns and maybe be able to switch from red light to white light and vice-versa.

And if there is a way to do this in Python that would be super ideal. If this isn't possible, I guess I will try writing a driver to abstract the DMD array into an addressable matrix or something.

CCS/TMS570LC4357: I can no longer flash code to the HDK for a debug session

$
0
0

Part Number:TMS570LC4357

Tool/software: Code Composer Studio

Hello,

I have been able to repeatedly compile and launch a debug session with the HDK over the past month.

Sometimes when the computer comes out of hibernation or low power standby, it has trouble connecting to the board.

If I disconnect power to the board, and disconnect and reconnect the USB cable, the connection is usually reestablished.

Sometimes I have needed to completely reboot the computer, and then connection is OK.

But now, the connection continuously fails. There is no method or procedure that causes a successful connection anymore.

Is there a means to reset the drivers for the jtag USB Debug Probe?

I have changed to a new HDK board, a new USB cable, and tried all the different available USB ports, and NOTHING is working anymore!

I go into the Project Properties panel, and check verify for the Texas Instruments XDS100V2 USB Debug Probe, and I get:

This error is generated by TI's USCIF driver or utilities. The value is '-150' (0xffffff6a). The title is 'SC_ERR_FTDI_FAIL'. The explanation is: One of the FTDI driver functions used during configuration returned a invalid status or an error.

Since this error is reported for different HDK hardware, different USB cables, and different USB ports, I primarily suspect it is due to a fault in a driver that needs updated.

Please advise on the best way to update or repair drivers for this functionality, please help provide a method to reliably enable connection for loading/starting a debug session on the HDK.

Thank You,

-Joseph 

ADS42JB69: Clarification on Bandwidth

$
0
0

Part Number:ADS42JB69

On Page 59 the analog input bandwidth is said to be 900 MHz.  But then it static that the first stage bandwidth is 250 MHz and 400 MHz depending on signal strength. 

I am a little confused by that. What first stages is it actually referring to? I need to understand so I can explain.

Thanks

SN74AC14: Operating with +/- power supplies to generate negative logic

$
0
0

Part Number:SN74AC14

Looking at using this inverter or another similar logic device in an application that needs +/-3.0 output logic levels. for this, VCC = 3.3V and VSS = -3.3V to make sure output reaches +/- 3.0V under load (< 1 uA). 

Any issue with this supply arrangement?  The total supply range is 6.6V which is above the recommended power supply range (2 - 6V), but below the absolute max rating of 7V. 

Understand that inputs will need to be level-shifted down to reference -3.3V VSS 

CC2538: Link Key related material

$
0
0

Part Number:CC2538

I want to find the code that in the joining part, the coordinator transport the link key to the end device to update from the default link key, but I cannot find it. Is there any code that is related to this part?

Best Regards

 Xian Wang

Viewing all 262198 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>