This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

BQ2022AEVM-001: EV2400 does not send programming pulse

Part Number: BQ2022AEVM-001
Other Parts Discussed in Thread: EV2400, BQ2022A

I understand this is the same issue as from other posts, but I could not find a definite resolution to the problem.

The EV2400, with either firmware version 0.28 or 0.32, does not generate the pulse to enable the necessary 12-V level for programming the bq2022 EPROM.

I have tried with two bq2022A EVM's and two EV2400 interfaces. I am able to read data from the device, but none of the write commands work. The power supply is connected, jumper J3 is in place. However, despite whether the setup has an issue or not, an observation at the HDQ connector with either oscilloscope or logic analyzer indicate the EV2400 does not generate the programming pulse. From other posts, I believe firmware version 0.28 should have taken care of this issue, but both customer and I could not make it work.

Do you have suggestions on how to go about this issue?

Thank you!

  • Hello Lenio,

    I could not find any documentation that indicates that v0.28 added support for the programming pulse. The EV2300 has all the features for bq2022A. As far as i know, the EV2400 can communicate well with bq2022A but does not implement the programming pulse.

  • Do we have a workaround for the EV2400? Is it possible to generate the pulse manually and, if so, can you offer details?

  • Hello Lenio,

    Yes, you can generate the pulse externally. The timing information is provided in the bq2022A datasheet.

  • My question was how do I manually synchronize the programming pulse with command 0x5A, if that is indeed critical. The flowchart on page 12 indicates that VPP should happen after the command is done. The picture in the datasheet you mention specifies the min duration, but it does not put it in the context of the other signals.

  • Hello Lenio,

    Applying the programming pulse is the next step after command 0x5A and requires a minimum of 5us delay, i do not see a max time specified. Let me know if i missed something.

    The response from the bq2022A is likely to be lost when sending the programming pulse externally because synchronization may be required. The workaround is to use the READ MEMORY commands to read it separately for verification.

  • The manual pulse works. I just added a toggle switch from 5V supply to the PROGRAM pin of the EVM. I send the write command and follow with flipping the switch back and forth. Indeed the pulse can be however long with a minimum of 2.5ms.

  • Hello, 

    I have exactly the same issue as described by Lenio. As per the thread I have tried latest code updates without success, and adding a 5V voltage with a toggle switch to the Vout3/program line - I cut the line and linked directly to switched 5V. This method does not appear to work - it may well work for a single 8 byte wirite burst, but not when trying to write the entire 1024 bit array. As I have no way of precisely timing the 5V signal, this results in CRC errors. Reading back the device after write attempt confirms some of the data is written, but not all, and not consistently.

    The frustrating thing about this is that if you read the forum this issue has been known for years, yet there is still no firmware update which provides a fix, and TI continues to market EV2400 as a solution to work with the BQ2022A evaluation kit, which it clearly isn't. EV2300 does not appear to be widely available any more, as was discontinued by TI some time ago.

    I need help to resolve this - need to be able to write data to the memory as well as read, preferably without having to design my own evaluation kit.

    Thanks

  • Hello Stephen,

    I have seen other threads that imply that TI claims that the EV2400 can be used in place of EV2300 with the bq2022A. If you can point me to the document/link that is causing confusion, i can request it to be updated.

    Here is another thread that I answered yesterday with the same issue .

    e2e.ti.com/.../ev2400-bq2022-evaluation-software-usb-error-insure-cable-is-connected-and-driver-is-working

  • Hi Shirish, check out the user guide 'BQ2022A Evaluation Software (Rev C)' - mentions the EV2400 throughout the document.. Confusion comes reading a note that states EV2400 is required but at the same time states that it doesn't work with code version 0.18 or earlier

    https://www.ti.com/lit/ug/sluu258c/sluu258c.pdf?ts=1644318352155&ref_url=https%253A%252F%252Fwww.ti.com%252Ftool%252FBQ2022AEVM-001%253FkeyMatch%253D%2526tisearch%253Dsearch-everything%2526usecase%253Dpartmatches

    The main page mentions EV2300 but this is no longer available from TI, and I have searched for other suppliers without success, so don't see a way forward there.

    Regarding your additional thread, my issue is only with write commands - I can see everything else works fine - USB interface, ROM CMD, read ID, read data are all good. I just have no obvious way of synchronising the write command with the program pulse (if I use an external toggled voltage), which results in partial writes with CRC errors  if I try to write multiple bytes. The only practical solution would be to have the MSP430 output synchronised program pulses onto Vout3 pin of the HDQ port, which I guess was the original intent as the HW is already in place on the EV2400.

  • Hello Stephen,

    Thank you for the information. I will request to have the document updated. We are also checking if the EV2400 hardware has the capability to support it.