BQ27520-G4: GG file

June 6, 2019, 12:42 am

≫ Next: CCS/TMS320F28069: Interfacing 4X20 LCD with TMS320f28069

≪ Previous: TAS5411-Q1: VOH and VOL of MUTE port

Part Number:BQ27520-G4

Hi team,

My customer considers employing BQ27520YZFT-G4 for 4.1 full charge voltage battery circuit and provided some questions.

[Problems]

Problems occurs when setting battery capacity value as follows when Golden File created

4.1V Charging(2800mAh)
→ File generation is passed, but when actually incorporated and used, as the learning of BQ27520YZFT-G4 progresses, FAC / FCC values decrease.
(2500 mAh before learning →　2100 mAh after learning: 25% decreased from inherent ability)
4.2V Charging(3350mAh)
→ The result of learning cycle is not good after creating file.
(Update Status does not show "1" at SLUA902 Gauge set up and Golden file generation 2.6 Leaning Cycle Step.3

[Questions]

1. Could you provide any advice about decrease of capacity after learning when setting 4.1V capacity applying for 4.1V charging circuit?

2.. What if the customer uses Golden File which doesn't change update status to 1 as mentioned above, what kind of risk can be considered?

I look forward to hearing back from you.

Best regards,
Shota Mago

↧

CCS/TMS320F28069: Interfacing 4X20 LCD with TMS320f28069

June 6, 2019, 12:43 am

≫ Next: CC2530: How to design a message exchange interface between RF module with Z-Stack and the host MCU

≪ Previous: BQ27520-G4: GG file

Part Number:TMS320F28069

Tool/software: Code Composer Studio

Hi,Myself Mihir i am working on one project related to TMS320F28069. and i want to interface LCD with it.so,please anyone can guide me how to do it?

↧

CC2530: How to design a message exchange interface between RF module with Z-Stack and the host MCU

June 6, 2019, 12:45 am

≫ Next: TPS7A85A: About the test condition with Bias voltage

≪ Previous: CCS/TMS320F28069: Interfacing 4X20 LCD with TMS320f28069

Part Number:CC2530

I am working on the project where ZED is implemented in the form of CC2530 as RF module and another MCU as a host. I am using one of the sample projects for ZED from the HomeAutomation directory provided with the Z-Stack 3.0.2 package. It fits perfectly for my application from a Zigbee interface perspective as I don't have to implement Zigbee standard interface management, for example, binding, in the host MCU connected through the UART to the RF module and interacting with it through MT interface commands. I have defined all the required attributes in the zcl_samplethermostat_data.c header. However, I still have to receive and transmit data from the host MCU. I have just modified the sample code slightly to send the MT_AF_INCOMING_MSG message to the host through the serial interface to process the application data by the host (apart from processing ZCL frames at the endpoint internally in the RF module). To send data to another node over Zigbee interface, I use AF_DATA_REQUEST with ZCL Write Attribute command sent from the host MCU. Unfortunately, in this case, the corresponding attributes in the RF module are not updated and report old value upon receiving ZCL Read Attributes command from ZC.

Below I have described the current situation.

Message exchange using ZCL Write Attributes from ZC to ZED:

ZC sends attribute value to ZED over Zigbee.
ZED's RF module receives attribute value, updates its internal variable, and passes data to the ZED's host MCU using MT_AF_INCOMING_MSG over UART.
ZED's host MCU receives MT_AF_INCOMING_MSG and updates its internal variable accordingly.

Message exchange using ZCL Write Attributes from ZED to ZC:

ZED's host MCU sends AF_DATA_REQUEST ZED's with ZCL Write Attributes command to ZED's RF module over UART.
ZED's RF module sends attribute value from host to ZC without updating its internal variable.

Although this would be sufficient for most of the cases, I need to support reading attributes as well to comply with the Zigbee standard and to unlock other use cases.

Message exchange by reading attributes from ZED by ZC:

ZC sends ZCL Read Attributes command to ZED.
ZED's RF module responds with ZCL Read Attributes Response carrying the value stored in its own variables.

The problem is that ZED's host MCU variable can contain a different value from the one stored in the ZED's RF module. Same about reporting, where I don't want to involve host MCU as well.

What is the best way to resolve this problem? I see the following options but open to consider others as I might miss something:

Modify ZED's RF module source code in the way that its internal variables are updated upon receiving the AF_DATA_REQUEST from the ZED's host MCU. Not sure if it will trigger redundant reporting of the change in case of the binding.
Implement custom messages just for the purpose to synchronize data between ZED's RF module and ZED's host MCU. Looks like something I should have done from the beginning.

↧

TPS7A85A: About the test condition with Bias voltage

June 6, 2019, 12:46 am

≫ Next: UCC28180: UCC28180 IC disable question

≪ Previous: CC2530: How to design a message exchange interface between RF module with Z-Stack and the host MCU

Part Number:TPS7A85A

There is thing I want to check.

Regarding the drop voltage specification of TPS7A85A [Electrical Characteristics], the test condition with Vbias is Vias = 5.0V.
Figure 26 shows a graph. It is Vbias = 3.3V.
Is this just a different test condition?
Also, is it correct that there is no significant change in the graph in Figure 26 at Vbias = 3.3V or 5.0V?

Regard

T Kishi

↧

UCC28180: UCC28180 IC disable question

June 6, 2019, 12:46 am

≫ Next: RTOS/66AK2G12: USB FIFO configurations

≪ Previous: TPS7A85A: About the test condition with Bias voltage

Part Number:UCC28180

Hi Support team

i would like to learn more about the protection of UCC28180, I would like to know if pull Vsense on the application (will the duty increase before protection?) or Icomp will be better. ? In addition, in standby mode, does the IC have other functions besides PWM?

↧

RTOS/66AK2G12: USB FIFO configurations

June 6, 2019, 12:47 am

≫ Next: DS90UB954-Q1: MIPI output issue

≪ Previous: UCC28180: UCC28180 IC disable question

Part Number:66AK2G12

Tool/software: TI-RTOS

Hello,

My customer would like to confirm the USB FIFO configuration in PDK implementation.

Please take a look at C:\ti\pdk_k2g_<latest version>\packages\ti\drv\usb\src\dwc\usb_dwc_dcd.c

void usbDwcDcdSetConfiguration(usbDwcDcdDevice_t *dwc3)
{
    uint32_t bulkInFifoSize, ep0CtrlMps, epBulkMps;
    volatile uint32_t regVal;

    tDeviceInfo*        ptDeviceInfo;

    /* This has to be done based on the speed */
    /* Check this logic */
    bulkInFifoSize = ((2U * (1024U + 8U) + 8U) / 8U);
    ep0CtrlMps = 64U;
    epBulkMps = 512U;

Here, it seems like the FIFO size hard-corded by ((2U * (1024U + 8U) + 8U) / 8U). And bulkInFifoSize will be used to configure USB related registers.

    regVal = HW_RD_REG32(dwc3->baseAddr + DWC_USB_GTXFIFOSIZ1);
    HW_SET_FIELD(regVal, DWC_USB_GTXFIFOSIZ0_TXFSTADDR, 66U);
    HW_SET_FIELD(regVal, DWC_USB_GTXFIFOSIZ0_TXFDEP, bulkInFifoSize);
    HW_WR_REG32(dwc3->baseAddr + DWC_USB_GTXFIFOSIZ1, regVal);

    regVal = HW_RD_REG32(dwc3->baseAddr + DWC_USB_GTXFIFOSIZ2);
    HW_SET_FIELD(regVal, DWC_USB_GTXFIFOSIZ0_TXFSTADDR, 66U + 256U);
    HW_SET_FIELD(regVal, DWC_USB_GTXFIFOSIZ0_TXFDEP, bulkInFifoSize);
    HW_WR_REG32(dwc3->baseAddr + DWC_USB_GTXFIFOSIZ2, regVal);

Considering the macro definitions, these registers would be :

0x0269C304U and 0x0269C308U for USB0
0x0259C304U and 0x0259C308U for USB1

I don`t know whether these are TI specific registers or USB IP Core registers. Can you comment ?

Some background:

They had a trouble with USB Audio and MSC composite operation with their USB driver code, which is based on TI PDK example. The driver worked basically, but sometimes, something error raised in runtime. And if they changed the FIFO size configuration (bulkInFifoSize in TI driver code), it seemed the error did not happen. So they want to know the reason for that.

As you see in the original post, I understand that there is no USB related information in TRM. And we need NDA with USB IP vendor for further information. As for TI wrapper registers, I understand these should be exactly same configuration with TI examples (Ex. PDK or Linux driver implementation). Unfortunately, my customer does not have NDA for now. They are finding right parson to have NDA with IP vendor to get the IP document and understand why the error does not happen by changing the above registers. But, you know, these registers might be TI related registers. So I`m asking if the above registers are TI part or IP vendor part.

Best Regards,
NK

↧

DS90UB954-Q1: MIPI output issue

June 6, 2019, 1:55 am

≫ Next: LMP92066: Recommend operating coditions for pressure

≪ Previous: RTOS/66AK2G12: USB FIFO configurations

Part Number:DS90UB954-Q1

Hi Teams,

I'm using 913 send 10bit RAW video to 954, and generate MIPI data to video grabber. But our backend grabber cannot recognize this MIPI data packet.

I cross check with another camera, it seems to have some differences at the end of the data packet.

Please let me know any else I can try.

Thanks.

Imager: 1300*1000px 10bit DVP 96MHz PCLK

Serializer: 913A

+STP cable

Deserializer: 954 port1

Setting

Deserialzer:

0x1f,0x03 //400mbps per lane

0x33,0x03 //4lane, continous clk

0x20,0x10 //Enabled FWD for RX Port 1, disabled FWD for RX Port 0

0x4c,0x12 //FPD3_PORT_SEL port1

(pass throuth/I2C alias)

0x7c,0x01 // FV,LV setting

0x70,0x6b // RAW10 DT

0x6d,0x73 // 913A 10-bit STP mode

0x10,0xc5 //Enable 954 GPIO0,1 OUTPUT FV and LV 0x11,0xe5

Serializer:

0x05,0x25 //10bit mode

Current status:

PASS, LOCK : high

No forward channel parity error

913 PCLK detect: STABLE HIGH

0x73,0x74 = DEC1300 line

0x75,0x76 = DEC 2000 byte

No CRC error occurs on backend grabber

HSYNC, VSYNC output on 954

MIPI dat

Camera B is a 12bit camera, using 913 and coax.

It can be displayed on the same backend grabber via 954.

↧

LMP92066: Recommend operating coditions for pressure

June 6, 2019, 2:01 am

≫ Next: TAS5825M: GPIO MUTE

≪ Previous: DS90UB954-Q1: MIPI output issue

Part Number:LMP92066

Hello support team,

I have a question regarding LMP92066.

Our customer might use this IC under low temperature and reduced pressure environment.
Although recommended operating condition for ambient temperature is specified in datasheet, are there any recommended operating condition for barometric pressure as an IC?
If you have such data, please let us know.

The conditions assumed by the customer are as follows.
Balometric pressure: about 500 hPa
Temperature: -20 ° C (minimum)

Sincerely,
M. Tachibana

↧

TAS5825M: GPIO MUTE

June 6, 2019, 2:04 am

≫ Next: CCS/CC2650: Is there a way to send the 32.768 kHz crystal clock output to any pin?

≪ Previous: LMP92066: Recommend operating coditions for pressure

Part Number:TAS5825M

Hi,

A customer asked to us about the operating supply voltage range of GPIO mute set by GPIO_MUTEZ_SEL field of GPIO_INPUT_SEL Register.
He seems to be trying to create a GPIO mute signal in hardware triggered by a power down.
Is GPIO mute operated by DSP processing?

Best regards,
Akio Ito

↧

CCS/CC2650: Is there a way to send the 32.768 kHz crystal clock output to any pin?

June 6, 2019, 2:10 am

≫ Next: TPS92662-Q1: Water Wash Ability

≪ Previous: TAS5825M: GPIO MUTE

Part Number:CC2650

Tool/software: Code Composer Studio

I am new to microcontrollers and all, and am trying to send a 32.768 kHz clock to a pressure sensor. Is there a way in Code Composer Studio to do this?

↧

TPS92662-Q1: Water Wash Ability

June 6, 2019, 2:13 am

≫ Next: CCS/DLPNIRNANOEVM: Error compiling Tiva Software for NIRScan Nano EVM

≪ Previous: CCS/CC2650: Is there a way to send the 32.768 kHz crystal clock output to any pin?

Part Number:TPS92662-Q1

Hi,

Is TPS92662 water washable with "de-ionized" water?

I see no indication of water / aqueous wash ability on the part's home page or in the datasheet.

What is your recommendation?

Best regards,

Florian Helling

↧

CCS/DLPNIRNANOEVM: Error compiling Tiva Software for NIRScan Nano EVM

June 6, 2019, 2:13 am

≫ Next: LM2904: LM2904AVQPWR : could you provide input offset current vs temperature curve?

≪ Previous: TPS92662-Q1: Water Wash Ability

Part Number:DLPNIRNANOEVM

Tool/software: Code Composer Studio

Hello everyone,

I'm trying to compile Tiva Software for the NIRScan Nano EVM, but I'm getting this errors.

I followed all the step in the User's Guide and I have used all the versions indicated on it.

Any idea of what it is happening?

Thanks.

↧

LM2904: LM2904AVQPWR : could you provide input offset current vs temperature curve?

June 6, 2019, 2:14 am

≫ Next: CC2564MODA: CC2564MODA BLE mode power consumption

≪ Previous: CCS/DLPNIRNANOEVM: Error compiling Tiva Software for NIRScan Nano EVM

Part Number:LM2904

customer want to get input offset current vs temperature on LM2904AVQPWR,

could you provide it?

thanks.

↧

CC2564MODA: CC2564MODA BLE mode power consumption

June 6, 2019, 2:14 am

≫ Next: DP83822H: TD_P, TD_M waveform

≪ Previous: LM2904: LM2904AVQPWR : could you provide input offset current vs temperature curve?

Part Number:CC2564MODA

Hi Champs,

Could you please clarify CC2564mod BLE mode power consumption ?

I would like to confirm how this consumption improve to BLE mode.

We have only this information. However, CC2640 or some BLE only device mentioned "standby current", "RX/TX current"

We would like to compare this information.

Could you please confirm this value ? If this value is not characterized , do you satisfy BLE consumption requirement and tell us what is this number ?