How to connect Power Commander tool to target board

Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
8 posts / 0 new
Last post
jeremye
Offline
Last seen: 4 months 4 weeks ago
Joined: 2017-01-10 15:40
How to connect Power Commander tool to target board

I have prototype boards containing the DA9053 PMIC and would like to know the requirements for connecting the Power Commander running on a PC to the PMIC, which in my case needs to use the 2-wire I2C interface. I see there is documentation for doing this to your eval boards, but cannot find an explanation for doing it on a production board. Thank you.

Device: 
ED_Dialog
Offline
Last seen: 1 hour 29 min ago
Staff
Joined: 2017-09-18 11:54
Hello Jeremye,

Hello Jeremye,

You will need access to Vsys, GND, GPIO14, GPIO15 and TP on your prototype board. TP will need to be pulled-up to VDDCORE.  GPIO14 and GPIO15 will be your I2C pins. 

Whilst you can get the DA9053 to enter Powercommander mode in system, you will not be able to program the part, this why we do not have any documentation on this.

I have a few questions:

  • Are the solder down parts programmed? 
  • If so, is it a customer OTP or a standard variant?
  • Do you have a DA9053 Eval board?
  • Do you intend on using the Eval board to communicate with the DA9053?

Kind regards,
Elliott Dexter 

 

jeremye
Offline
Last seen: 4 months 4 weeks ago
Joined: 2017-01-10 15:40
The part is the DA9053-60HA2.

The part is the DA9053-60HA2. We haven't used this variant before. It is the standard variant, not programmed by us.
We don't have an eval board., and didn't have intention of using one to communicate with the DA9053 (that might change).

Your final question implies that I might use an eval board to communicate with the soldered-in part, is that the case? I had assumed I would need at least a USB to I2C bridge device.
The reason I want to do this is solely for debugging, not programming. For some reason the DA9053 will not communicate to the host processor on our board, over the 2-wire i/f) and I was hoping to find out what state it is in.

Unfortunately the TP pin of the DA9053 is connected to 0V, and I don't think I can change that. Useful to know for future designs nonetheless.

ED_Dialog
Offline
Last seen: 1 hour 29 min ago
Staff
Joined: 2017-09-18 11:54
Hello Jeremye,

Hello Jeremye,

I have used our ICP board in the past to force one of the DA9061/62/63 parts into Powercommander mode, I found this method easier for myself. However these parts are different. The -60 varaint has no AutoBoot, so you should be able to connected onto the I2C lines (GPIO14 and GPIO15) and have some element of control before the start-up and after start-up. However if you want to make changes before the start-up, you will have to make sure there are no IRQ's or wake-up events before you make the changes.

 

It will not be full powercommander mode, but its the best option we have. 

 

Are you just testing the turn on of LDO4?

Kind regards,
Elliott Dexter  

jeremye
Offline
Last seen: 4 months 4 weeks ago
Joined: 2017-01-10 15:40
HI Elliott

HI Elliott
That sounds encouraging.
I'm a bit confused now about what I need to communicate to the DA9053: ICP board, Eval Board or custom interface?
Can you tell me what I need and how to obtain it? The Dialog website seems not very clear on this.

No, not trying to turn on LDO4 at present. I'd have to go down the route of custom OTP to make that viable, as It would need to turn on first in the sequence.
Thank you

ED_Dialog
Offline
Last seen: 1 hour 29 min ago
Staff
Joined: 2017-09-18 11:54
Hello Jeremye,

Hello Jeremye,

Ok, So the ICP board is for the DA9061/62 and DA9063 only. This board is used for in-circuit programming only.

The two options you have is:

  • Write via I2C to the DA9053 from a processor or FPGA.
  • Or use the DA9053 Eval board. This method you will then get the correct drivers and directly link the DA9053 to the GUI. This is a slightly more expensive approached but you will have visibility into the registers on the DA9053.

I will have a quick talk with the apps team, to see if there is another possibility, but i think we only have the two options.

 

Kind regards,
Elliott Dexter 

jeremye
Offline
Last seen: 4 months 4 weeks ago
Joined: 2017-01-10 15:40
My original problem was that

My original problem was that the host processor couldn't communicate with the DA9053-60HA2 over the 2-wire Power Commander interface. Taking your earlier hint to use GPIO_14,15, I lashed-up an extra I2C connection to these pins and succeeded in getting the two to talk, Hurrah.
I've examined all the register state in the DA9053 and discovered a few unexpected things:
* The DA9053's PC I2C addresses (OxB0 write, 0xB1 read) have changed relative to the previous DA9053-3FHA2 variant we were using (Ox90 write, 0x91 read) .
* The default power commander interface has changed from the 2-wire to the 4-wire, our current board can't handle that.

The new I2C address is in contradiction to the DA9053's datasheet (v2.1, section 10.3, page 65), you might like to know.

To correct these issues, and a number of other minor issues, it's looking like the best way to proceed is to produce our own custom OTP data. Not having done that before, I wonder if you would give a pointer on how to get started with that? Thank you

ED_Dialog
Offline
Last seen: 1 hour 29 min ago
Staff
Joined: 2017-09-18 11:54
Hello Jeremye,

Hello Jeremye,

The -60 and the -3F standard variants are for different processors. The -3F is for the i.MX53 and the -60 is for the i.MX6DL. 

  • I checked both OTPs and your observation is correct, the I2C address between the two variants is different and there is a change from 2-wire to 4-wire. AN-PM-31 recommends using the 4-wire for the I.MX6DL. I will ask the application team why there was a change from 4-wire to 2-wire, this might be why there is a change in I2C address but i will confirm.
  • For a custom OTP, i will need to submit a business case to the BU, they will then judge if it is viable to create a new OTP. However there is a threshold of approx. 50K parts per year for the creation of new OTP. Unlike the DA9061/62/63 we cannot In-circuit program the DA9053.

Kind regards,
Elliott Dexter