meson: Fix meson builds

When building the project from scratch (from a new workstation without
docker) I found that there were dependencies missing. Fixed them up.

Tested: Was able to build " tools

meson: Fix meson builds

When building the project from scratch (from a new workstation without
docker) I found that there were dependencies missing. Fixed them up.

Tested: Was able to build " tools/" and "bmc/"

Signed-off-by: Brandon Kim <brandonkim@google.com>
Change-Id: Id2250c481a37d3cd4ed6915b1b2b0978df6e4649

show more ...

build: remove autotool

Change-Id: I662c8a5d29453622744f44c1984416f1303354e6
Signed-off-by: Willy Tu <wltu@google.com>

build: Add meson build

Changes to note,
- `with_systemdsystemunitdir` and `with_tmpfilesdir` is removed since it
is not being documented nor used in OpenBMC.
- Removed the Code coverage feature wi

build: Add meson build

Changes to note,
- `with_systemdsystemunitdir` and `with_tmpfilesdir` is removed since it
is not being documented nor used in OpenBMC.
- Removed the Code coverage feature with `-DDHAVE_GCOV`, since it is not
used and meson covers it.
- Removed `--enable-oe-sdk` for using the OpenBMC SDK. It should work
directly with no change required.

Tested:
```
Jan 01 00:01:54 ipmid[709]: Try loading blob from persistent data
Jan 01 00:01:54 ipmid[709]: Stale blob data, resetting internals...
Jan 01 00:01:56 ipmid[709]: config loaded: /flash/bios
Jan 01 00:01:56 ipmid[709]: config loaded: /flash/image
Jan 01 00:01:56 ipmid[709]: config loaded: /flash/dummy
...
```

```
$ ls /usr/lib/blob-ipmid/
libfirmwareblob.so
libfirmwarecleanupblob.so libversionblob.so
```

Testing the service,
```
$ echo "hello" > /tmp/test.txt
$ burn_my_bmc -command update -layout dummy -image /tmp/test.txt
Sending over the firmware image.
Opening the verification file
Committing to /flash/verify to trigger service
Calling stat on /flash/verify session to check status
running
success
Returned success
succeeded
```

On the BMC.
```
/run/initramfs$ cat dummy
hello
```

Change-Id: I21c7c33bd62c0ee40681cb40da90125c125bea2f
Signed-off-by: Willy Tu <wltu@google.com>

show more ...

bmc: provide disabled json support

Provide support such that a json configuration file can define a firmware
handler and its behavior. This is not yet enabled.

Signed-off-by: Patrick Venture <vent

bmc: provide disabled json support

Provide support such that a json configuration file can define a firmware
handler and its behavior. This is not yet enabled.

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: If21f4e97951b3bb91a8afc53bee493d8600a04b7

show more ...

build: install three targets to handle bmc updates

Transition from three service files to three targets installed by the
BMC library:
- phosphor-ipmi-flash-bmc-prepare.target
- phosphor-ipmi-flash

build: install three targets to handle bmc updates

Transition from three service files to three targets installed by the
BMC library:
- phosphor-ipmi-flash-bmc-prepare.target
- phosphor-ipmi-flash-bmc-verify.target
- phosphor-ipmi-flash-bmc-update.target

The prepare target is started each time the firmware update state
machine changes from notYetStarted to uploadInProgress and can be
leveraged to free memory (flush caches) or anything else required.

The verify target is started when the verify blob is committed. The
implementation of services within this target are such that they are
expected to output a status value that's readable (typically via a
file).

The update target is started when the update blob is committed.

Signed-off-by: Patrick Venture <venture@google.com>
Change-Id: I1e838de954a3cf8956ff4b72d090e253b832efe7

show more ...

autotools: Fix for autoconf-archive 2019.01.19

The code coverage macros from the archive changed in a backward
incompatible way. This adds a workaround to autodetect either version
and do the right

autotools: Fix for autoconf-archive 2019.01.19

