Peripheral FW capsule delivery?

Peripheral FW capsule delivery?

[Brad Bozarth]

Hi!

I am implementing firmware for a touchpad that will be going into a laptop,
connected via i2c. We would like to take advantage of the UEFI firmware
capsule delivery method for firmware updates if possible. I am struggling
to find out how to do this. In particular, I'd like to know whether there
is a "standard" delivery mechanism we can take advantage of and communicate
with from the firmware side over i2c, or if we need to write UEFI driver
code of some sort to pass the update down. We'd love to leverage a standard
pipe that dumps an update over i2c if possible and implement what we need
to on the firmware side. We are supplying our touchpad to the laptop OEM
and they are distant and have their own software teams, so if we need to
write UEFI code, it complicates matters!

This is the page that I'd love to read, if it were filled out :)
https://github.com/mdkinney/edk2/wiki/Capsule-Based-Device-Firmware-Update

Thank you!
Brad

Re: Peripheral FW capsule delivery?

[Brad Bozarth]

I would really appreciate a small pointer on this - yes/no on if is a
standard peripheral fw delivery buit-in, and maybe a pointer to a doc or
source code directory to take a look at?

Thank you,
Brad

On Tue, Jan 29, 2019 at 4:54 PM Brad Bozarth <brad@sensel.com> wrote:

> Hi!
>
> I am implementing firmware for a touchpad that will be going into a
> laptop, connected via i2c. We would like to take advantage of the UEFI
> firmware capsule delivery method for firmware updates if possible. I am
> struggling to find out how to do this. In particular, I'd like to know
> whether there is a "standard" delivery mechanism we can take advantage of
> and communicate with from the firmware side over i2c, or if we need to
> write UEFI driver code of some sort to pass the update down. We'd love to
> leverage a standard pipe that dumps an update over i2c if possible and
> implement what we need to on the firmware side. We are supplying our
> touchpad to the laptop OEM and they are distant and have their own software
> teams, so if we need to write UEFI code, it complicates matters!
>
> This is the page that I'd love to read, if it were filled out :)
> https://github.com/mdkinney/edk2/wiki/Capsule-Based-Device-Firmware-Update
>
> Thank you!
> Brad
>

Re: Peripheral FW capsule delivery?

[Kinney, Michael D]

Hi Brad,

In order to update a FW storage device in UEFI, a UEFI driver
that produces the Firmware Management Protocol is required.

There are some protocols to access I2C devices, so the 
implementation of the Firmware Management Protocol for
an I2C device can use the I2C protocols to perform the
I2C transactions to update the FW storage device on that
I2C device.

I am not aware of a standard for updating firmware devices
on I2C busses, so a new UEFI Driver would be required.

Please let me know if there is a public standard for 
this operation that I am not aware of.

Thanks,

Mike



> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-
> bounces@lists.01.org] On Behalf Of Brad Bozarth
> Sent: Tuesday, February 5, 2019 11:07 AM
> To: edk2-devel@lists.01.org
> Subject: Re: [edk2] Peripheral FW capsule delivery?
> 
> I would really appreciate a small pointer on this -
> yes/no on if is a
> standard peripheral fw delivery buit-in, and maybe a
> pointer to a doc or
> source code directory to take a look at?
> 
> Thank you,
> Brad
> 
> On Tue, Jan 29, 2019 at 4:54 PM Brad Bozarth
> <brad@sensel.com> wrote:
> 
> > Hi!
> >
> > I am implementing firmware for a touchpad that will
> be going into a
> > laptop, connected via i2c. We would like to take
> advantage of the UEFI
> > firmware capsule delivery method for firmware updates
> if possible. I am
> > struggling to find out how to do this. In particular,
> I'd like to know
> > whether there is a "standard" delivery mechanism we
> can take advantage of
> > and communicate with from the firmware side over i2c,
> or if we need to
> > write UEFI driver code of some sort to pass the
> update down. We'd love to
> > leverage a standard pipe that dumps an update over
> i2c if possible and
> > implement what we need to on the firmware side. We
> are supplying our
> > touchpad to the laptop OEM and they are distant and
> have their own software
> > teams, so if we need to write UEFI code, it
> complicates matters!
> >
> > This is the page that I'd love to read, if it were
> filled out :)
> > https://github.com/mdkinney/edk2/wiki/Capsule-Based-
> Device-Firmware-Update
> >
> > Thank you!
> > Brad
> >
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel

Re: Peripheral FW capsule delivery?

[Brad Bozarth]

Thank you Mike! This is kind of what I thought, but wasn't sure if I was
missing something. I will let you know if I come across any standard.
-Brad

On Tue, Feb 5, 2019 at 2:58 PM Kinney, Michael D <michael.d.kinney@intel.com>
wrote:

