↧
TPS65982: TPS65982 HOST Device Setting
↧
Linux/AM3351: AM3351 not detected while connecting to PC through USB
Part Number:AM3351
Tool/software: Linux
Hi,
We made a custom board based on AM3351. I have been trying to flash linux kernel on EMMC through USB/RNDIS using Uniflash and following this link. Initially, my PC detected AM335 as a serial port device. Following the link, I tried installing NDIS driver and then changed the IP address from DHCP to static IP. After changing the IP, my device disappeared. Now, device is neither detected as USB nor RNDIS. Also, I am not seeing any C character on UART which ROM generates. Kindly let me know of a possible solution.
Thanks!
↧
↧
TLV320AIC3106: I2S Input and Line Output
Part Number:TLV320AIC3106
Hello,
I've designed a system to generate Analog Audio Line Out from an I2S Digital Input using TLV320AIC3106.
The schematics page is attached alongside.
Please help me to confirm the following.
1. I2S Input.
2. Use of MCLK, its frequency used.
3. Line Output pins, the reference signal used.
4. GND connections to IC.
Thanks in advance.
Emil Zacharia
↧
CCS/CC2640R2F: RF Software interrupts
Part Number:CC2640R2F
Tool/software: Code Composer Studio
What are the software interrupts available for RF driver and why it was given lowest priority.
If we give it highest priority will it affect the system load.
↧
BQ34Z100-G1: SoC deviation
Part Number:BQ34Z100-G1
Hi,
I am using a BQ34z100-g1 with an 8s2p LiFePO4 batteries. The nominal capacity of the battery is 3200mAh.
I have obtained the golden image of the battery and load it in the bq24z100-g1. I have tested the bq34z100-g1 performance during two weeks in a laboratory functional prototype and I have seen twice an irregular performance.
I did a constant current discharge from 100% SoC(and FC bit set) to 10% SoC. The discharge current was 4.4A.
After reaching 10% I stopped the discharge and the systems went in the standby state (30mA consumption). After a few minutes the SoC was 17%.
- Why did this change occur? I supposed It was due to a capacity simulation.
- What parameters are taking into account in this capacity simulation?
Best regards,
↧
↧
BQ27411-G1: Bq27411-G1A
Part Number:BQ27411-G1
Hi All,
We have selected the BQ27411-G1A FG in our design. Our Battery Characteristics as below.
We are using 2 Cells in parallel. 3.7V/5200mAh battery.
Design Voltage is 3.7V.
Design Capacity is 5200mAh
Design Energy is 19240 mA
Taper rate is 87.
Terminate voltage 3.6V
Hibernate voltage 2.7V
We have configured all other values of bq27411 with typical values
And I calibrate the bq27411 ,complete the learning cycle, export a .otfs file.
Using EV2300 and smartflash V0.7.0 , I manually turn on the 7.4 power and remove the 7.4V power.
Program of Fuel Gauge is successful.
But battery monitoring showing wrong percentages.... When we see in Battery Management Studio.
We have connected the I2C lines of bq27411 to EV2300 and we are monitoring all the values which we programmed.
For example my battery is at 4.2V and percentage is showing as 60%. My battery voltage is 4.0V, percentage is showing as 90%.....etc.
It is completely showing wrong % and it is going up and down....
Could any one help us....
Regards,
Amarendar
↧
TPSM84A21: Input current transient
Part Number:TPSM84A21
Hi,
As far as I could understand (referring to slva750a) the internal switching mechanism of this part is based upon a N steps looping machine, where only 1 step interval is dedicated to energy transfer from Input voltage to output current.
Webench simulations also help to understand that input transfer (hence input current transients) indeed occurs every other clock rising edge. Correct me if I am wrong.
Hi,
As far as I could understand (referring to slva750a) the internal switching mechanism of this part is based upon a N steps looping machine, where only 1 step interval is dedicated to energy transfer from Input voltage to output current.
Webench simulations also help to understand that input transfer (hence input current transients) indeed occurs every other clock rising edge.
My question is related to the fact that we have a lot of DC/DC converters, some of them running at a lower 1Mhz, and we want to control the distribution of input current transient , seen by the Input voltage source (each DC/DC converter being synchronized by its dedicated clock, with dedicated phase delay)
In such case where the part is externally synchronized by a 4Mhz clock, is there a way to know which clock rising edge does correspond to transfer energy from the input voltage ? for example odd rising edges, or even rising edge (counted from the first rising edge appearance of the external 4M clock) ?
with best regards,
Bruno
↧
DAC8814: Abnormal output
Part Number:DAC8814
Conditions of use:
1. SPI control output of DAC8814 through SPARAN6 FPGA of XILINX;
2. DAC88144 channels are used for simultaneous output, of which one channel is converted from single-ended output to differential output.
3. The reference voltage is 10V.
4. The output waveform of the design is amplitude (+10V) and the frequency is 220 KHz square wave.
Schematic diagram:
Principle Diagram of DAC8814 Output Current-to-Voltage Conversion
Principle diagram of DAC8814 output single-ended output to differential output
Output waveform measured by oscilloscope:
Debugging problems:
1. When jumping from + 10V to - 10V, or from - 10V to + 10V (full range jump), there is a jitter within 500 ns or so, as shown in the red circle of the above-illustrated wave, and the amplitude is close to 4V.
2. In steady state, the waveform also has a burr of about 200 mV.
↧
BQ34Z100-G1: Temperature performance
Part Number:BQ34Z100-G1
Hi,
I am using a BQ34z100-g1 with an 8s2p LiFePO4 batteries. The nominal capacity of the battery is 3200mAh.
I have obtained the golden image of the battery and load it in the bq24z100-g1.
I sent my system to a controlled temperature test(1000 hours at a temperature of 85ºC). This test is carried out with the system off. When my device returned I checked it and everything was in perfect state but the Bq34z100-G1, that was damage. It did not respone to any communications and we had to replace it.
- What are the possible causes of this damage?
Bes regards,
↧
↧
CCS/UCD3138: I don't understand PEC_VALID of UCD3138 ?
Part Number:UCD3138
Tool/software: Code Composer Studio
I find the register of PEC_VALID :
PEC Valid Indicator
0 = Received PEC not valid (if EOM is asserted)
1 = Received PEC is valid
the meaning is when received wrong PEC , the PEC_VALID is Low ;when received right PEC , the PEC_VALID is Hi ?
Is PEC verification handled by hardware or software?
The system takes PEC to PSU write byte and no PEC to write word. How is the hardware distinguished?
;
↧
DS90UB913A-Q1: Problem for I2C communication (with DS90UB914A)
Part Number:DS90UB913A-Q1
Question about DS90UC913A and DS90UB914A, these are connecting below block diagram.
But I2C communication for Repeater board to Camera board are occur error.
Is there any adjusting point?
Or, Can't below connection communicate I2C on Repeater board to Camera board?
By the way, unused Repeater board is normal I2C communication.
Best regards,
Satoshi
↧
TXB0104: Level translator drive strength
Part Number:TXB0104
TXB0104ZXUR is driving one of the processor device. The IOH and IOL of the level translator is 20uA, whereas the input current of the processor is 50uA. Will the level translator be able to drive the processor?
↧
RTOS/MSP432P401R: SDFatFS Driver from SimpleLink SDK not working properly
Part Number:MSP432P401R
Tool/software: TI-RTOS
Hello,
I have been using the SDFatFS driver shipped with the last version of SimpleLink SDK for MSP432P401R (simplelink_msp432p4_sdk_2_30_00_14). I have imported the example "fatsd_MSP_EXP432P401R_freertos_ccs" from TI Resource Explorer and modified it to write a large array buffer (16 kbytes), filled with a dummy pattern data (0xAA), to SD Card. I realized that the write speed performance is poor, and then, I have attached a Logic Probe to SPI lines and I discovered even writing a multiple integer of a data block size (512 bytes) the Driver provided by TI is issuing multiples CMD24 (SINGLE DATA BLOCK WRITE) instead of a single CMD25 (MULTIPLE DATA BLOCK WRITE). I looked at the source code provided by TI and I realized that multiple data block (CMD25) is implemented in the TI current driver, but not working for some reason. Is it a possible bug?
The writing of sixteen data blocks is depicted bellow
Zooming around the time that precedes the writing of one of data blocks, the CMD24 can be seen.
I attached the CCS project working out of the box, in order to reproduce the problem, but my code is shown bellow
#include <file.h>
#include <stdbool.h>
#include <stddef.h>
#include <stdint.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <time.h>
/* POSIX Header files */
#include <pthread.h>
#include <third_party/fatfs/ffcio.h>
#include <ti/display/Display.h>
#include <ti/drivers/GPIO.h>
#include <ti/drivers/SDFatFS.h>
/* Example/Board Header files */
#include "Board.h"
/* Buffer size used for the file copy process */
#ifndef CPY_BUFF_SIZE
#define BUFF_SIZE 512*16
#endif
/* String conversion macro */
#define STR_(n) #n
#define STR(n) STR_(n)
/* Drive number used for FatFs */
#define SD_DRIVE_NUM 0
const char outputfile[] = "fat:"STR(SD_DRIVE_NUM)":data.dat";
static Display_Handle display;
/* Set this to the current UNIX time in seconds */
const struct timespec ts = {
.tv_sec = 1469647026,
.tv_nsec = 0
};
/* File name prefix for this filesystem for use with TI C RTS */
char fatfsPrefix[] = "fat";
unsigned char buff[BUFF_SIZE] __attribute__ ((aligned (4)));
/*
* ======== mainThread ========
*/
void *mainThread(void *arg0)
{
SDFatFS_Handle sdfatfsHandle;
/* Variables for the CIO functions */
FILE *dst;
/* Variables to keep track of the file copy progress */
unsigned int bytesWritten = 0;
/* Call driver init functions */
GPIO_init();
Display_init();
SDFatFS_init();
/* Configure the LED pin */
GPIO_write(Board_GPIO_LED0, Board_GPIO_LED_OFF);
/* add_device() should be called once and is used for all media types */
add_device(fatfsPrefix, _MSA, ffcio_open, ffcio_close, ffcio_read,
ffcio_write, ffcio_lseek, ffcio_unlink, ffcio_rename);
/* Open the display for output */
display = Display_open(Display_Type_UART, NULL);
if (display == NULL) {
/* Failed to open display driver */
while (1);
}
/* Initialize real-time clock */
clock_settime(CLOCK_REALTIME, &ts);
Display_printf(display, 0, 0, "Starting the fats application\n");
/* Mount and register the SD Card */
sdfatfsHandle = SDFatFS_open(Board_SDFatFS0, SD_DRIVE_NUM);
if (sdfatfsHandle == NULL) {
Display_printf(display, 0, 0, "Error starting the SD card\n");
while (1);
}
else {
Display_printf(display, 0, 0, "Drive %u is mounted\n", SD_DRIVE_NUM);
}
memset((void*) buff, (int) (0xAA), (size_t) BUFF_SIZE);
/* Create a new file object for the file copy */
dst = fopen(outputfile, "w");
if (!dst) {
Display_printf(display, 0, 0, "Error opening \"%s\"\n", outputfile);
Display_printf(display, 0, 0, "Aborting...\n");
while (1);
}
else {
Display_printf(display, 0, 0, "Starting file write\n");
}
/* Write buff to dst file */
bytesWritten = fwrite(buff, 1, BUFF_SIZE, dst);
if (bytesWritten < BUFF_SIZE) {
Display_printf(display, 0, 0, "Disk Full\n");
}
/* Close outputfile[] */
fclose(dst);
/* Stopping the SDCard */
SDFatFS_close(sdfatfsHandle);
Display_printf(display, 0, 0, "Drive %u unmounted\n", SD_DRIVE_NUM);
return (NULL);
}(Please visit the site to view this file)
↧
↧
CC2640R2F: RTC reliability in CC2640R2F
Part Number:CC2640R2F
Hi all,
Im using RTC to keep track of time in my CC2640R2F device. Im working on OTA code and i need to update the firmware at a particular time in a week or a month.
How reliable and accurate is the RTC in it and how much drift I get when I run for weeks without calibrating the time? I set the device time once using Seconds_set module.
I don't have an external (LFXOSC) crystal oscillator in my circuit and Im not using internal LF RC oscillator(RCOSC_LF) either.
My clock configuration is like this in ccfg.c file,
#ifndef SET_CCFG_MODE_CONF_SCLK_LF_OPTION
// #define SET_CCFG_MODE_CONF_SCLK_LF_OPTION 0x0 // LF clock derived from High Frequency XOSC
// #define SET_CCFG_MODE_CONF_SCLK_LF_OPTION 0x1 // External LF clock
#define SET_CCFG_MODE_CONF_SCLK_LF_OPTION 0x2 // LF XOSC
// #define SET_CCFG_MODE_CONF_SCLK_LF_OPTION 0x3 // LF RCOSC
#endif
But there is no external oscillator in circuit. What frequency or which oscillator will the RTC use in this case? And how reliable is it?
I have read the datasheet in which it is stated to use external LF oscillator or calibrate internal LF oscillator but in my case its not the both.
I have read the following documents and threads but I dont find particular answer to my question.
http://www.ti.com/lit/an/swra499b/swra499b.pdf
http://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/587863
http://www.ti.com/lit/ug/swru393e/swru393e.pdf
Note:
Im using CCS and sdk 1.50
Thanks,
radha.
↧
BQ20Z95: BQ20Z95
↧
TPS92692-Q1: SS Connects 100nF Capacitor to GND
Part Number:TPS92692-Q1
hI
SS Connects 100nF Capacitor to GND.In disable mode, what's the difference between setting PWM duty cycle to zero and lowering SS foot?
↧
IWR1642BOOST: Conformence between Sensing Estimator design and mmWave Studio Post Processing capabilities
Part Number:IWR1642BOOST
Hi,
I'm using the IWR1642BOOST ES2.0 together with the DCA1000 for raw data capturing. I really like the Post Processing tool in mmWave Studio, cause it gives a fast feedback (e.g. when doing field tests) of the performance of a certain setting. In the mmWave Sensing Estimator's user guide it says "After it is designed here, the chirp can be configured on the device through the use of mmWave SDK. Please note that that these parameters only specify the front-end and additional processing may be required to achieve the scene parameters." For my case, so far, I'm only using the IWR1642BOOST to capture raw data, so the chip itself doesn't have to do any additional processing. In my application I would like to measure an object with a velocity around 200 k/h for as long of a distance the system can manage. In the Sensing Estimator I made this chirp:
I'm wondering, would the mmWave Studio Post Processing tool be able to display the data properly, concerning max velocity etc? (if not, what are out of bounds?) Or would I have to do the post processing myself? And if the mmWave Studio Post Processing tool is not capable of this, how do I know its limits?
Thanks!
↧
↧
UCC2895: switching frequency
↧
TPA3111D1: Line Out from TLV320AIC3106 is to be amplified to drive 30W 8ohm speaker- Reference GND to be used?
Part Number:TPA3111D1
Hello,
We wanted to amplify the line out signal generated using TLV320AIC3106 to drive 30W 8E speaker(we donot want to use full power out speaker, so 10W amp used).
I've some confusion regarding the GND connections.
Please check the image of schematics below and let me know if it is fine.
Thanks in advance.
Emil Zacharia George
↧
TMS320F28069: Booting procedure (selecting boot mode)
Part Number:TMS320F28069
Hello from Ubstadt, Germany,
Documents used:
A) TMS320x280x, 2801x, 2804x Boot ROM Reference Guide;
B) TMS320x2806x Piccolo Technical Reference Manual:
==========
Questions:
==========
1.) The booting procedure (using GPIO settings to select boot mode)
is described differently in each document. Both methods cannot be applicable at the same time.
Which of the mentioned documents describes the method correctly?
2.) If the method in document B) applies:
This would require defined values in defined OTP locations -- or ALTERNATIVELY:
GPIO 37 == 1; GPIO 34 == 1; TRST == 0.
==> Is this statement correct?
(By the way: How to place values into the OTP when no software/data has
been loaded so far (device is in delivery state))?
3.) We plan to avoid using the ROM-bootloader. This is, we plan to
download the software via JTAG; then to configure booting to "run to flash"
-- without using the OTP, if this is possible. Is it? (See 2.))?
4.) Two different applications shall be loaded to the µC, one of them being a custom
bootloader (which is currently under work). The second (placed in higher flash sections) is the actual
application.
This means that from the bootloader we must branch *properly* to the application (after downloading
the appl. or after a timeout if no download is desired). How to achieve this branching correctly?
==> Or, in general: What must we keep in mind in order to branch correctly from one independent
application to another one the same board?
Thanks & Greetings
Goetz
Annotation for support members:
Somehow, my email address didn't come through correctly; here it is again:
g.borkowski.ext@bremsenergie.de
↧