Part Number: IWR6843ISK

• Version of mmWave SDK:  mmwave_sdk_03_00_00_08

• Details of board platform IWR6843ISK PROC 073 Rev A.and MMWAVEICBOOST

I had the ROS point cloud demo working yesterday, but now it keeps failing.  RViz opens but no points are displayed.

I have tried 3 different power supplies, it was working with a 2.5A supply yesterday.  I have been trying to make it work again with a 3.5A power supply, but ROS is still complaining about mmWaveCLI failing.  the output is below

$ roslaunch ti_mmwave_rospkg rviz_6843_3d.launch
... logging to /home/dharper/.ros/log/b5957b96-c44d-11e9-bce3-9cb6d0c83c04/roslaunch-CPR01973-369.log
Checking log directory for disk usage. This may take a while.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

started roslaunch server http://CPR01973:56324/

SUMMARY
========

PARAMETERS
 * /mmWave_Manager/command_port: /dev/ttyS5
 * /mmWave_Manager/command_rate: 115200
 * /mmWave_Manager/data_port: /dev/ttyS4
 * /mmWave_Manager/data_rate: 921600
 * /mmWave_Manager/max_allowed_azimuth_angle_deg: 90
 * /mmWave_Manager/max_allowed_elevation_angle_deg: 90
 * /rosdistro: indigo
 * /rosversion: 1.14.3

NODES
  /
    mmWaveQuickConfig (ti_mmwave_rospkg/mmWaveQuickConfig)
    mmWave_Manager (ti_mmwave_rospkg/ti_mmwave_rospkg)
    rviz (rviz/rviz)
    static_tf_map_to_base_radar_link (tf/static_transform_publisher)

auto-starting new master
process[master]: started with pid [382]
ROS_MASTER_URI=http://localhost:11311

setting /run_id to b5957b96-c44d-11e9-bce3-9cb6d0c83c04
process[rosout-1]: started with pid [396]
started core service [/rosout]
process[mmWave_Manager-2]: started with pid [403]
process[mmWaveQuickConfig-3]: started with pid [404]
process[static_tf_map_to_base_radar_link-4]: started with pid [405]
[ INFO] [1566417369.162228600]: mmWaveQuickConfig: Configuring mmWave device using config file: /home/dharper/catkin_ws/src/ti_mmwave_rospkg/cfg/6843_3d.cfg
[ INFO] [1566417369.172232400]: waitForService: Service [/mmWaveCommSrv/mmWaveCLI] has not been advertised, waiting...
process[rviz-5]: started with pid [406]
[ INFO] [1566417369.513027500]: Initializing nodelet with 12 worker threads.
[ INFO] [1566417369.518699900]: mmWaveCommSrv: command_port = /dev/ttyS5
[ INFO] [1566417369.519014700]: mmWaveCommSrv: command_rate = 115200
[ INFO] [1566417369.522130700]: mmWaveDataHdl: data_port = /dev/ttyS4
[ INFO] [1566417369.522358700]: mmWaveDataHdl: data_rate = 921600
[ INFO] [1566417369.522802600]: mmWaveDataHdl: max_allowed_elevation_angle_deg = 90
[ INFO] [1566417369.523325000]: mmWaveDataHdl: max_allowed_azimuth_angle_deg = 90
[ INFO] [1566417369.525800600]: DataUARTHandler Read Thread: Port is open
[ INFO] [1566417369.532174200]: waitForService: Service [/mmWaveCommSrv/mmWaveCLI] is now available.
[ INFO] [1566417369.533032000]: mmWaveQuickConfig: Ignored blank or comment line: '% ***************************************************************'
[ INFO] [1566417369.533993400]: mmWaveQuickConfig: Ignored blank or comment line: '% Created for SDK ver:03.00'
[ INFO] [1566417369.534521500]: mmWaveQuickConfig: Ignored blank or comment line: '% Created using Visualizer ver:3.0.0.1'
[ INFO] [1566417369.535384100]: mmWaveQuickConfig: Ignored blank or comment line: '% Frequency:60.25'
[ INFO] [1566417369.535940200]: mmWaveQuickConfig: Ignored blank or comment line: '% Platform:xWR68xx'
[ INFO] [1566417369.536354200]: mmWaveQuickConfig: Ignored blank or comment line: '% Scene Classifier:best_range_res'
[ INFO] [1566417369.537073800]: mmWaveQuickConfig: Ignored blank or comment line: '% Azimuth Resolution(deg):15 + Elevation'
[ INFO] [1566417369.538129900]: mmWaveQuickConfig: Ignored blank or comment line: '% Range Resolution(m):0.045'
[ INFO] [1566417369.538766900]: mmWaveQuickConfig: Ignored blank or comment line: '% Maximum unambiguous Range(m):9.02'
[ INFO] [1566417369.539434600]: mmWaveQuickConfig: Ignored blank or comment line: '% Maximum Radial Velocity(m/s):5.06'
[ INFO] [1566417369.541080400]: mmWaveQuickConfig: Ignored blank or comment line: '% Radial velocity resolution(m/s):0.64'
[ INFO] [1566417369.541771700]: mmWaveQuickConfig: Ignored blank or comment line: '% Frame Duration(msec):33.333'
[ INFO] [1566417369.542278000]: mmWaveQuickConfig: Ignored blank or comment line: '% Range Detection Threshold (dB):9'
[ INFO] [1566417369.542789600]: mmWaveQuickConfig: Ignored blank or comment line: '% Doppler Detection Threshold (dB):9'
[ INFO] [1566417369.543255700]: mmWaveQuickConfig: Ignored blank or comment line: '% Range Peak Grouping:disabled'
[ INFO] [1566417369.543851000]: mmWaveQuickConfig: Ignored blank or comment line: '% Doppler Peak Grouping:enabled'
[ INFO] [1566417369.544413400]: mmWaveQuickConfig: Ignored blank or comment line: '% Static clutter removal:disabled'
[ INFO] [1566417369.544948900]: mmWaveQuickConfig: Ignored blank or comment line: '% Angle of Arrival FoV: Full FoV'
[ INFO] [1566417369.545455800]: mmWaveQuickConfig: Ignored blank or comment line: '% Range FoV: Full FoV'
[ INFO] [1566417369.546006400]: mmWaveQuickConfig: Ignored blank or comment line: '% Doppler FoV: Full FoV'
[ INFO] [1566417369.546433400]: mmWaveQuickConfig: Ignored blank or comment line: '% ***************************************************************'
[ INFO] [1566417369.547409500]: mmWaveQuickConfig: Sending command: 'sensorStop'
[ INFO] [1566417369.550556200]: mmWaveCommSrv: Sending command to sensor: 'sensorStop'
[ INFO] [1566417369.556965800]: mmWaveCommSrv: Received response from sensor: 'sensorStop
Ignored: Sensor is already stopped
Done
mmwDemo:/>'
[ INFO] [1566417369.564453700]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.565237000]: mmWaveQuickConfig: Sending command: 'flushCfg'
[ INFO] [1566417369.568092700]: mmWaveCommSrv: Sending command to sensor: 'flushCfg'
[ INFO] [1566417369.571070300]: mmWaveCommSrv: Received response from sensor: 'flushCfg
Done
mmwDemo:/>'
[ INFO] [1566417369.576981600]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.577820400]: mmWaveQuickConfig: Sending command: 'dfeDataOutputMode 1'
[ INFO] [1566417369.580570600]: mmWaveCommSrv: Sending command to sensor: 'dfeDataOutputMode 1'
[ INFO] [1566417369.584475600]: mmWaveCommSrv: Received response from sensor: 'dfeDataOutputMode 1
Done
mmwDemo:/>'
[ INFO] [1566417369.591152300]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.591860900]: mmWaveQuickConfig: Sending command: 'channelCfg 15 7 0'
[ INFO] [1566417369.594686600]: mmWaveCommSrv: Sending command to sensor: 'channelCfg 15 7 0'
[ INFO] [1566417369.598581200]: mmWaveCommSrv: Received response from sensor: 'channelCfg 15 7 0
Done
mmwDemo:/>'
[ INFO] [1566417369.604225000]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.604827900]: mmWaveQuickConfig: Sending command: 'adcCfg 2 1'
[ INFO] [1566417369.607846200]: mmWaveCommSrv: Sending command to sensor: 'adcCfg 2 1'
[ INFO] [1566417369.611110400]: mmWaveCommSrv: Received response from sensor: 'adcCfg 2 1
Done
mmwDemo:/>'
[ INFO] [1566417369.617244400]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.617964800]: mmWaveQuickConfig: Sending command: 'adcbufCfg -1 0 1 1 1'
[ INFO] [1566417369.620851700]: mmWaveCommSrv: Sending command to sensor: 'adcbufCfg -1 0 1 1 1'
[ INFO] [1566417369.625120500]: mmWaveCommSrv: Received response from sensor: 'adcbufCfg -1 0 1 1 1
Done
mmwDemo:/>'
[ INFO] [1566417369.630767600]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.631552800]: mmWaveQuickConfig: Sending command: 'profileCfg 0 60.25 7 7 75 0 0 50 1 240 3582 0 0 30'
[ INFO] [1566417369.634792800]: mmWaveCommSrv: Sending command to sensor: 'profileCfg 0 60.25 7 7 75 0 0 50 1 240 3582 0 0 30'
[ INFO] [1566417369.642019900]: mmWaveCommSrv: Received response from sensor: 'profileCfg 0 60.25 7 7 75 0 0 50 1 240 3582 0 0 30
Done
mmwDemo:/>'
[ INFO] [1566417369.648258900]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.649002000]: mmWaveQuickConfig: Sending command: 'chirpCfg 0 0 0 0 0 0 0 1'
[ INFO] [1566417369.651760400]: mmWaveCommSrv: Sending command to sensor: 'chirpCfg 0 0 0 0 0 0 0 1'
[ INFO] [1566417369.656150200]: mmWaveCommSrv: Received response from sensor: 'chirpCfg 0 0 0 0 0 0 0 1
Done
mmwDemo:/>'
[ INFO] [1566417369.662827400]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.663591600]: mmWaveQuickConfig: Sending command: 'chirpCfg 1 1 0 0 0 0 0 4'
[ INFO] [1566417369.666466400]: mmWaveCommSrv: Sending command to sensor: 'chirpCfg 1 1 0 0 0 0 0 4'
[ INFO] [1566417369.670945700]: mmWaveCommSrv: Received response from sensor: 'chirpCfg 1 1 0 0 0 0 0 4
Done
mmwDemo:/>'
[ INFO] [1566417369.677450700]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.677992500]: mmWaveQuickConfig: Sending command: 'chirpCfg 2 2 0 0 0 0 0 2'
[ INFO] [1566417369.680823600]: mmWaveCommSrv: Sending command to sensor: 'chirpCfg 2 2 0 0 0 0 0 2'
[ INFO] [1566417369.685156200]: mmWaveCommSrv: Received response from sensor: 'chirpCfg 2 2 0 0 0 0 0 2
Done
mmwDemo:/>'
[ INFO] [1566417369.690728300]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.691653800]: mmWaveQuickConfig: Sending command: 'frameCfg 0 2 16 0 33.333 1 0'
[ INFO] [1566417369.694466800]: mmWaveCommSrv: Sending command to sensor: 'frameCfg 0 2 16 0 33.333 1 0'
[ INFO] [1566417369.699327000]: mmWaveCommSrv: Received response from sensor: 'frameCfg 0 2 16 0 33.333 1 0
Done
mmwDemo:/>'
[ INFO] [1566417369.706621400]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.707183000]: mmWaveQuickConfig: Sending command: 'lowPower 0 0'
[ INFO] [1566417369.710033300]: mmWaveCommSrv: Sending command to sensor: 'lowPower 0 0'
[ INFO] [1566417369.713465300]: mmWaveCommSrv: Received response from sensor: 'lowPower 0 0
Done
mmwDemo:/>'
[ INFO] [1566417369.720668100]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.721303800]: mmWaveQuickConfig: Sending command: 'guiMonitor -1 1 0 0 0 0 0'
[ INFO] [1566417369.724643200]: mmWaveCommSrv: Sending command to sensor: 'guiMonitor -1 1 0 0 0 0 0'
[ INFO] [1566417369.729234700]: mmWaveCommSrv: Received response from sensor: 'guiMonitor -1 1 0 0 0 0 0
Done
mmwDemo:/>'
[ INFO] [1566417369.735043900]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.735970700]: mmWaveQuickConfig: Sending command: 'cfarCfg -1 0 0 8 4 4 0 768 0'
[ INFO] [1566417369.738881400]: mmWaveCommSrv: Sending command to sensor: 'cfarCfg -1 0 0 8 4 4 0 768 0'
[ INFO] [1566417369.743773500]: mmWaveCommSrv: Received response from sensor: 'cfarCfg -1 0 0 8 4 4 0 768 0
Done
mmwDemo:/>'
[ INFO] [1566417369.749547300]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.750270200]: mmWaveQuickConfig: Sending command: 'cfarCfg -1 1 0 4 2 3 1 768 1'
[ INFO] [1566417369.753303800]: mmWaveCommSrv: Sending command to sensor: 'cfarCfg -1 1 0 4 2 3 1 768 1'
[ INFO] [1566417369.758163600]: mmWaveCommSrv: Received response from sensor: 'cfarCfg -1 1 0 4 2 3 1 768 1
Done
mmwDemo:/>'
[ INFO] [1566417369.763989000]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1566417369.765269100]: mmWaveQuickConfig: Sending command: 'multiObjBeamForming -1 1 0.5'
[ERROR] [1566417369.767174900]: mmWaveQuickConfig: Failed to call service mmWaveCLI
[ERROR] [1566417369.767425000]: multiObjBeamForming -1 1 0.5
[mmWaveQuickConfig-3] process has died [pid 404, exit code 1, cmd /home/dharper/catkin_ws/devel/lib/ti_mmwave_rospkg/mmWaveQuickConfig /home/dharper/catkin_ws/src/ti_mmwave_rospkg/cfg/6843_3d.cfg __name:=mmWaveQuickConfig __log:=/home/dharper/.ros/log/b5957b96-c44d-11e9-bce3-9cb6d0c83c04/mmWaveQuickConfig-3.log].
log file: /home/dharper/.ros/log/b5957b96-c44d-11e9-bce3-9cb6d0c83c04/mmWaveQuickConfig-3*.log