The code coverage macros from the archive changed in a backward
incompatible way. This adds a workaround to autodetect either version
and do the right thing.

Change-Id: I71627d62a41d2c3cc07764cd0901354680092f07
Signed-off-by: Patrick Venture <venture@google.com>

show more ...

.gitignore: add autom4te.cache

Add autom4te.cache to .gitignore file.

Change-Id: I4b246860edc94dd31e844badc7ddfa54febe50fb
Signed-off-by: Patrick Venture <venture@google.com>

tools: start burn_my_bmc tool

Start implementation of burn_my_bmc host tool, the purpose of which is
to upload the firmware image and trigger the verification process.

The utility will accept four

tools: start burn_my_bmc tool

Start implementation of burn_my_bmc host tool, the purpose of which is
to upload the firmware image and trigger the verification process.

The utility will accept four parameters:
1) command - the command to run, initially only "update"
2) interface - the data interface to use, e.g. lpc or pci
3) image - the path to the image file
4) sig - the path to the image's signature file

Change-Id: Ifbab7df947f37dd3a6fddddcf523c0fa724c9551
Signed-off-by: Patrick Venture <venture@google.com>

show more ...

test: fixup unit-test naming

Fixup naming convention for unit-test files and add to gitignore.

Change-Id: I0fe5d167e52c4a05d1c89dfd996afdde4b48a4c9
Signed-off-by: Patrick Venture <venture@google.co

test: fixup unit-test naming

Fixup naming convention for unit-test files and add to gitignore.

Change-Id: I0fe5d167e52c4a05d1c89dfd996afdde4b48a4c9
Signed-off-by: Patrick Venture <venture@google.com>

show more ...

gitignore: Add test-driver

Add test-driver object to gitignore.

Change-Id: I0395e9a95a977831fa995b4bd0bf400901b46d70
Signed-off-by: Patrick Venture <venture@google.com>

update gitignore for more artifacts

Add more autotools artifacts to gitignore file.

Change-Id: Ib935e247a7acba3eedd4c1f7b2bad30bbe04134f
Signed-off-by: Patrick Venture <venture@google.com>

Add gitignore to repo

Add gitignore to repo.

Change-Id: I61b99b40c03d96bf49b48358a1b357c3f7d2311d
Signed-off-by: Patrick Venture <venture@google.com>

tools: starting burn_my_bmc host utility

burn_my_bmc is a host-run utility that in cooperation with the
phosphor-ipmi-flash library, attempts to send a BMC firmware image and
signature file to the B

tools: starting burn_my_bmc host utility

burn_my_bmc is a host-run utility that in cooperation with the
phosphor-ipmi-flash library, attempts to send a BMC firmware image and
signature file to the BMC and trigger verification of said image.

The program's current design and use were tailored towards the legacy
OpenBMC image and not UBI. Therefore, changes to support the UBI
process will get addressed as it all takes shape.

The overall process is:
1) Attempts to send firmware image over an interface.
2) Attempts to send signature file contents over an interface*.
3) Triggers a verification step.
4) Reboots the BMC**.

* The only interface in the initial version here is the blocktransfer
interface. It's technically also possibly KCS. It's sending the data
over the same communications channel as the normal IPMI packets. A
later patchset will enable sending the data bytes over an LPC memory
region or the PCI P2A region.

** The 4th step is done by a separate call to the 'reboot' command.
The 'reboot' and 'ping' commands will come in a later patchset.

Change-Id: I62d725274e56c55ca414fa6c2a3eab6c500066ed
Signed-off-by: Patrick Venture <venture@google.com>

show more ...

ipmi: start implementing flashStartTransfer

Change-Id: I1f8b1498d517c0661e98b1ba895e7152f7a9ed8e
Signed-off-by: Patrick Venture <venture@google.com>

main: start with no-op handler

Change-Id: I0504ad186687535966179757cef68c3b4eca754f
Signed-off-by: Patrick Venture <venture@google.com>