Part Number:TPS92692-Q1
Hello,
The Pout(max) in the table 5 of Buck Boost design parameters is 12.6W.
However, the Vout is 39.6V(max) and ILED is 1500mA(max). So the Pout (max) would be 59.4W
I think that the calculation of Pout is not same with 12.6W if we use maximum value of Vout and ILED.
Is the calculated value of 12.6W correct?
Part Number:TMS320F28335
There is AEC-Q100 qualification in datasheet.
TMS320F28335PTPQ can support PPAP?
Part Number:66AK2H06
Hi all,
I cannot find the code for EDMA3 linking and chaining example with CSL function in my local pdk_k2hk_4_0_12 folder.
Does anyone have suggestion or can provide the code example?
Thank you.
Part Number:PUREPATHCONSOLE
Is there a way the PPC3 software can be controlled by an external control surface or midi controller? What I am talking about is something that looks like a modern mixer that could, for example, control the equalizer bi-quad filters. In order for this to work, I would need to have access to Key Definitions used in the application. I have attached a link to an example programmable MIDI control surface.
Mackie Pro - https://mackie.com/products/mcu-pro-and-xt-pro
Brian
Part Number:TMS320F28023
Tool/software: Code Composer Studio
Win7 (SP1), CCS 6.
I am making a program with a "Function Jump Table," and I am having difficulty getting the table to be placed in the program section (.text) in page 0.
My program receives an ASCII byte in the range '0'..'Z' from the serial port then depending on that byte I want to jump to 43 different functions.
Ideally, I'd like it to put the table in the .text section someplace. The actual location is unimportant.
This is what I have so far, and this works...
Here is the partial contents of Menu_Commands.def
/* 0 */ GetParagraphs, /* 1 */ GetDirect, /* 2 */ PutDirect, /* 3 */ ...(40 more)
And the declaration to the corresponding FunctionCallTable looks like...
#pragma DATA_SECTION(FunctionCallTable, "FunctCodeTbl");
static void (* FunctionCallTable[])(void) = {
#include "Menu_Commands.def" /* see above */
};And finally, the code that actually jumps...
if ((byte1 >= '0') && (byte1 <= 'Z')) {
byte1 -= '0';
FunctionCallTable[byte1]();
}I created a memory area in FLASH in page 1, then I make a section (you see above) and that works, but the problem is the compiler or linker creates a bunch of entries in the .cinit section because it thinks it is data that needs to be initialized. Not to mention all the effort of setting aside some FLASH so the two memory areas don't overlap.
So, I have tried to replace the pragma with the following...
#pragma CODE_SECTION(FunctionCallTable, ".text");
but I get a compiler error stating...
"N:/Standalone/Piccolo-28022/Src/MainSub.c", line 81: warning #1111-D: pragma CODE_SECTION can only be applied to a function definition, not "FunctionCallTable" (declared at line 83)
Please, can someone tell me how to set this straight?
I have considered writing all this in assembler, and I am sure I can do so, but I'd rather let the C compiler deal with it.
Thanks for any help on this,
Mark
Part Number:DLP2010EVM-LC
I am attempting to read data from a 2010 EVM and am getting unexpected results from my read functions. This function is very
similar to my write functions (all of which work no problem). Can anyone give a suggestion as to what I might be getting wrong?
This function should return the 'input source selection' detailed at the bottom of this message.
int DLPC3470_USB_Read() { UINT8 gpioValue = 0; UCHAR rData[64]; CY_DATA_BUFFER rdBuffer; CY_I2C_DATA_CONFIG i2cReadConfig; CY_RETURN_STATUS retStatus; int retry = 1000; UINT32 timeout = 5000; memset(rData, 0, sizeof(rData)); rdBuffer.buffer = rData; rdBuffer.buffer[0] = 0x06; // read input source select rdBuffer.length = 1; i2cReadConfig.slaveAddress = 0x1B; i2cReadConfig.isNakBit = false; i2cReadConfig.isStopBit = true; if (cyHandle == NULL) // cyHandle is static to the file and is open at this point return CY_ERROR_INVALID_HANDLE; // set GPIO5 to request I2C bus; wait for GPIO6 to go high to awknowlege request; set GPIO9 high to enable I2C bus retStatus = CySetGpioValue(cyHandle, 0x05, 0x01); while (gpioValue != 1 && retry--) retStatus = CyGetGpioValue(cyHandle, 0x06, &gpioValue); retStatus = CySetGpioValue(cyHandle, 0x09, 0x01); // after this call, I would expect rdBuffer.buffer[0] to hold the current source select....it does not printf("rdBuffer values before CyI2cRead() call\n"); printf("rdBuffer[0] is %d\nrdBuffer[1] is %d\nrdBuffer[2] is %d\n", rdBuffer.buffer[0], rdBuffer.buffer[1], rdBuffer.buffer[2]); retStatus = CyI2cRead(cyHandle, &i2cReadConfig, &rdBuffer, 5000); if (retStatus != CY_SUCCESS) printf("CyI2cRead failure\n"); else { printf("Results of CyI2cRead()\n"); printf("rdBuffer should now have a value of 0-5 or 255 per section 3.1.2 of DLPC3470 and DLP3478 Software Programmer's Guide\n"); printf("rdBuffer[0] is %d\nrdBuffer[1] is %d\nrdBuffer[2] is %d\n", rdBuffer.buffer[0], rdBuffer.buffer[1], rdBuffer.buffer[2]); } retStatus = CySetGpioValue(cyHandle, 0x05, 0x00); // done with I2C bus retStatus = CySetGpioValue(cyHandle, 0x09, 0x00); // done with I2C bus return rdBuffer.transferCount; }
--------------------- output here ------------------------
rdBuffer values before CyI2cRead() call
rdBuffer[0] is 6
rdBuffer[1] is 0
rdBuffer[2] is 0
Results of CyI2cRead()
rdBuffer should now have a value of 0-5 or 255 per section 3.1.2 of DLPC3470 and DLP3478 Software Programmer's Guide
rdBuffer[0] is 158
rdBuffer[1] is 0
rdBuffer[2] is 0
-------------------- expected results ---------------------
3.1.2 Read Input Source Select (06h)
This command reads the operating mode of the system.
3.1.2.1 Read Parameters
This command has no parameters.
3.1.2.2 Return Parameters
Byte 1 Operating Mode
00h Display - External Video Mode
01h Display - Test Pattern Generator Mode
02h Display - Splash Screen Mode
03h Light Control – External Pattern Streaming Mode
04h Light Control – Internal Pattern Streaming Mode
05h Light Control – Splash Pattern Mode
06h - FEh Reserved
FFh Standby Mode
This command works in all operating modes and has no effect on the current system configuration.
Part Number:LM73606-Q1
Are there any specification differences between LM73606QRNPRQ1 (Q100 version) and LM73606RNPR (catalog)? I could not find anything significant. My customer wants to confirm there's no difference, as LM73606RNPR seems to have more inventory available for their initial board build.
Thanks,
Alan
Part Number:TDC7200
Hi,
I am working on TDC7200 recently. I am using TDC7200 for our LiDAR. I can get a pretty good PointCloud right now.
But we want to discard some of the nearby noise to improve resolution. Is there any way to set a boundary for the ToF result?
What is the meaning of Clock_Counter_Stop_Mask_L register? Can I change the default value to get a better resolution?
Thanks,
Kevin Fan
Part Number:AWR1843BOOST
Tool/software: Linux
Hello,
I tried to follow 
to visualize 2D and 3D point cloud on ros with AWR1843BOOST.
The commands can be successfully send to AWR1843BOOST device, but there are some runtime errors as follows:
(base) pj@pj-K36-Pro:~/catkin_ws$ roslaunch ti_mmwave_rospkg rviz_1843_2d.launch
... logging to /home/pj/.ros/log/9dfa0014-6c65-11e9-a294-f40669d902a1/roslaunch-pj-K36-Pro-29700.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.
started roslaunch server http://pj-K36-Pro:42643/
SUMMARY
========
PARAMETERS
* /mmWave_Manager/command_port: /dev/ttyACM0
* /mmWave_Manager/command_rate: 115200
* /mmWave_Manager/data_port: /dev/ttyACM1
* /mmWave_Manager/data_rate: 921600
* /mmWave_Manager/max_allowed_azimuth_angle_deg: 90
* /mmWave_Manager/max_allowed_elevation_angle_deg: 90
* /rosdistro: kinetic
* /rosversion: 1.12.14
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 [29710]
ROS_MASTER_URI=http://localhost:11311
setting /run_id to 9dfa0014-6c65-11e9-a294-f40669d902a1
process[rosout-1]: started with pid [29723]
started core service [/rosout]
process[mmWave_Manager-2]: started with pid [29731]
process[mmWaveQuickConfig-3]: started with pid [29741]
[ INFO] [1556751931.545529126]: mmWaveQuickConfig: Configuring mmWave device using config file: /home/pj/catkin_ws/src/ti_mmwave_rospkg/cfg/1843_2d.cfg
process[static_tf_map_to_base_radar_link-4]: started with pid [29742]
[ INFO] [1556751931.549503230]: waitForService: Service [/mmWaveCommSrv/mmWaveCLI] has not been advertised, waiting...
process[rviz-5]: started with pid [29753]
[ INFO] [1556751931.560979885]: Initializing nodelet with 8 worker threads.
[ INFO] [1556751931.563951102]: mmWaveCommSrv: command_port = /dev/ttyACM0
[ INFO] [1556751931.563985899]: mmWaveCommSrv: command_rate = 115200
[ INFO] [1556751931.566147408]: mmWaveDataHdl: data_port = /dev/ttyACM1
[ INFO] [1556751931.566183557]: mmWaveDataHdl: data_rate = 921600
[ INFO] [1556751931.566191796]: mmWaveDataHdl: max_allowed_elevation_angle_deg = 90
[ INFO] [1556751931.566217400]: mmWaveDataHdl: max_allowed_azimuth_angle_deg = 90
[ INFO] [1556751931.570333604]: waitForService: Service [/mmWaveCommSrv/mmWaveCLI] is now available.
[ INFO] [1556751931.570394224]: mmWaveQuickConfig: Ignored blank or comment line: '% ***************************************************************'
[ INFO] [1556751931.570410513]: mmWaveQuickConfig: Ignored blank or comment line: '% Created for SDK ver:03.01'
[ INFO] [1556751931.570420628]: mmWaveQuickConfig: Ignored blank or comment line: '% Created using Visualizer ver:3.1.0.1'
[ INFO] [1556751931.570432678]: mmWaveQuickConfig: Ignored blank or comment line: '% Frequency:77'
[ INFO] [1556751931.570446991]: mmWaveQuickConfig: Ignored blank or comment line: '% Platform:xWR18xx'
[ INFO] [1556751931.570458407]: mmWaveQuickConfig: Ignored blank or comment line: '% Scene Classifier:best_range_res'
[ INFO] [1556751931.570469639]: mmWaveQuickConfig: Ignored blank or comment line: '% Azimuth Resolution(deg):15'
[ INFO] [1556751931.570480763]: mmWaveQuickConfig: Ignored blank or comment line: '% Range Resolution(m):0.044'
[ INFO] [1556751931.570492219]: mmWaveQuickConfig: Ignored blank or comment line: '% Maximum unambiguous Range(m):9.02'
[ INFO] [1556751931.570503297]: mmWaveQuickConfig: Ignored blank or comment line: '% Maximum Radial Velocity(m/s):1'
[ INFO] [1556751931.570514434]: mmWaveQuickConfig: Ignored blank or comment line: '% Radial velocity resolution(m/s):0.13'
[ INFO] [1556751931.570525335]: mmWaveQuickConfig: Ignored blank or comment line: '% Frame Duration(msec):100'
[ INFO] [1556751931.570536507]: mmWaveQuickConfig: Ignored blank or comment line: '% Range Detection Threshold (dB):15'
[ INFO] [1556751931.570547704]: mmWaveQuickConfig: Ignored blank or comment line: '% Doppler Detection Threshold (dB):15'
[ INFO] [1556751931.570558520]: mmWaveQuickConfig: Ignored blank or comment line: '% Range Peak Grouping:enabled'
[ INFO] [1556751931.570569766]: mmWaveQuickConfig: Ignored blank or comment line: '% Doppler Peak Grouping:enabled'
[ INFO] [1556751931.570580499]: mmWaveQuickConfig: Ignored blank or comment line: '% Static clutter removal:disabled'
[ INFO] [1556751931.570591672]: mmWaveQuickConfig: Ignored blank or comment line: '% Angle of Arrival FoV: Full FoV'
[ INFO] [1556751931.570602355]: mmWaveQuickConfig: Ignored blank or comment line: '% Range FoV: Full FoV'
[ INFO] [1556751931.570613152]: mmWaveQuickConfig: Ignored blank or comment line: '% Doppler FoV: Full FoV'
[ INFO] [1556751931.570624794]: mmWaveQuickConfig: Ignored blank or comment line: '% ***************************************************************'
[ INFO] [1556751931.570638882]: mmWaveQuickConfig: Sending command: 'sensorStop'
[ INFO] [1556751931.572013326]: mmWaveCommSrv: Sending command to sensor: 'sensorStop'
[ INFO] [1556751931.578118591]: mmWaveCommSrv: Received response from sensor: 'sensorStop
Ignored: Sensor is already stopped
Done
mmwDemo:/>'
[ INFO] [1556751931.579181679]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.579213708]: mmWaveQuickConfig: Sending command: 'flushCfg'
[ INFO] [1556751931.580229398]: mmWaveCommSrv: Sending command to sensor: 'flushCfg'
[ INFO] [1556751931.582894296]: mmWaveCommSrv: Received response from sensor: 'flushCfg
Done
mmwDemo:/>'
[ INFO] [1556751931.583718804]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.583743536]: mmWaveQuickConfig: Sending command: 'dfeDataOutputMode 1'
[ INFO] [1556751931.584726169]: mmWaveCommSrv: Sending command to sensor: 'dfeDataOutputMode 1'
[ INFO] [1556751931.588418780]: mmWaveCommSrv: Received response from sensor: 'dfeDataOutputMode 1
Done
mmwDemo:/>'
[ INFO] [1556751931.589253621]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.589285107]: mmWaveQuickConfig: Sending command: 'channelCfg 15 5 0'
[ INFO] [1556751931.590699476]: mmWaveCommSrv: Sending command to sensor: 'channelCfg 15 5 0'
[ INFO] [1556751931.594180400]: mmWaveCommSrv: Received response from sensor: 'channelCfg 15 5 0
Done
mmwDemo:/>'
[ INFO] [1556751931.595013070]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.595038503]: mmWaveQuickConfig: Sending command: 'adcCfg 2 1'
[ INFO] [1556751931.596143079]: mmWaveCommSrv: Sending command to sensor: 'adcCfg 2 1'
[ INFO] [1556751931.599016149]: mmWaveCommSrv: Received response from sensor: 'adcCfg 2 1
Done
mmwDemo:/>'
[ INFO] [1556751931.599838765]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.599864573]: mmWaveQuickConfig: Sending command: 'adcbufCfg -1 0 1 1 1'
[ INFO] [1556751931.601147650]: mmWaveCommSrv: Sending command to sensor: 'adcbufCfg -1 0 1 1 1'
[ INFO] [1556751931.604891100]: mmWaveCommSrv: Received response from sensor: 'adcbufCfg -1 0 1 1 1
Done
mmwDemo:/>'
[ INFO] [1556751931.605720638]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.605750437]: mmWaveQuickConfig: Sending command: 'profileCfg 0 77 429 7 57.14 0 0 70 1 256 5209 0 0 30'
[ INFO] [1556751931.606726634]: mmWaveCommSrv: Sending command to sensor: 'profileCfg 0 77 429 7 57.14 0 0 70 1 256 5209 0 0 30'
[ INFO] [1556751931.613326202]: mmWaveCommSrv: Received response from sensor: 'profileCfg 0 77 429 7 57.14 0 0 70 1 256 5209 0 0 30
Done
mmwDemo:/>'
[ INFO] [1556751931.614316260]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.620408411]: mmWaveQuickConfig: Sending command: 'chirpCfg 0 0 0 0 0 0 0 1'
[ INFO] [1556751931.622002954]: mmWaveCommSrv: Sending command to sensor: 'chirpCfg 0 0 0 0 0 0 0 1'
[ INFO] [1556751931.626077519]: mmWaveCommSrv: Received response from sensor: 'chirpCfg 0 0 0 0 0 0 0 1
Done
mmwDemo:/>'
[ INFO] [1556751931.626919108]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.626945284]: mmWaveQuickConfig: Sending command: 'chirpCfg 1 1 0 0 0 0 0 4'
[ INFO] [1556751931.628245618]: mmWaveCommSrv: Sending command to sensor: 'chirpCfg 1 1 0 0 0 0 0 4'
[ INFO] [1556751931.632330837]: mmWaveCommSrv: Received response from sensor: 'chirpCfg 1 1 0 0 0 0 0 4
Done
mmwDemo:/>'
[ INFO] [1556751931.633208303]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.633239263]: mmWaveQuickConfig: Sending command: 'frameCfg 0 1 16 0 100 1 0'
[ INFO] [1556751931.634500403]: mmWaveCommSrv: Sending command to sensor: 'frameCfg 0 1 16 0 100 1 0'
[ INFO] [1556751931.638676392]: mmWaveCommSrv: Received response from sensor: 'frameCfg 0 1 16 0 100 1 0
Done
mmwDemo:/>'
[ INFO] [1556751931.639523290]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.644269716]: mmWaveQuickConfig: Sending command: 'lowPower 0 0'
[ INFO] [1556751931.645435104]: mmWaveCommSrv: Sending command to sensor: 'lowPower 0 0'
[ INFO] [1556751931.648482968]: mmWaveCommSrv: Received response from sensor: 'lowPower 0 0
Done
mmwDemo:/>'
[ INFO] [1556751931.649321786]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.649347980]: mmWaveQuickConfig: Sending command: 'guiMonitor -1 1 1 0 0 0 1'
[ INFO] [1556751931.650239746]: mmWaveCommSrv: Sending command to sensor: 'guiMonitor -1 1 1 0 0 0 1'
[ INFO] [1556751931.654417637]: mmWaveCommSrv: Received response from sensor: 'guiMonitor -1 1 1 0 0 0 1
Done
mmwDemo:/>'
[ INFO] [1556751931.655344376]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.655392497]: mmWaveQuickConfig: Sending command: 'cfarCfg -1 0 0 8 4 4 0 1280 1'
[ INFO] [1556751931.656406102]: mmWaveCommSrv: Sending command to sensor: 'cfarCfg -1 0 0 8 4 4 0 1280 1'
[ INFO] [1556751931.660961699]: mmWaveCommSrv: Received response from sensor: 'cfarCfg -1 0 0 8 4 4 0 1280 1
Done
mmwDemo:/>'
[ INFO] [1556751931.661843573]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.661866302]: mmWaveQuickConfig: Sending command: 'cfarCfg -1 1 0 4 2 3 1 1280 1'
[ INFO] [1556751931.663262028]: mmWaveCommSrv: Sending command to sensor: 'cfarCfg -1 1 0 4 2 3 1 1280 1'
[ INFO] [1556751931.667803060]: mmWaveCommSrv: Received response from sensor: 'cfarCfg -1 1 0 4 2 3 1 1280 1
Done
mmwDemo:/>'
[ INFO] [1556751931.668766072]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.668790716]: mmWaveQuickConfig: Ignored blank or comment line: '%peakGrouping 1 0 0 1 114'
[ INFO] [1556751931.668804399]: mmWaveQuickConfig: Sending command: 'multiObjBeamForming -1 1 0.5'
[ INFO] [1556751931.669686200]: mmWaveCommSrv: Sending command to sensor: 'multiObjBeamForming -1 1 0.5'
[ INFO] [1556751931.674124130]: mmWaveCommSrv: Received response from sensor: 'multiObjBeamForming -1 1 0.5
Done
mmwDemo:/>'
[ INFO] [1556751931.674952117]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.674975274]: mmWaveQuickConfig: Sending command: 'clutterRemoval -1 0'
[ INFO] [1556751931.676282795]: mmWaveCommSrv: Sending command to sensor: 'clutterRemoval -1 0'
[ INFO] [1556751931.680009852]: mmWaveCommSrv: Received response from sensor: 'clutterRemoval -1 0
Done
mmwDemo:/>'
[ INFO] [1556751931.680999727]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.681023995]: mmWaveQuickConfig: Sending command: 'calibDcRangeSig -1 0 -5 8 256'
[ INFO] [1556751931.682189218]: mmWaveCommSrv: Sending command to sensor: 'calibDcRangeSig -1 0 -5 8 256'
[ INFO] [1556751931.686718131]: mmWaveCommSrv: Received response from sensor: 'calibDcRangeSig -1 0 -5 8 256
Done
mmwDemo:/>'
[ INFO] [1556751931.687607111]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.687633086]: mmWaveQuickConfig: Sending command: 'compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0'
[ INFO] [1556751931.689053572]: mmWaveCommSrv: Sending command to sensor: 'compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0'
[ INFO] [1556751931.697716280]: mmWaveCommSrv: Received response from sensor: 'compRangeBiasAndRxChanPhase 0.0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
Done
mmwDemo:/>'
[ INFO] [1556751931.698715224]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.698745115]: mmWaveQuickConfig: Sending command: 'measureRangeBiasAndRxChanPhase 0 1.5 0.2'
[ INFO] [1556751931.699974270]: mmWaveCommSrv: Sending command to sensor: 'measureRangeBiasAndRxChanPhase 0 1.5 0.2'
[ INFO] [1556751931.705484152]: mmWaveCommSrv: Received response from sensor: 'measureRangeBiasAndRxChanPhase 0 1.5 0.2
Done
mmwDemo:/>'
[ INFO] [1556751931.706394582]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.706423978]: mmWaveQuickConfig: Sending command: 'aoaFovCfg -1 -90 90 -90 90'
[ INFO] [1556751931.707760389]: mmWaveCommSrv: Sending command to sensor: 'aoaFovCfg -1 -90 90 -90 90'
[ INFO] [1556751931.712010327]: mmWaveCommSrv: Received response from sensor: 'aoaFovCfg -1 -90 90 -90 90
Done
mmwDemo:/>'
[ INFO] [1556751931.712911453]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.712945022]: mmWaveQuickConfig: Sending command: 'cfarFovCfg -1 0 0 8.92'
[ INFO] [1556751931.714015612]: mmWaveCommSrv: Sending command to sensor: 'cfarFovCfg -1 0 0 8.92'
[ INFO] [1556751931.717926154]: mmWaveCommSrv: Received response from sensor: 'cfarFovCfg -1 0 0 8.92
Done
mmwDemo:/>'
[ INFO] [1556751931.718812031]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.718840140]: mmWaveQuickConfig: Sending command: 'cfarFovCfg -1 1 -1 1.00'
[ INFO] [1556751931.720271565]: mmWaveCommSrv: Sending command to sensor: 'cfarFovCfg -1 1 -1 1.00'
[ INFO] [1556751931.724078029]: mmWaveCommSrv: Received response from sensor: 'cfarFovCfg -1 1 -1 1.00
Done
mmwDemo:/>'
[ INFO] [1556751931.724943667]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.724969624]: mmWaveQuickConfig: Sending command: 'sensorStart'
[ INFO] [1556751931.726710574]: mmWaveCommSrv: Sending command to sensor: 'sensorStart'
[ INFO] [1556751931.785719745]: mmWaveCommSrv: Received response from sensor: 'sensorStart
Debug: Init Calibration Status = 0x7fe
Done
mmwDemo:/>'
[ INFO] [1556751931.786733639]: mmWaveQuickConfig: Command successful (mmWave sensor responded with 'Done')
[ INFO] [1556751931.787595645]: mmWaveQuickConfig: mmWaveQuickConfig will now terminate. Done configuring mmWave device using config file: /home/pj/catkin_ws/src/ti_mmwave_rospkg/cfg/1843_2d.cfg
[ INFO] [1556751931.791506111]: Configured DataHandler numRangeBins: 256 numDopplerBins: 16 rangeIdxToM: 0.043602 dopplerResToMps: 0.125224
[ INFO] [1556751931.791896958]: DataUARTHandler Read Thread: Port is open
terminate called after throwing an instance of 'std::out_of_range'
what(): vector::_M_range_check: __n (which is 672) >= this->size() (which is 672)
[mmWaveQuickConfig-3] process has finished cleanly
log file: /home/pj/.ros/log/9dfa0014-6c65-11e9-a294-f40669d902a1/mmWaveQuickConfig-3*.log
[mmWave_Manager-2] process has died [pid 29731, exit code -6, cmd /home/pj/catkin_ws/devel/lib/ti_mmwave_rospkg/ti_mmwave_rospkg mmWaveDataHdl/RScan:=radar/RScan __name:=mmWave_Manager __log:=/home/pj/.ros/log/9dfa0014-6c65-11e9-a294-f40669d902a1/mmWave_Manager-2.log].
log file: /home/pj/.ros/log/9dfa0014-6c65-11e9-a294-f40669d902a1/mmWave_Manager-2*.log
Could you please help me to solve this problem?
Thank you very much!
Best Regards,
PJ
Part Number:CC1200EMK-868-930
Hi,
I am using an ST Nucleo microcontroller to configure and use a CC1200 EM to transmit data to another CC1200EM chip connected to a TrxEB board that is using SmartRF to decode the packets. Depending on which fixed packet length size that I am using, I get more or less of the total data that I am sending. I am using a fixed packet length configuration.
For example, I am sending packet that just have values that count from 0 to 255. If I use a packet of length 6, I only get data from 0 to 114 (19 packets total, expecting ~42 packets). When I use packets of length 15, I get all of the data. And when I use other lengths in between or more than 15, I do not get all of my data. In SmartRF, it looks like the packets with values greater than a certain point (114 in the case of packets of length 6) never get sent or just can't be received for some reason.
My application uses packets of smaller size (less than 10 bytes per packet) and the packets are all the same size, so I want them configured to fixed length size. Is this a known issue or is there some configuration that I am missing to make sure all of my data gets sent. I check for errors by using the command strobe registers and making sure that I got back into transmit mode in the case of TX FIFO errors.
Part Number:AWR1642BOOST
I'm testing driver vital signs with AWR1642.
I am trying to connect to a computer without a usb cable.
1. R169, R166 connected.
2. R128, R129 disconnected.
3. I connected the pins 5 and 7 of J6 to the computer.
4. connected R26.
5. I connected J5's 9th pin to my computer.
Reading data through AR_MSS_LOGGER was successful.
However, sending config value fails.
------------------------------------------------------
sensorStop
flushCfg
dfeDataOutputMode 1
channelCfg 15 3 0
adcCfg 2 1
adcbufCfg -1 0 0 1 0
profileCfg 0 77 7 6 57 0 0 70 1 200 4000 0 0 48
chirpCfg 0 0 0 0 0 0 0 1
frameCfg 0 0 2 0 50 1 0
lowPower 0 1
guiMonitor 0 0 0 0 1
calibDcRangeSig -1 0 0 0 0
vitalSignsCfg 0.3 0.9 256 512 4 0.1 0.05 100000 300000
motionDetection 1 20 2.0 0
sensorStart
-------------------------------------------------------
This is the config value I sent device.
The baud rate is 115200bps and the format is ASCII.
Part Number:TMS320F28377S
Tool/software: TI C/C++ Compiler
Hi.
I don't want to show all the code content to other companies for security reasons.
So, I leave a portion of the code and the rest use only obj files. There is a problem here.
I tried searching, but I could not find a related way.
Who can give me advice?
Part Number:SN74LVC1G123
Hi,
I'm currently having a problem using SN74LVC1G123 -- the output pulse isn't appearing. An image of it in my schematic can be seen below. I would like it to trigger on the falling edge of input A and output a pulse that is a little over 10 us long (I think the application curves place it at roughly 20 us, which is fine).
The "3.3 V" power supply is currently at a little under 3.6 V. The input, measured at TP5, is shown below on the yellow trace (sorry about the phone picture, didn't have a flash drive on me at the time). In both pictures below, the blue trace is the signal INSTR1, which is divided down by 1/4 (R2 has been changed to 301kOhm).
Based on the datasheet, I'm led to believe that this should work fine. The max of the input is 2.3 V (above 2 V), and the min is ~700 mV (below 800 mV). The output, measured at TP7, is shown below.
The output, for whatever reason, is at a DC ~1 V. Can anyone let me know if there's something I'm doing wrong? If more information from my end is needed, let me know and I would be happy to oblige.
Regards,
Michael
Part Number:TPS22968
Does the TPS22968x-Q1 have an expected behavior if VIN/VBIAS pushes past its limits? Does that behavior change based on how far past its limits it goes?
• Input Voltage Range: 0.8 to 5.5 V
• VBIAS Voltage Range: 2.5 to 5.5 V
Part Number:HD3SS3212-Q1
Dear Supporting Staff.
I am trying to use the re-driver TUSB501 with HD3SS3212 for USB type-C application.
As below
Host processor USB 3.0 PHY TX ------------> Cap 100nF ------> TUSB501 ---------------> HD3SS3212 ---------> Cap 100nF -----> USB Type-C connector
Host Processor USB 3.0 PHY RX <----------- Cap 100nF <------- TUSB501<--------------- HD3SS3212<------------------------------- USB Type-C connector
The questions are:
1. The parameter of VCM-TX in TUSB501 is 1.2V(min) to 2.5V (max), also the VCM-RX is 3.3V (Typical), will these common mode voltage exceed the range for HD3SS3212 ? (which the CM input voltage is limited to 0~2V)
2. For the TX path , TUSB501 will detect the cable connection / far side termination periodically after power on, once it detect the termination at far side, then TUSB501 will present 100ohm Termination for Host processor, and , if the cable is then disconnected, will TUSB501 disable the 100ohm termination for Host and back to far side detection mode? (for next connection, even it's USB 2.0 only cable)
appreciated for the help
Regards,
Chenglin WU
Part Number:CC430F5133
I'm working on a key fob that runs off a CR2032 lithium battery and uses the CC430F5133 microcontroller from the MSP430 family. The clock source is an external 32 KHz crystal on XT1.
In normal operation, the current consumption in LPM4 sleep state is 5.5 uA. Every once in a while the sleep current is 8.5 uA.
I have trimmed down the code to the following:
#include <msp430.h>
#include <stdint.h>
#include "HAL_PMM.h"
#define FOB_UBTN0 BIT0
#define FOB_UBTN0_PORT_DIR P1DIR
#define FOB_UBTN0_PORT_SEL P1SEL
#define FOB_UBTN1 BIT1
#define FOB_UBTN1_PORT_DIR P1DIR
#define FOB_UBTN1_PORT_SEL P1SEL
#define FOB_UBTN2 BIT7
#define FOB_UBTN2_PORT_DIR P1DIR
#define FOB_UBTN2_PORT_SEL P1SEL
#define FOB_UBTN3 BIT6
#define FOB_UBTN3_PORT_DIR P2DIR
#define FOB_UBTN3_PORT_SEL P2SEL
#define FOB_VREF_PIN BIT4
#define FOB_VREF_PORT_DIR P2DIR
#define FOB_LED1 BIT4
#define FOB_LED_PORT_DIR P3DIR
#define FOB_LED_PORT_OUT P3OUT
#define FOB_LED_PORT_SEL P3SEL
static void initializePorts(void)
{
P1SEL = 0x00;
P2SEL = 0x00;
P3SEL = 0x00;
P5SEL = 0x00;
P1DIR = 0xFF;
P2DIR = 0xFF;
P3DIR = 0xFF;
P5DIR = 0xFF;
PJDIR = 0xFF;
P1OUT = 0x00;
P2OUT = 0x00;
P3OUT = 0x00;
P5OUT = 0x00;
PJOUT = 0x00;
// Set up port 5 for XIN for XOUT
P5DS |= BIT0+BIT1;
P5OUT |= BIT0+BIT1;
P5SEL |= BIT0+BIT1;
P5DIR &= ~(BIT0+BIT1);
FOB_UBTN0_PORT_DIR &= ~FOB_UBTN0;
FOB_UBTN0_PORT_SEL &= ~FOB_UBTN0;
FOB_UBTN1_PORT_DIR &= ~FOB_UBTN1;
FOB_UBTN1_PORT_SEL &= ~FOB_UBTN1;
FOB_UBTN2_PORT_DIR &= ~FOB_UBTN2;
FOB_UBTN2_PORT_SEL &= ~FOB_UBTN2;
FOB_UBTN3_PORT_DIR &= ~FOB_UBTN3;
FOB_UBTN3_PORT_SEL &= ~FOB_UBTN3;
FOB_VREF_PORT_DIR &= ~FOB_VREF_PIN;
FOB_LED_PORT_OUT &= ~FOB_LED1;
FOB_LED_PORT_DIR |= FOB_LED1;
FOB_LED_PORT_SEL &= ~FOB_LED1;
}
void LFXT_Start(uint16_t xtdrive)
{
UCSCTL6_L |= XT1DRIVE1_L + XT1DRIVE0_L; // Highest drive setting for XT1 startup
while (SFRIFG1 & OFIFG) { // check OFIFG fault flag
UCSCTL7 &= ~(DCOFFG + XT1LFOFFG + XT1HFOFFG + XT2OFFG); // Clear OSC flaut Flags fault flags
SFRIFG1 &= ~OFIFG; // Clear OFIFG fault flag
}
UCSCTL6 = (UCSCTL6 & ~(XT1DRIVE_3)) | (xtdrive); // set Drive mode
}
int main(void)
{
// Watchdog off
WDTCTL = WDTPW + WDTHOLD;
SFRIE1 &= ~WDTIE;
SetVCore(0);
initializePorts();
LFXT_Start(XT1DRIVE_0);
// RTC timer on
RTCCTL01 = RTCTEV0_H;
__bis_SR_register(LPM4_bits);
}
The SetVCode(0) function is from the HAL_PMM.c module from the TI example projects. LFXT_Start() which I show above is also taken directly from the TI demo code.
As you can see, there are no interrupt handlers in this trimmed down code. The code just boots and goes right to sleep and stays asleep.
If I cut battery power then reapply battery power, usually waiting 500-1500 msec in between, once in every 10 or 20 power cycles the sleep current is 8.5 uA. In all other cases the sleep current is 5.5 uA.
In the full product source code (before I whittled it down to what you see above), I have buttons on the fob that wake the CPU, do some processing, then go back to LPM4 sleep state. I can repeat this sequence over and over when the fob is in the "bad" mode and it always goes back to sleep at the higher 8.5 uA sleep current.
However, if while the CPU is awake, I execute ONLY the LFXT_Start() call shown above to reinitalize the clock system, the problem goes away and the next sleep cycle goes back to the desired 5.5 uA sleep current and will stay at the correct sleep current after many wake/sleep cycles.
As another clue, it seems that if I comment out the code that starts the RTC timer, that also makes the problem go away (or makes it really, really hard to reproduce). With the RTC off I tested over 150 power cycles and never saw the higher sleep current.
Can anyone offer some guidance on how to debug this?
Thanks,
Bob
Part Number:CC2640
Hello,
I'm preparing for Continua certification for our glucose meter.
First, what does mean of the Regulatory Certification Data List?
Second, Can I just write it into DIS characteristic with the specific format?
Or should I consider your ble stack meets the IEEE 11073-20601 specification?
Thanks,
Calvin
Part Number:TUSB7320EVM
Can I get the design file schematic and layout in orcad format for TUSB7320EVM?
Thanks
Tuan