I have tried reloading v3.2 of the demo firmware and tried out the mmWave Demo Visualizer and it works, but the ROS demo does not anymore.

Part Number: DRV2700

Good afternoon,

We've designed a board that uses the DRV2700 driver to drive a 1.5uF piezo actuator that positions a mirror.  Its input is a 0-12V DC signal (mcoil-) that makes small (<1V) corrections up to 50k times per second.  It is working quite nicely, though limited to 105V at the output in this configuration, but the output noise is canceled out in differential mode, so a big improvement over the flyback version.

However, we've had 3 of these drivers blow up.  Suddenly the HV output drops low, as does the voltage present on the SW node.  In circuit, I measure ~1.08k ohms between pins 8 (SW) and 11 (VBST).  On a working driver, I measure ~800k ohms between these two nodes.  One time the driver blew up when power was cycled, another time the driver blew up when the input signal (mcoil-) changed suddenly by a volt or two.  After blowing up, the driver board draws excessive current (enough to burn up a zero ohm 0603 resistor in the 5V supply path).

With the bad parts removed from the board, I measure between pins 8 and 11. 50 ohms on one, 1.4k ohms on another.  A working driver measures OPEN between these 2 nodes.

I see from the block diagram that there is a diode between pins 8 and 11, and sure enough, my DMM in diode mode measures .615V on a working part, and 0.558V on a bad part.  One part (that measured 50 ohms) measures 0.056 across that diode, so nearly a short.

From the datasheet, I don't see ratings that I am exceeding.  My schematic is attached below.  Do you see any glaring problems with how this is configured?  Or some known mode of operation that can lead to permanent damage to this part, and the apparent diode between SW and BST nodes in particular?

Thank you,

Andy

Part Number: TPS40090-Q1

Hi Team,

I wanted to verify the startup operation of the TPS40090-Q1. According to the engineer i am working with he is seeing the following start up behavior, which in fact is not documented in the datasheet:

1. When EN pin goes high the IC starts up in hiccup (7 SS ramp cycles) mode occasionally.
   I’m not sure it’s a feature or bug, but it’s slightly inconvenient for us, since it messes up our power sequence a bit.
   
   (In our design we don’t use the internal BP5 regulator, but we provide 5V directly instead. That 5V supply is present before EN is asserted.)
2. We are using it in 2-Phase configuration, but soft-start and shutdown ramps are always generated with only phase #1 active.
   Likewise, I’m also unsure whether it’s a feature or bug, but datasheet does not mention such behavior to be exist. 

During this time the only load is a ~25Ohm bleeder resistance on this 0.85V rail. It seems that after EN goes high the device starts in hiccup mode.

Part Number: CC1352P

Hi Team,

Could you please advise if there is any PA available for CC1352P, for an example, CC1190 can support CC1352P?

