Part Number:BQ25703AEVM-732
Hi
I am using BQ25703A for the battery Charger for 5*AA NiMH battery Pack.
When i remove the battery pack the CELL_BATPRESZ does not fall to below 15% of REGN. Datasheet Specify's on page 16.
The Charger does not set the Charge current to 0 when bettery has been removed and BATFET is ON causing the charge Voltage present at VBAT connector.
regards
Babar
Part Number:AM4376
Hi,
Our customers are using QSPI NOR flash memory with 128MB.
QSPI flash is accessed via memory mapped port. In this case, 64MB from 0x30000000 to 0x33FFFFFF can be accessed,
but 64MB above it can not be accessed.
Please tell me how to do to access.
Which of the following is possible?
① Can it be set so that the memory area of 0x04000000 to 0x07FFFFFF of the QSPI flash memory is mapped to the memory area of 0x30000000 to 0x33FFFFFF of AM4378?
② Is it be accessed via the configuration port?
Best Regards,
Shigehiro Tsuda
Part Number:BQ27542-G1
Hello,
I'm working with the bq27542-G1 in a custom design and the SOC values are inaccurate. A golden pack was created initially and the gauge values were fine. We are unsure why the gauge is inaccurate now but we wanted to know if there were a way to correct the gauge in the field. Our MCU is connected to the gauge via I2C. Is there a command we can send to re-calibrate the gauge. We don't have control over the current since it is in a device so we can't calibrate with open circuit or anything like that.
What we are currently seeing is a SOC anywhere from 25%-37% with a battery voltage of around 3.3V. Based on our current draw, we expect this to be around 7 - 13% SOC. Is there anything we can do to tweak the gauge on the fly?
Thanks
Craig
Part Number:TPS1H100-Q1
Hi team,
I would like to improve current sense accuracy using TPS1H100-Q1.
Therefore, I'm considring to calibrate in the system.
The target accuracy is ±1% when load current is over 200mA.
I think that I will be able to cancel the offset by storing the offset current when turning off the switch, is this effective?
If this is effective, then can I cancel the offset temperature drift?
If I know what temperature drift fwithin the range, I can multiply the offset cancellation amount by the temperature coefficient.
If this method is effective, to what extent can the accuracy be improved theoretically?
Best regards,
Tomoaki Yoshida
Part Number:TPS51285B
If in the case of TPS51285B use VREG3 and VREG5 only, disable dual buck controllers, please let me check below if there are any issues.
---------------------------------------------------------
EN1, EN2 => direct connect to ground.
VCLK => connect to ground via a 200ohm resistor.
VBST1, DRVH1, SW1, DRVL1, VO1, FB1, CS1, VBST2, DRVH2, SW2, DRVL2, VO2, FB2, CS2 => floating
---------------------------------------------------------
Best regards,
Satoshi
Part Number:CC2640R2F
Hi Support,
if a customer is using CC2640R2F with external MCU:
Thanks andregards,
Alberto
Part Number:TM4C123GH6PM
Tool/software: Starterware
For a Tiva C series TM4C123GH6PM
I need driver libraries from:
Can you please share the link to it?
Thank you!
Part Number:CC2540
Hello everyone,
I'm trying to use CC2540 to read temperature and humidity from a DHT11 sensor.
This device uses one wire communication. The host (CC2540) must pull the line down for at least 18 ms, then passes control to the sensor.
The bit format is as follows : 50µs low followed by 27µs high -> 0
50µs low followed by 70µs high -> 1
Total data size is 40 bits.
I tried to use input capture (Timer1 and P0_2). I also tried using GPIO interrupt and reading the timer counter at that time in an array.
In both cases the timings correspond to low bits. (50µs low+ 27 µs high).
I used the sensor with another 32 bits MCU and it worked fine.
Is there something I'm missing here?
Thanks in advance.
Part Number:BQ40Z50-R1
What is exactly the short circuit in charge protection (ASCC) ? Is this a protection to limit the charging current to the cells?
Also what is the difference between Overload in discharge and Short circuit in discharge protection?
Part Number:DS90LV047A
Team,
My customer want to use FPGA to connect to LCD(RGB666), is below solution ok for customer to use?
They use DS90LV047A and DS90CR216A here as showed above, the signal between FPGA and DS90LV047A is 4 wire LVTTL, the signal between DS90LV047A and DS90CR216A is 4 wire differential, then the serial signal was converted to parallel signal sent to LCD(RGB666).
Why customer don't use differential signal between FPGA and DS90LV047A is because they need 2.5V supply, the number of IO is not enough, so they use LVTTL signal here. So below are support need:
1. If above solution ok for customer to use?
2. If not, why and any other solution for customer to use here?
Best regards,
Sulyn
Part Number:TPA6211A1
Hi team,
My customer is using the TPA6211A now. and The shutdown pin is damaged. The schematic is below. We also test the shutdown pin, the voltage is 5.6v.It's weird the pin voltage is higher than the VDD. So we want to check the internal circuit of the TPA6211A and find the broken reason. Thanks.
BR
Frank
Part Number:AWR1642
Hi,
I would like to know is there a way to get the Serial Number or chip ID by reading a register. If so, please provide the register name or register address. Thanks a lot.
Lifeng Liu
Part Number:CC2640
Tool/software: Code Composer Studio
I'm trying to make a script to program a CC2640 using command line srfprog. This basically works fine in general. However, if you first read the ble address with: "-t lsidx(0) -r macsecble" and then try to flash with: "-t lsidx(0) -e all -a 0x00000000 -p -f <binary> -c macble=<newaddr> -v -rs pinHib"
It appears to work just fine, in the end after the verify step it says OK, the exit code however is not 0 but 5, which should indicate an error. BTW, if I don't first read the Mac address I generally don't get this problem. I'm using SmartRF Flash Programmer 2 v1.7.2
What does the exit code 5 mean?
Part Number:CC3200
Hi,
I am getting an error : "Connection with Email Server Failed, Check Internet Connection and Retry"
I have gone through this ink and tried but not getting any solution.
demo_config.h -->
//All SMTP defines
#define SMTP_BUF_LEN 100
#define GMAIL_HOST_NAME "smtp.gmail.com"
#define GMAIL_HOST_PORT 465
#define YAHOO_HOST_NAME "smtp.mail.yahoo.com"
#define YAHOO_HOST_PORT 25
#define USER "xxxxxxx@gmail.com"
#define USER_RFC "xxxxxxx@gmail.com"
#define PASS "xxxxxxxxx"
#define RCPT_RFC "yyyyyyyyyy@gmail.com"
#define EMAIL_SUB "Hello from Simplelink!"
main.c -->
Try 1 :
eMailServerSetting.SecurityMethod = SL_SO_SEC_METHOD_SSLV3;
eMailServerSetting.SecurityCypher = SL_SEC_MASK_SSL_RSA_WITH_RC4_128_MD5;
Try 2:
eMailServerSetting.SecurityMethod = SL_SO_SEC_METHOD_TLSV1_2;
eMailServerSetting.SecurityCypher = SL_SEC_MASK_TLS_RSA_WITH_AES_256_CBC_SHA;
Kindly help me.
Regards,
Ankit Suthar
Part Number:AWR1243
Hi everyone,
I am trying to get two chips up in cascaded mode. Therefor I have a few questions about the mmwavelink API. As I understood you can use the deviceMap to determine which device(s) you want to send a certain command to. This works perfectly fine when I am not in cascaded mode, even when configuring both chips at once. However, when in casceded mode, I have to power up the master first, followed by the slave. When I call the power up function for the slave, the API callback to disable the first device is issued by mmwavelink. This puts the master in reset mode - the clock turns off and I am not able to power up the slave.
I guess I am doing something wrong or did not understand how to implement the API callbacks. Do I need two instances of rlClientCbs_t, one for each client? Can they share the same callbacks? Especially the async event callback and its global variables? If it should work with one instance of rlClientCbs_t, why does powering up ones device turns off the other? The mmwavelink code is quite clear about that within the power on function:
/* if driver is already initialized */
if ((RL_NULL != rlDriverData) && (rlDriverData->isDriverInitialized == 1U))
{
/* DeInitialize Device */
retVal += rlDevicePowerOff();
}Ofcourse the driver is already initialized! So what is my mistake? Or is the mmwavelink source code wrong?
Best regards,
Fabian
Part Number:CC1310
Hi,
I'm using a selfmade Board what is, for most parts, compatible with the CC1310 Launchpad. I'm using the sensor example from the simplelink SDK 1.50 where I just changed the Button what is used to associate the sensor, adjusted polling and orphan intervals, change the frequency band to APIMAC_STD_ETSI_863_PHY_3 and turned off security.
As long as the connection is established, everything seems to work fine. The current consumption ist just the expected standby current. When I disconnect the collector (unplug it), the current cunsomption of the sensor goes up to 4.395mA. That's way too much for our low energy application.
I tought, with the latest fix
| SDKSYSAPPS-162 | Fixed the issue where sensor device could not sleep before start event and between scans |
that problem should be solved, but I still have the problem when the connection was lost.
Is there a known workaround or a fix in near future for this issue?
Part Number:LAUNCHXL-F28027F
Tool/software: Code Composer Studio
Using the universal GUI. After uploading the appProgram.out correctly and even being able to Enable System:
Restarting Program Model...
Initializing target : C:\ti\guicomposer\eclipse\workspace\.metadata\.plugins\com.ti.binding.program\appConfig.ccxml
Connecting target: Texas Instruments XDS100v2 USB Debug Probe/C28xx
Loading program: C:\ti\guicomposer\webapps\InstaSPIN_F2802xF_UNIVERSAL\appProgram.out
Enabling Realtime
Running Program...
I keep getting this error:
C28xx: Error (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 5.1.641.0)
I already tried reinstalling the FTDI drivers stored in:
C:\ti\ccsv6\ccs_base\emulation\windows\xds100_drivers\ftdi
I have Windows 10 Education and CCS 6
Part Number:TMS320F28335
Tool/software: Code Composer Studio
Hello,
When I try to run in real time emulation mode I get this error:
Trouble Reading Register ST1:
(Error -1142 @ 0x6)
Device blocked debug access because it is currently executing non-debuggable code. Choose 'Rude Retry' to disable polite mode and force the operation.
(Emulation package 6.0.407.3)
Yesterday it was all fine!
Part Number:CC3200MOD
Hello everyone,
I'm doing some reliability tests on my CC3200 for the self signed certificate that allow my mqtt client to open an SSL connection to one remote server.
I'm trying to verify the lifespan of my certificates modifying the dates on this way:
- on the server with the command: date -s "YYYY-MM-DD HH:MM"
- on the CC3200 with the command: sl_DevSet(SL_DEVICE_GENERAL_CONFIGURATION, SL_DEVICE_GENERAL_CONFIGURATION_DATE_TIME, sizeof(SlDateTime_t),(unsigned char *)(&g_time));
I use these commands to generate the certificates (the certificates are generated with the correct system time):
# Generate a CA certificate valid for 50 years: $ openssl req -out CAroot.pem -new -x509 -days 18250 # this command create CAroot.pem and privkey.pem files. # Generate server certificate/key pair: $ openssl genrsa -out server.key 1024 $ openssl req -key server.key -new -out server.req -days 18250 $ echo 00 > file.srl $ openssl x509 -req -in server.req -CA CAroot.pem -CAkey privkey.pem -CAserial file.srl -out server.pem -days 18250 # these commands create server.key and server.pem files # Translate CA certificate to DER format (to be read from the device): $ openssl x509 -in CAroot.pem -inform PEM -out CAroot.der -outform DER -days 18250
With the above certificates I'm able to connect to the server until 06 february 2036 that is 6684 days from today. Farther from this date, the -461 (connected with certificate date verification error) value will be returned by the sl_Connect() function.
If I generate a certificate valid for 6679 days (that will expire on 02 february 2036) I'm correctly able to connect until 01 feb 2036.
Is this a known limitation of the simplelink driver or is there something wrong with my certificate generation?
Regards,
Rosario