On Fri, Jan 05, 2018 at 10:41:51AM +0800, Jun Nie wrote:
> 2018-01-04 22:53 GMT+08:00 Maxime Ripard <[email protected]>:
> > On Fri, Dec 29, 2017 at 05:35:51PM +0800, Jun Nie wrote:
> >> Hi Bernhard,
> >>
> >> Resend this mail with CCing mail list so that more people can see this
> >> issue and may have answer. Also correct register access code I use as
> >> I send wrong version code in last mail.
> >>
> >> I see sunxi-tool patch a3ce5f9f and you also mentioned that writing value 
> >> is OK
> >> with register based method in google group. Do you have eFuse writing
> >> code that works? I can write OEM_PROGRAM and THERMAL_SENSOR with below
> >> code. But when I write ROTPK_HASH, eFuse is not changed.
> >
> > I'm not sure if this is still relevant, but some of the older SoCs
> > were allegedly needing to toggle one pin low in order to program the
> > fuses (VDDQE on the A20) before writing to it.
> >
> > I have no idea whether it's still there on the H3 though, and no one
> > ever tried it as far as I'm aware.
> >
> > Maxime
> 
> Maxime,
> 
> Thanks for sharing this info! Did you remember what pin is needed to
> toggle? The toggling is needed for any eFuse field program, or just
> some fields of eFuse?

On the A20, it's the ball T9 (with the VDDQE name). Unfortunately,
that pin was forced on all the designs we've seen, so we haven't been
able to confirm this, but I guess it's just some kind of write protect
covering the whole fuses

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Attachment: signature.asc
Description: PGP signature

Reply via email to