> Hi Brad,
>
> In order to update a FW storage device in UEFI, a UEFI driver
> that produces the Firmware Management Protocol is required.
>
> There are some protocols to access I2C devices, so the
> implementation of the Firmware Management Protocol for
> an I2C device can use the I2C protocols to perform the
> I2C transactions to update the FW storage device on that
> I2C device.
>
> I am not aware of a standard for updating firmware devices
> on I2C busses, so a new UEFI Driver would be required.
>
> Please let me know if there is a public standard for
> this operation that I am not aware of.
>
> Thanks,
>
> Mike
>
>
>
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-
> > bounces@lists.01.org] On Behalf Of Brad Bozarth
> > Sent: Tuesday, February 5, 2019 11:07 AM
> > To: edk2-devel@lists.01.org
> > Subject: Re: [edk2] Peripheral FW capsule delivery?
> >
> > I would really appreciate a small pointer on this -
> > yes/no on if is a
> > standard peripheral fw delivery buit-in, and maybe a
> > pointer to a doc or
> > source code directory to take a look at?
> >
> > Thank you,
> > Brad
> >
> > On Tue, Jan 29, 2019 at 4:54 PM Brad Bozarth
> > <brad@sensel.com> wrote:
> >
> > > Hi!
> > >
> > > I am implementing firmware for a touchpad that will
> > be going into a
> > > laptop, connected via i2c. We would like to take
> > advantage of the UEFI
> > > firmware capsule delivery method for firmware updates
> > if possible. I am
> > > struggling to find out how to do this. In particular,
> > I'd like to know
> > > whether there is a "standard" delivery mechanism we
> > can take advantage of
> > > and communicate with from the firmware side over i2c,
> > or if we need to
> > > write UEFI driver code of some sort to pass the
> > update down. We'd love to
> > > leverage a standard pipe that dumps an update over
> > i2c if possible and
> > > implement what we need to on the firmware side. We
> > are supplying our
> > > touchpad to the laptop OEM and they are distant and
> > have their own software
> > > teams, so if we need to write UEFI code, it
> > complicates matters!
> > >
> > > This is the page that I'd love to read, if it were
> > filled out :)
> > > https://github.com/mdkinney/edk2/wiki/Capsule-Based-
> > Device-Firmware-Update
> > >
> > > Thank you!
> > > Brad
> > >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
>

Re: Peripheral FW capsule delivery?

[Doran, Mark]

Hi Brad:

One other possible path you might be able to consider.  Have you looked at Component Firmware Update as a way to manage in-device firmware??  While that originates with Microsoft, it's open source and OS neutral and might be an easier overall. 

  https://blogs.windows.com/buildingapps/2018/10/17/introducing-component-firmware-update/

As a general rule of thumb, I'd always advise that your first choice should be to move any work out of the Pre-OS space and into OS-present space wherever possible.

--
Cheers,

Mark.


-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Brad Bozarth
Sent: Tuesday, February 5, 2019 12:26 PM
To: Kinney, Michael D <michael.d.kinney@intel.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [edk2] Peripheral FW capsule delivery?

Thank you Mike! This is kind of what I thought, but wasn't sure if I was missing something. I will let you know if I come across any standard.
-Brad

On Tue, Feb 5, 2019 at 2:58 PM Kinney, Michael D <michael.d.kinney@intel.com>
wrote:

> Hi Brad,
>
> In order to update a FW storage device in UEFI, a UEFI driver that 
> produces the Firmware Management Protocol is required.
>
> There are some protocols to access I2C devices, so the implementation 
> of the Firmware Management Protocol for an I2C device can use the I2C 
> protocols to perform the I2C transactions to update the FW storage 
> device on that I2C device.
>
> I am not aware of a standard for updating firmware devices on I2C 
> busses, so a new UEFI Driver would be required.
>
> Please let me know if there is a public standard for this operation 
> that I am not aware of.
>
> Thanks,
>
> Mike
>
>
>
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel- bounces@lists.01.org] On Behalf 
> > Of Brad Bozarth
> > Sent: Tuesday, February 5, 2019 11:07 AM
> > To: edk2-devel@lists.01.org
> > Subject: Re: [edk2] Peripheral FW capsule delivery?
> >
> > I would really appreciate a small pointer on this - yes/no on if is 
> > a standard peripheral fw delivery buit-in, and maybe a pointer to a 
> > doc or source code directory to take a look at?
> >
> > Thank you,
> > Brad
> >
> > On Tue, Jan 29, 2019 at 4:54 PM Brad Bozarth <brad@sensel.com> 
> > wrote:
> >
> > > Hi!
> > >
> > > I am implementing firmware for a touchpad that will
> > be going into a
> > > laptop, connected via i2c. We would like to take
> > advantage of the UEFI
> > > firmware capsule delivery method for firmware updates
> > if possible. I am
> > > struggling to find out how to do this. In particular,
> > I'd like to know
> > > whether there is a "standard" delivery mechanism we
> > can take advantage of
> > > and communicate with from the firmware side over i2c,
> > or if we need to
> > > write UEFI driver code of some sort to pass the
> > update down. We'd love to
> > > leverage a standard pipe that dumps an update over
> > i2c if possible and
> > > implement what we need to on the firmware side. We
> > are supplying our
> > > touchpad to the laptop OEM and they are distant and
> > have their own software
> > > teams, so if we need to write UEFI code, it
> > complicates matters!
> > >
> > > This is the page that I'd love to read, if it were
> > filled out :)
> > > https://github.com/mdkinney/edk2/wiki/Capsule-Based-
> > Device-Firmware-Update
> > >
> > > Thank you!
> > > Brad
> > >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org
> > https://lists.01.org/mailman/listinfo/edk2-devel
>
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel