Part Number: BQ27426
Hi BGP team,
Posting this Q on behalf of my customer.
"I am trying to port the driver to our host MCU. One question about the voltage command:
I read the bq27426's technical reference manual. I saw that for the voltage command, the command code is 0x04 and 0x05, however, the sample code [referenced from app note "Battery Management Solutions, Battery Gauges, Gauge Communication"] only read from 0x04. Why is that? What does 0x05 do?"
Thanks,
Lauren
Part Number: TPS65987EVM
Hi,
My customer is having issues flashing the unit through the application customization tool.
Below is the error:
Exception Encountered during SPI Flash to Device:No FTDI I2C channels (I2C_GetNumChannels) detected, exiting....
<type 'exceptions.Exception'>
In the Show Details I get:
Traceback (most recent call last):
File "dialogWindow.pyc", line 3393, in flash_device
File "hw_interface.pyc", line 187, in hw_open
Exception
Under the device manager I can see 4 USB Serial Com ports with no errors and the ports go away when I disconnect the usb cable so it appears the FTDI unit is connected. I am using Windows 7.
I appreciate the support.
Thanks,
Kevin
Part Number: IWR6843
Tool/software: Code Composer Studio
CCS version : 9.2
My typical sequence is launch, group connect and group CPU reset by pressing the reset icon at the group level to reset both cores before loading code, this sequence now requires an additional GUI step compared to previous CCS versions, cannot see the reason why and therefore I am reporting it as a problem. Sequence to recreate below:
Say a previous session had cores grouped. As we know, when you terminate and launch the target, it remembers the grouping and after the launch, it shows the group 1 highlighted as expected. At this point the CPU reset icon hasn't shown up at the Group level [probably not expected to show as I haven't connected yet]. Then I group connect the target, both cores connect. The CPU reset icon at group level still hasn't shown up, even though the Group 1 is still highlighted. Then I move the cursor to Group1 box and click it to select it [and it remains highlighted as before after this step], and the CPU reset icon shows up (also works as expected) and stays until the rest of the session [even if you ungroup and group again]. So there is an additional step here as you can see.
Part Number: CC3220MOD
Hi,
I have been working with CC3200. Will the code that I developed for CC3200 run on CC3220?
Thank you.
Me and my friend, we are working on a project here in our apartment through the communication of two CC1310 through the UART. My friend has already opened two posts and thanks to you we found some chinks to finish it. Now I'm debugging all the code, but I found some anomalies. Right now the WoR Mode works quite well, the two devices communicate with each other by exchanging messages. I have these questions:
1) Using RX-TX in a single device, I find myself as a consumer 1uA. It seems that the transmission is always on. How can I solve this?
2) In the Callback function, I store the packetDataPointer variable inside an MAX_LENGTH array, I try to print this variable out to the callback function, but it doesn't work. Within the function, yes. Why?
3) When I want to send the package, I have the packet value [0] in RF_cmdPropTXAdv.pktLen. I'm sending characters from the serial, so if I send "test" I have 4 characters and this must be the length. So, I opted to use RF_cmdPropTXAdv.pktLen = strlen (myvariable), but with this function it doesn't print anything on the reception.
Can anyone give me some information?
Thanks!
Part Number: TM4C129ENCPDT
Tool/software: Code Composer Studio
We just purchased a new XDS560V2 so that we could debug over the network and it will not talk with our TM4C129ENCPDT boards.
We have 3 XDS220's (with CodeComposer 9.1) and they all work fine to debug the TM4C129ENCPDT boards - but the XDS560V2 fails. Further, we use the same 14-pin connector to attach the XDS560V2 that we use on XDS220 with all wires verified.
We get the following error:
...
The controller has a version number of '6' (0x00000006).
The controller has an insertion length of '0' (0x00000000).
The cable+pod has a version number of '8' (0x00000008).
The cable+pod has a capability number of '7423' (0x00001cff).
This utility will attempt to reset the controller.
A error occurred while attempting to reset the controller.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-181' (0xffffff4b).
The title is 'SC_ERR_CTL_NO_TRG_CLOCK'.
The explanation is:
The controller has detected a dead JTAG clock.
The user must turn-on or connect the JTAG clock for the target.
[End: Spectrum Digital XDS560V2 STM USB Emulator_0]
Can you give us any guidance?
Thanks.
Part Number: CC3120
Hi,
I recently take over a design with CC3120. the image is generated by other engineer without leaving any documents. I'v gone through TI product page and this forum, I am getting confused about UniFlash with CC3120. Can someone answer the questions below:
Thanks,
Jeff
Part Number: IWR6843
Tool/software: Code Composer Studio
CCS version : 9.2 on windows 10
Check for updates pops up a window showing error, below is copy-paste after clicking "Details":
"No repository found at http://www.blackhawk-dsp.com/updates/ccsv9. while continuing to show the "available updates" window [shows a TI C2000 device support version update]. I ignore the warning but I assume the link is obsolete as going there does not resolve it. I don't need any updating of blackhawk drivers presently so it is not a blocker but I wanted to inform.
Part Number: LT1013-DIE
I have a customer troubleshooting a design that0 uses the TI LT1013-DIE. They are operating the amplifier in an non-inverting configuration with a gain of 2. They are experiencing distortion on the output at -55C. It resembles crossover distortion, however it is not occurring at the zero crossing.
The operating frequency is 3.2KHz, the output voltage is 2Vrms full scale. The supply voltages are +/-5VDC.
Do you have any insight into this behavior? Since the die are only tested at 25C, are there temp guardbands in place to ensure known good die at 25C are functional and in spec across temp?
Thanks.
Part Number: AM3357
Hello, I am trying to get our RGMII interfaces running. below you will find my device tree, some bootup logs and cmd line output. But when use an oscope to look for the 25MHz tx_clk, i get nothing. From the other side i do get rx_clk since the other device is working properly.
Thanks for any help
Logs:
[ 1.038721] libphy: Fixed MDIO Bus: probed
[ 1.061055] cpsw 4a100000.ethernet: Detected MACID = 04:79:b7:02:9c:c4
[ 1.068485] cpsw 4a100000.ethernet: initialized cpsw ale version 1.4
[ 1.075154] cpsw 4a100000.ethernet: ALE Table size 1024
[ 1.080743] cpsw 4a100000.ethernet: cpts: overflow check period 500 (jiffies)
[ 1.089962] cpsw 4a100000.ethernet: cpsw: Detected MACID = 04:79:b7:02:9c:c6
/ # ifdown -a
/ # ifup -a
[ 177.375341] net eth0: initializing cpsw version 1.12 (0)
[ 177.383541] libphy: PHY 4a100000.ethernet:mdio:02 not found
[ 177.389403] net eth0: phy "4a100000.ethernet:mdio:02" not found on slave 0, err -19
[ 177.445955] net eth1: initializing cpsw version 1.12 (0)
[ 177.454214] libphy: PHY 4a100000.ethernet:mdio:03 not found
[ 177.460080] net eth1: phy "4a100000.ethernet:mdio:03" not found on slave 1, err -19
/ # [ 179.216375] smsc95xx 2-1:1.0 eth2: link up, 100Mbps, full-duplex, lpa 0xCDE1
/ # ifconfig
eth0 Link encap:Ethernet HWaddr 04:79:B7:02:9C:C4
inet addr:192.168.45.45 Bcast:0.0.0.0 Mask:255.255.255.254
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:43
eth1 Link encap:Ethernet HWaddr 04:79:B7:02:9C:C6
inet addr:192.168.55.55 Bcast:0.0.0.0 Mask:255.255.255.254
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
eth2 Link encap:Ethernet HWaddr 2E:FC:FA:D3:30:69
inet addr:172.16.1.9 Bcast:0.0.0.0 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4612 (4.5 KiB) TX bytes:0 (0.0 B)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
/ #Here is my am335x-evm.dts:
cpsw_enet1: cpsw_enet1 {
pinctrl-single,pins = <
/* Slave 0 */
AM33XX_IOPAD(0x914, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txen.rgmii1_tctl */
AM33XX_IOPAD(0x918, PIN_INPUT_PULLUP | MUX_MODE2) /* mii1_rxdv.rgmii1_rctl */
AM33XX_IOPAD(0x91c, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd3.rgmii1_td3 */
AM33XX_IOPAD(0x920, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd2.rgmii1_td2 */
AM33XX_IOPAD(0x924, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd1.rgmii1_td1 */
AM33XX_IOPAD(0x928, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* mii1_txd0.rgmii1_td0 */
AM33XX_IOPAD(0x92c, PIN_OUTPUT_PULLUP | MUX_MODE2) /* mii1_txclk.rgmii1_tclk */
AM33XX_IOPAD(0x930, PIN_INPUT_PULLDOWN | MUX_MODE2) /* mii1_rxclk.rgmii1_rclk */
AM33XX_IOPAD(0x934, PIN_INPUT_PULLUP | MUX_MODE2) /* mii1_rxd3.rgmii1_rd3 */
AM33XX_IOPAD(0x938, PIN_INPUT_PULLUP | MUX_MODE2) /* mii1_rxd2.rgmii1_rd2 */
AM33XX_IOPAD(0x93c, PIN_INPUT_PULLUP | MUX_MODE2) /* mii1_rxd1.rgmii1_rd1 */
AM33XX_IOPAD(0x940, PIN_INPUT_PULLUP | MUX_MODE2) /* mii1_rxd0.rgmii1_rd0 */
/* Slave 1 */
AM33XX_IOPAD(0x840, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* gpmc_a0.rgmii2_tctl */
AM33XX_IOPAD(0x844, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_a1.rgmii2_rctl */
AM33XX_IOPAD(0x848, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* gpmc_a2.rgmii2_td3 */
AM33XX_IOPAD(0x84C, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* gpmc_a3.rgmii2_td2 */
AM33XX_IOPAD(0x850, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* gpmc_a4.rgmii2_td1 */
AM33XX_IOPAD(0x854, PIN_OUTPUT_PULLDOWN | MUX_MODE2) /* gpmc_a5.rgmii2_td0 */
AM33XX_IOPAD(0x858, PIN_OUTPUT_PULLUP | MUX_MODE2) /* gpmc_a6.rgmii2_tclk */
AM33XX_IOPAD(0x85C, PIN_INPUT_PULLDOWN | MUX_MODE2) /* gpmc_a7.rgmii2_rclk */
AM33XX_IOPAD(0x860, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_a8.rgmii2_rd3 */
AM33XX_IOPAD(0x864, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_a9.rgmii2_rd2 */
AM33XX_IOPAD(0x868, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_a10.rgmii2_rd1 */
AM33XX_IOPAD(0x86C, PIN_INPUT_PULLUP | MUX_MODE2) /* gpmc_a11.rgmii2_rd0 */
>;
};
cpsw_enet2: cpsw_enet2 {
pinctrl-single,pins = <
/* Slave 0 */
AM33XX_IOPAD(0x914, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_txen.rgmii1_tctl */
AM33XX_IOPAD(0x918, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_rxdv.rgmii1_rctl */
AM33XX_IOPAD(0x91c, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_txd3.rgmii1_td3 */
AM33XX_IOPAD(0x920, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_txd2.rgmii1_td2 */
AM33XX_IOPAD(0x924, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_txd1.rgmii1_td1 */
AM33XX_IOPAD(0x928, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_txd0.rgmii1_td0 */
AM33XX_IOPAD(0x92c, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_txclk.rgmii1_tclk */
AM33XX_IOPAD(0x930, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_rxclk.rgmii1_rclk */
AM33XX_IOPAD(0x934, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_rxd3.rgmii1_rd3 */
AM33XX_IOPAD(0x938, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_rxd2.rgmii1_rd2 */
AM33XX_IOPAD(0x93c, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_rxd1.rgmii1_rd1 */
AM33XX_IOPAD(0x940, PIN_INPUT_PULLDOWN | MUX_MODE7) /* mii1_rxd0.rgmii1_rd0 */
/* Slave 1 */
AM33XX_IOPAD(0x840, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a0.rgmii2_tctl */
AM33XX_IOPAD(0x844, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a1.rgmii2_rctl */
AM33XX_IOPAD(0x848, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a2.rgmii2_td3 */
AM33XX_IOPAD(0x84C, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a3.rgmii2_td2 */
AM33XX_IOPAD(0x850, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a4.rgmii2_td1 */
AM33XX_IOPAD(0x854, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a5.rgmii2_td0 */
AM33XX_IOPAD(0x858, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a6.rgmii2_tclk */
AM33XX_IOPAD(0x85C, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a7.rgmii2_rclk */
AM33XX_IOPAD(0x860, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a8.rgmii2_rd3 */
AM33XX_IOPAD(0x864, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a9.rgmii2_rd2 */
AM33XX_IOPAD(0x868, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a10.rgmii2_rd1 */
AM33XX_IOPAD(0x86C, PIN_INPUT_PULLDOWN | MUX_MODE7) /* gpmc_a11.rgmii2_rd0 */
>;
};
&mac {
status = "okay";
pinctrl-names = "default", "sleep";
pinctrl-0 = <&cpsw_enet1>;
pinctrl-1 = <&cpsw_enet2>;
};Here is am335x.dtsi:
mac: ethernet@4a100000 {
compatible = "ti,am335x-cpsw","ti,cpsw";
ti,hwmods = "cpgmac0";
clocks = <&cpsw_125mhz_gclk>, <&cpsw_cpts_rft_clk>;
clock-names = "fck", "cpts";
cpdma_channels = <8>;
ale_entries = <1024>;
bd_ram_size = <0x2000>;
mac_control = <0x20>;
slaves = <2>;
active_slave = <0>;
cpts_clock_mult = <0x80000000>;
cpts_clock_shift = <29>;
reg = <0x4a100000 0x800
0x4a101200 0x100>;
#address-cells = <1>;
#size-cells = <1>;
/*
* c0_rx_thresh_pend
* c0_rx_pend
* c0_tx_pend
* c0_misc_pend
*/
interrupts = <40 41 42 43>;
ranges;
syscon = <&scm_conf>;
status = "disabled";
dual_emac; // Must be set. Enables two slaves, switch VLAN support.
davinci_mdio: mdio@4a101000 {
compatible = "ti,cpsw-mdio","ti,davinci_mdio";
#address-cells = <1>;
#size-cells = <0>;
ti,hwmods = "davinci_mdio";
bus_freq = <1000000>;
reg = <0x4a101000 0x100>;
status = "disabled";
};
fake_mdio: mdio {
// This is just a bogus phandle that doesn't load any driver.
compatible = "";
#address-cells = <1>;
#size-cells = <0>;
};
//To get "fixed-link", 'Fake PHY' support, see:
// e2e.ti.com/.../367068
// Using patches from above comment.
cpsw_emac0: slave@4a100200 {
phy_id = <&fake_mdio>, <2>; // Fake PHY, 2 to distinquish from any physical phy.
phy-mode = "rgmii"; // Desired.
fixed-link = <1 100 0 0>; // 100Mbs operation.
dual_emac_res_vlan = <1>;
/* Filled in by U-Boot */
mac-address = [ 00 00 00 00 00 00 ];
};
cpsw_emac1: slave@4a100300 {
phy_id = <&fake_mdio>, <3>; // Fake PHY, 3 to distinquish from any physical phy.
phy-mode = "rgmii"; // Desired.
fixed-link = <1 100 0 0>; // 100Mbs operation.
dual_emac_res_vlan = <2>;
/* Filled in by U-Boot */
mac-address = [ 00 00 00 00 00 00 ];
};
phy_sel: cpsw-phy-sel@44e10650 {
compatible = "ti,am3352-cpsw-phy-sel";
reg= <0x44e10650 0x4>;
reg-names = "gmii-sel";
};
};
Part Number: ADS1299EEGFE-PDK
I have an ADS1299EEG FE Rev A board and I am trying to use it as an ECG front end.
I have three electrodes attached to a person with this placement.
They are connected to the ADS1299 through the J6 jumpers like so:
I collected data for 30 seconds with the following Channel Registers configuration.
The data gathered was periodic and the LA signal had a higher amplitude than the RA signal which made sense, but the frequency was really high.
While the average resting heart rate is 60 bpm or 1 Hz the signal I collected reported had a frequency of 60 Hz.
When I looked at the scope tab I saw that the signal did in fact have a very high frequency and the peaks were ~30 samples apart.
I'm not familiar with this hardware so I'm unsure if this is a mistake or if I should be performing some kind of post processing on the data.
Any suggestions on why I am getting such and odd recording?
Part Number: SN6505B
Team-
I know that it is possible to use cascode transistors with the SN6501 (see PMP30440) to extend the input voltage range > 5V.
I'd like to do the same with SN6505B, see below. Any problems with this? Tina simulation attached.
Thanks, Best, Steve
(Please visit the site to view this file)
Part Number: DP83867CS
Hello, I'm reading the datasheet on the DP83867 on page 26 it says a 5-bit address is used to distinguish the PHY. Furthermore, it says that at power-up reset the PHY latches in the PHY_ADD config pins to determine the address. Looking on page 37 is only shows PHY_ADD0 - PHY_ADD3 which is only 4-bits not five. What am I missing here? Where is the fifth bit?
Thank you,
Joe
Part Number: TM4C1294KCPDT
Hello,
We have been using the TiVa series for a while, and are now working on a new thing with IoT. Is there a device similar to the TM4C1294 that also meets as many of the below requirements as possible?
Thanks for the help!
Best,
Adam
Part Number: UCC28742
Tool/software: WEBENCH® Design Tools
I am needing an output of 15Vdc at 1.3Adc.
With no load everything looks fine with the output at 15.3Vdc.
A load of 150 ohm causes the output voltage rise (almost too high, but ok) to 15.9Vdc. Absolute max that can be tolerated is 16Vdc.
A load of 15 ohm causes the output voltage to fall to 6Vdc which is unacceptable.
I need the output voltage to remain at least 14.5Vdc min at 1.3Adc and the absolute maximum the output voltage can go is 16Vdc, but I would prefer it remain up to 15.5Vdc.
Any idea why the output voltage is falling down to 6Vdc when I setup my calculations to have short circuit current at 1.5A. A 15 ohm load should not be near the Iocc_target?
I tried also changing my Rcs resistor from 4.7ohm down to ~4ohm and the changes were as follows:
15.3Vdc - no load
16.3Vdc - 150ohm load -- Unacceptable (too high)
8.93Vdc - 15 ohm load -- higher than 6Vdc, but still no where near 14.5Vdc?
Regards,
Clint
Part Number: BQ25887
Hello,
I have a quick question regarding the BQ25887. On page 6 of the datasheet under "7.3 Recommended Operating Conditions" there is a maximum rating listed for "RMS discharging current with internal MOSFET" given as 5 A. What exactly does this mean, and which internal MOSFET is the datasheet referring to?
To elaborate on my confusion, I was under the impression that the system to be powered would be directly connected to the two series battery cells (i.e. the BAT pin node). So in my mind, I don't see how the BQ25887 would limit discharge current, since the battery is discharging directly to the system to be powered. For my application, I have two batteries capable of delivering 6 A of current, and I'd like to ensure that current level is achievable with the BQ25887.
Thank you,
Thomas
Part Number: TPS65987D
Hi Team,
My customer is trying to use GPIO 12 and 13 to detect the presence of a DP signal. Currently, one is mapped to "Port 0 DP Mode Select Event" and the other is mapped to "Port 0 DP or USB3 Event." The other settings are all default.
Their setup is currently passing DP through the EVM to a display, but when probing GPIO 12 and 13, they aren't seeing a high output. Do one of the other boxes need to be checked or another setting changed?
Thanks,
Michael
Part Number: LMG5200
Hello,
LMG5200 is made of three dies : one driver die and two GANFET dies. I would like to know the reference of the driver used Inside this part ?
Thank you !!
Francois
Part Number: CC1310
Hi,
We want to interface CC1310 with external 32 bit host microcontroller and run CC1310 in network coprocessor mode. There is an example for linux based system. But there is no example for any other MCU. I found http://dev.ti.com/tirex/content/simplelink_cc13x0_sdk_1_40_00_10/docs/ti154stack/ti-15.4-stack-cop-interface-guide.pdf which shows software command interface. Is there any API library than can be integrated with host code?
Thanks
Vishal
Part Number: AWR1443BOOST
Hi,
I have an AWR1443BOOST ES3.0, and am using Industrial Toolbox 4.0.1 from CCS 9.1.0. Reading the documentation for the vital signs lab, I have become very confused as to what version of the mmWaveSDK I should be using. The Vital Signs Developer's Guide suggests that the latest version of the SDK is required. The Vital Signs Lab's release notes states that mmWave SDK 2.1 is required. I have tried and failed to run the with both of these and am already getting some assistance with it in this post: https://e2e.ti.com/support/tools/ccs/f/81/t/845743#pi320995=2. Finally, "C:\ti\mmwave_industrial_toolbox_4_0_1\labs\vital_signs\14xx_vital_signs\gui" suggests that the GUI supports mmWave SDK 1.2.0.5.
I would like to know which version should be used, and how anyone is expected to know, for sure and without trial and error to select a specific version of the SDK? Judging from the first suggestions on many different forum posts, a lot of people have run into this same issue of not knowing which version of the SDK to use.
Thanks in advance,
Aarjav
Edit: attached the files that I have been referring to. Please note that all of these files were obtained from Industrial Toolbox 4.0.1 (current latest version)
(Please visit the site to view this file)
(Please visit the site to view this file)
(Please visit the site to view this file)