Thanks in advance

Kind regards,

Shai

Part Number: MSP430F2272

MSP430F2272

Part Number: UCD90320

Hi,

If there is a GPI fault and an AMON fault that occur at the same time, how much delay would there need to be between the two faults to ensure the GPI fault will always be logged first?

Also, would this vary depending on device? For example 90160 vs  90320 vs 90120A.

Thanks,

Jose

Part Number: LMX2595

I'm trying to do a manual ramp (15 to 16.6 GHz, 133.33 MHz steps, re-cal every step).  Using Trigger A = RampClk Rising Edge and RAMP0_NEXT_TRIG = Trigger A, this works fine for the first ramp.

My question is how to reset the ramp back to 14GHz.  Enabling RAMP0_RST makes the ramp not work at all (which makes sense - the datasheet says RAMP0_RST must only be used in automatic mode).

The obvious way to do this is to set RAMP1 up to have -133.33MHz steps and provide the required number of RampClk edges to get back to the starting frequency, but this provides no protection in case of a RampClk glitch - the frequencies will be off by one step forever.

I can also reset everything using SPI commands, but I'd prefer not to have to take so long to reset the ramp.

Is there any way I can set this up to reset the ramp back to its original frequency by, for example, toggling RampDir? 

Part Number: CC2652R

Hi,

I found on documentation that the function "appForceBoot" need to execute when I want to start the serial bootloader from the app code,

But I cant find the reference for it.

Only found it in a file:

simplelink_cc26x2_sdk_2_30_00_34\source\ti\ble5stack\common\cc26xx\onboard.c

But the folder ../../util/sbl/app/ not exist.

Please advice.

I'm using simplelink_cc26x2_sdk_2_30_00_34.

SN55LVDS31-SP

Could you let me know the package information as follows?

P/N:
5962-9762101VFA

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom

Part Number: MSP430F5259

Tool/software: TI C/C++ Compiler

Hello, 

I'm trying to restore a very old project - MSP430F5259, TI-RTOS based, built circa 2015/6.

I've installed the latest TI-RTOS(2.20) / MSPWare (3.80.03.07) /CCS (v901) / xdctools (3.55.02.22) and pulled the source and project files from git.

I just can't get it to build properly.

I'm afraid that I'm experiencing a mess-up between older and current versions of the dev tools/libraries etc and probably system 'macros' (aka 'variables' such as ${COM_TI_MCU_MSP430WARE_LIBRARY_PATH}) are probably irrelevant...

Is there a way / clear guide of how to prepare a clean build environment comprising the ide (ccs), rtos, xdctools and supporting MSPware libraries (or are these part of the RTOS distribution) + sys 'variables', and what are their interdependencies - e.g. which versions work with which, is there a forward compatibility, driverlib & iqmathlib location (MSPware folders or TI RTOS folders) etc etc..

What is the correct way to recover an old project as I'm spending hours and hours to no avail  :-(

Thanks

Part Number: ADC128S102QML-SP

Could you let me know the package information as follows?

P/N:
5962R0722701VZA

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom

(Please visit the site to view this file)

Part Number: ADS5463-SP

Could you let me know the package information as follows?

P/N:
5962R0720802VXC

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom(Please visit the site to view this file)

Part Number: SN54LVTH244A-SP

Could you let me know the package information as follows?

P/N:
5962-9584401VSA

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom(Please visit the site to view this file)

Part Number: SN55LVDS33-SP

Could you let me know the package information as follows?

P/N:
5962-0724801VFA

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom(Please visit the site to view this file)

Part Number: TLK2711-SP

Could you let me know the package information as follows?

P/N:
5962-0522101VXC

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom(Please visit the site to view this file)

Part Number: CC2642R

Hi,

I’m using SDK 3.10. GapBondMgr adds/removes bond info to/from the bonding table and manages resolving list and white list(if synced) as well. By the spec, modifying resolving list and white list contents are prohibited under some conditions which are all related to scanning, advertising, and connection requesting. There is nothing to do with active connection. It seems that the Link Layer correctly responds according to the spec.

However, the spec is not taken into account when GapBondMgr updates resolving list and white list.

• When adding a device to those lists upon authentication completion, GapBondMgr doesn’t check anything. As a result, if there is any on-going scanning or advertising associated with privacy/whitelist, those list will not be updated. LL will reject, but application won’t know.
• When removing a device (or all) from those lists upon GAPBOND_ERASE_SINGLEBOND (or GAPBOND_ERASE_ALLBONDS), GapBondMgr checks if there is any active connection, and delays the removal, if there is any, until all the connections are terminated. As a result, even when there is no on-going scanning or advertising associated with privacy/whitelist and therefore LL can handle it, the removal is unnecessarily delayed or never happens in the worst case.

My suggestion is, GapBondMgr checks if a removal is associated with a connection currently active only. If there is no active connection associated with the current GAPBOND_ERASE_SINGLEBOND request shall not be delayed inside GapBondMgr. Pausing privacy/whitelist-related advertising/scanning can be left to application’s responsibility.

- Cetri

Part Number: DAC121S101QML-SP

Could you let me know the package information as follows?

P/N:
5962R0722602VZA

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom(Please visit the site to view this file)

Part Number: TL1431-SP

Could you let me know the package information as follows?

P/N:
5962-9962001VPA

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom(Please visit the site to view this file)

Part Number: UC1843-SP

Could you let me know the package information as follows?

P/N:
5962-8670410VPA

・Package material/ base plating /plating (ex. Ceramic(Alumina)/Ni/Au

・Lid material/ base plating /plating (ex. Covar/Ni/Au

・Package cavity wall thickness(mm) (ex. 0.25mm

・Lid thickness(mm) (ex. 0.25mm

・Part weight(typ. grams) (ex. 3.5g

・Part weight(max. grams) (ex. 4.0g

We'd like to use it for a thermal & radiation analysis.

Regards,
Tom(Please visit the site to view this file)

Part Number: DLP3010EVM-LC

I recently purchase a DLP3010EVM-LC. Initially, I was able to successfully set it up and operate it through the DLP GUI (v2.1.0.7). I was also able to successfully deploy the updated firmware (v 7.3.1) as well, and continue to operate it afterwards. Specifically, it was still able to display a clone of my computer screen or display custom patterns through the GUI.

In a subsequent session with using the device, the DLP GUI started giving me an error message "Get Video Information Error! Error while trying to gain access to the I2C bus" when I hit any "get" button. As far as I can tell, I have reassembled the entire system exactly as described in the DLP3010EVM-LC user manual. In the EVM information, it is able to recognize the DLPC3430 controller, but is unable to recognize the DMD or the PMIC/LED driver. Upon power up, D5 and D6 LEDs are appropriately lit. D1 and D2 are also lit. When switching the projector to the on position, D3 lights up. However, the RGB LEDs no longer are powered and there is no image projected from the system. If an HDMI cable is attached, the MSP2/D7 LED lights up as well. The fans continue to operate normally. It is still possible to successfully redeploy the firmware update to the system, although doing so does not appear to make any meaningful change in the system operation.

Please advise. Thank you.