Age | Commit message (Collapse) | Author |
|
Correct the misspelled URL from fimware to
firmware. The misspelled URL is able to use
although.
Change-Id: I0f1722e1ebb9cc58c0805c648d58db16813ab290
Signed-off-by: Haoran Wang <Haoran.Wang@freescale.com>
|
|
Update the prebuilt bootloader, adds
support for BPT.
Change-Id: I7009f9d14bc5553e0e79b84413bdb74254d6d59c
Signed-off-by: Stefan Stanacar <stefan.stanacar@intel.com>
|
|
Added uboot packages for picoimx.
Change-Id: I2364ab742ce24c06aa1fcf7ae2655ed8efb9e987
Signed-off-by: fang hui <hui.fang@freescale.com>
|
|
This update add support for BPT generated
partition tables and drops gpt.bin
Includes these source commits:
541858e edison: make power on write protection configurable
b547979 fastboot: make GPT partitions verification optional
996b9e7 edison: Add variables to kernel command line
5f99566 brillo: Add erase userdata before recovery mode
6f9233d Add more info to "fastboot getvar all" command
32effe5 fastboot: Change gpt flashing to consider full images
eb94feb Add indication when booting to the non-requested A/B
56ec6fb edison: write the developer key to the security partition
be08822 brillo: Invalidate slots before booting to recovery
Bug: 28252130
Change-Id: I78c27a40858102ce885cf169814f11a9babfdf1b
Signed-off-by: Stefan Stanacar <stefan.stanacar@intel.com>
|
|
Updates OS/packages to get absolute paths (this allows
the tests DB to have relative paths and not break).
BUG: https://b/28718555, https://b/28723347
Change-Id: Ibe292b9a7c179607d428a01fb381b0695bcc93d6
TEST: sh cli/bdk_tests.sh passes, unit tests pass.
|
|
Added bcm4339 firmware packages for
wifi and BT in picoimx.
Change-Id: I77d66e8ab745f3a26703c4acb34736d771dd71cf
Signed-off-by: Wang Haoran <Haoran.Wang@freescale.com>
|
|
Whenever we refactor file names, it often leaves behind a .pyc file.
These files still get discovered when running commands and unit
tests, and can lead to accidental failures.
Also add this script to run on PREUPLOAD. Since repo currently does
not provide a method of running hooks on a sync, this is the best
we can do at the moment.
Bug: 28053765
Test: `./tools/cleanup.py` lists my orphaned .pyc files.
Does not delete them unless inputting 'y' at the prompt.
Test: `./tools/cleanup.py --quiet --yes` automatically cleans
up all orphaned .pyc files.
Test: Orphaned .pyc files are cleaned up when uploading this CL.
Change-Id: I5c1cada450b448938d285c5802499a3a890fe215
|
|
The buffer flag was added w/out a specific reason that I can see. Back
that out so we get more immediate output rather than wait for all tests
to finish, and make it so we abort on the first test failure. Otherwise,
if something is hung, CTRL+C will kill the test w/no output at all.
Bug: None
Change-Id: Ia28318a8ccda136ba044861d950578b3cd591888
Test: `python cli/lib/test_runner.py` shows immediate output & failure
|
|
BUG: 28666685
TEST: unit tests pass, os_root shows up for 'bdk config' commands,
confirmed other BDK commands still work.
Change-Id: If33efed3006fd32ac0837e1be33fe1e3230b3799
|
|
With the exception of DEPRECATED_GetDefaultOSPath.
Now, use methods of <platform>.os.
BUG: 28637815
TEST: Unit tests pass, ran affected commands
Change-Id: I8b3ff07580a9c03ea662ac39de9955966f57f109
|
|
BUG: 28527859
Change-Id: I7ecde3882f601e33243ad30e1ec5872d662efced
TEST: unit tests pass, ran modified commands
|
|
BUG: 28637861
Change-Id: I73fc9d7f32956f0b6b7c43d33ed62c4c435fafbb
TEST: unit tests pass, commands work.
|
|
Encapsulates os name, path, and version in a handy
place.
BUG: 28637491
Change-Id: I532c5b6a24887594eb49f6ff37350bfad8685bf3
TEST: unit tests pass
|
|
Provision device script (at least Intel's) expects
to be in $ANDROID_PRODUCT_OUT. But bdk flash was using
the one from the platform $ANDROID_PRODUCT_OUT, then re-setting
$ANDROID_PRODUCT_OUT to point to the special flashing dir. In this
particular case, Intel's script searches the local dir first, and thus
found the default platform system.img instead of the bdk-built one.
This fixes bdk flash to instead use the provision-device
located in the flashing dir (which happens to just be a link
to the other, but that's besides the point). It also updates
all tools to just use env variables in their paths, so that
if those variables change, the tool path does too.
BUG: 28564349
TEST: unit tests pass. Added unit test that failed before
this fix and passed afterwards. Manual runs of
`bdk2 build image` and `bdk2 root provision`
result in expected behavior (user artifacts on the device).
Change-Id: I505298b702706df79cc2e68bb1c1a81ead14f55d
|
|
util.GetProductDir() expects os.getcwd() to start with '/' or else it
may loop forever. This seems like a reasonable expectation (on Linux at
least) so adjust StubOs.cwd to comply.
This fixes an issue where in some cases climanager_unittest.BdkTest
would end up calling util.GetProductDir(), but a previous test had
replaced util.os with StubOs, leading to this infinite loop.
The real underlying problem is that manually monkey-patching over
imported modules is super unpredictable and brittle, but that will have
to be addressed in a larger test overhaul.
Bug: 28602169
Change-Id: I5eda7e55b704933272f97a4334d7a92d18a0f6fa
Test: `python test_runner.py`, with and without randomized test order.
|
|
Replaces putting metadata in <target cache> and user
artifacts in <target cache>/root with placing the former
in <target cache>/metadata and the latter in <target cache>/build_root
(I figured might as well reduce potential for accidental aliasing
by also moving where metadata was kept). Both these paths are no longer
magical, instead they come from methods of the spec.config.
Also cleaned up metadata/selinux paths so they're no longer magical.
BUG: 28588412
Change-Id: Iad0edf525a2687c5f8f1973f3455fbe22e1faba6
TEST: unit tests pass, bdk build image and root sync work.
|
|
The current wrapping logic lets the default OUT_DIR be used when setting
up the env which means later commands will search out/. It's then passed
in directly to `make` to override things to the custom path. Export the
var instead for all commands.
In practice, this might not make much of a difference, but it can cause
really confusing behavior when adding more commands to this shell chain
as it searches a completely different (possibly already existing) build
tree.
Bug: 27808605
Test: build platform still works
Change-Id: Id8e127da7fe4ef0abce407dbdedf63842bccbb6e
|
|
The clicommand.RunWithMetrics tests code was never updated when
the user store was refactored. As such, the stubs stopped taking
effect, so the actual user store in the BDK tree was being created
and used, which could lead to unpredictable behavior.
Bug: 28590102
Change-Id: I3ec1b74b7f338fa086f38bb13c41be08e2c5e23e
Test: `python test_runner.py` passes, no user_store created in BDK tree.
|
|
os, bsp, and versions of both have been replaced
in target with a Platform wrapping them all. The
Platform object also provides methods/properties
to get os root, build cache, and other cache dirs, as
well as wrap device/os linking.
BUG: 28401438
Change-Id: Id1d37e89b3b2295557a5071854772d6f4718b9da
TEST: Unit tests pass, ran all affected commands
|
|
The test did not stub out the metrics_util class, so it would
try to create the user_data directory in the BDK tree and pull
actual data for the unit test.
Bug: 28566748
Change-Id: Iec69b3d9f4a5e8a09f8edb3c3249516cdb9eb942
Test: `python test_runner.py` passes
|
|
BUG: 28564349
Change-Id: Idd9ee459f8cdeae9871c7d8d38acc5ce2c52aed2
TEST: unit tests pass, manually did image build/flash/syncs.
|
|
Abstracts Platforms into a unified object. Not yet
integrated.
BUG: 28401438
Change-Id: I7c727f277c4493e0bd93339fc614f2d2d93e77c7
TEST: unit tests pass
|
|
Bug: 28530837
Test: looked at the markdown in gitiles
Change-Id: Ie4624d47a466f5d67a1f9dffa86ff3ef8b9929a0
|
|
Change the os.chmod() call to use the stat constants
rather than 0o600, and add a unit test to make sure that
the permissions are being set properly.
Bug: 27718898
Test: `python test_runner.py` passes
Change-Id: Ifea8b99e21f4914b8235733e575d948d5d183b86
|
|
There were a few old brunch/BDKv1 commands that still manually added a
REMAINDER arg rather than using the new parsing features. This CL moves
them over to the new parsing and removes manual '--' checking.
Bug: 28182026
Test: python lib/test_runner.py
Test: Checked several legacy commands to make sure arguments parsed
the same before and after this CL:
$ gdbclient.py
$ gdbclient.py -x foo bar
$ m -j81
$ mm -j81
$ brunch product build -- -j81
Change-Id: Idb5ad19fe502d16dbfc311dd5c5b0644c82ecbda
|
|
Check that commit messages contain a 'Test: ' line.
Bug: 28320807
Test: Could not upload this CL without this line.
Change-Id: Id5a55d483c1644f85fc88e32d3b307fdc80a51aa
|
|
Bug: 28320810
Test: Tried to upload a CL with broken unit tests
Change-Id: Ibf17e337b2915fe46a4bead2999f7d6090e63af4
|
|
When test_runner.py has any unit tests fail, exits with a non-zero
return code so that test_runner.py can be called from scripts.
Bug: 28321483
Test: Make a unit test fail. Checked the exit code.
Change-Id: Ib6a9a753d26cd00a4a8785193b03ebb76f7f1d98
|
|
Bug: 28319301
Test: Unable to submit this CL without the above Bug line.
Change-Id: I806729bdd1337adfac6575c66d5214f9747ce6e9
|
|
In order to make Bdk metrics more useful, send the command
type in all hits.
Bug: 28054708
Change-Id: Ib2d0b68a61e790d4c58af221562a76d9214c8d49
|
|
Fix a few last style issues.
Bug: 28007659
Test: `python test_runner.py` passes
Test: pylint passes
Change-Id: Ib559fa6192e662658e0290f7279a4c14d5a04454
|
|
Fixed up bsp integration tests as possible,
disabled other tests for now and opened bugs.
BUG: 28169855
TEST: unit tests pass
TEST: sh bdk_tests.sh passes
Change-Id: I22b8594d13952312980620f4d747fdfad8ac352c
|
|
Enables the pylint preupload hook. Since the Bdk's main entry
point is not the top-most directory, it adds 'cli/lib' to the
front of the PYTHONPATH. It has to be added to the front, due
to a conflict with pylint's own 'test' module when the Bdk's
modules call 'from test import stubs' or other imports from the
test folder.
Bug: 27926782
Test: Uploading a CL runs pylint.
Change-Id: I4e99868db872fc09151b91ae26724e30a601bacc
|
|
Convert all the remaining files to a 4 space indent
to comply with PEP8 style rules. ALso fixed up a few
other style issues that were recently introduced.
Bug: 28007659
Test: `python test_runner.py` passes.
Test: pylint passes.
Change-Id: I519246493407ca8cd4a7a5da84140a6e67618592
|
|
Convert all files in the project/ folder to a 4 space indent
to comply with PEP8 style rules.
Bug: 28007659
Test: `python test_runner.py` passes.
Test: pylint passes.
Change-Id: Ie558e256e0c343d4786f5fd7f18a671446e79c41
|
|
If cache_root/system/etc/fs_config_* exists,
append it to the generated fs_config_* to ensure
that system image generation does not miss existing
customizations.
Ordering matters and this approach allows for product
fs_config_* values to override pre-existing. As this is
largely only relevant on /system, it seems to be the correct
layering.
(In fact, it may be worth placing the final fs_config_*
files in system/etc/*.)
BUG=27905017
TEST=manually check fs_config_files that were generated. added new test_runner.py
Change-Id: Iabb1eac470c6bacc8524f8431010aceb86c762b5
|
|
Update bsp configuration to fetch dragonboard v2.1 binaries.
BUG=none
Change-Id: I5d4c6de139b71ce55ed3c7fa45aec03aa98e2756
|
|
Provision requires linking.
BUG: 28274249
TEST: unit tests
Change-Id: I18a6205b9ab0218bcd8a03729643e7122215306c
|
|
The provision-device scripts assume the BSP is linked.
Longer term a better solution might exist,
but this will do for now.
BUG: 288271372
TEST: unit tests pass
Change-Id: I0056885eb44d1a32652f02cdd9edbea9f95d80c7
|
|
Convert all files in the environment/ folder to a 4 space indent
to comply with PEP8 style rules.
Bug: 28007659
Test: `python test_runner.py` passes.
Test: pylint passes.
Change-Id: Ib079be15e5ecc2cb705b5270e0dd730f490080dc
|
|
The example Makefile from bdk environment setup now
sets just 3 variables at the top (BDK, DEVICE, OS) that
the user might need to change, preventing the need to change
these in multiple places. This is particularly useful for sharing
a Makefile between collaborators, as one only needs to change
the path to their BDK command.
BUG: 27747562
Change-Id: I3533fb36f9217618b0f0212178372db64297a093
TEST: unit tests pass
|
|
Fixed up all the instances of CapWords() method names to use the
proper PEP8 lower_with_under() style.
Bug: 27836335
Test: `python test_runner.py` passes
Test: pylint passes
Change-Id: I130dcd3db000994d19de09d01c8f3aa826044244
|
|
Convert all files in the core/ folder to a 4 space indent
to comply with PEP8 style rules.
Bug: 28007659
Test: `python test_runner.py` passes.
Test: pylint passes.
Change-Id: If470162a50e29621cea84aef02dadb816ca1c46c
|
|
Convert all files in the bsp/ folder to a 4 space indent
to comply with PEP8 style rules.
Bug: 28007659
Test: `python test_runner.py` passes.
Test: pylint passes.
Change-Id: I9ed93ee77acccaa6b4b30a2a2fe4b9ab02546a35
|
|
This change includes /system using a single
recurive Copy in the OS pack that provides
os.core.
At the same time, this change fixes a few bugs:
- Unmanaged files were being ignoreѕ after /system
was moved to /root/system.
- image_info.txt rewriting we adding newlines on every
re-run.
- Don't use AddFile on symlinks and enable symlinks=True
on AddDirs (though we may want to parameterize <copy>.
When fixing the first issue while also moving /system
management into CreateTargetCache, the unmanaged file
clean up needed to be optimized. While python3 will
bring a better os.scandir, in the meantime, os.walk was
used minimally with all tweaking done after using set()
operations. This appears to keep performance in line
with system image creation while ensuring that the files
in the target cache are all intended to end up in the final
image -- even when it was just an iterative rebuild.
TEST=manual build; new unittests
BUG=28208639
Change-Id: I459ccca076921dfe0c7f2365deba98d6bab26162
|
|
Instead of the older flow using True/False.
Uses ToolWrapper for the tools.
Updates ToolWrapper to use Popen instead of
subprocess, so that stdout/stderr can be read if
desired.
BUG: https://b/27930418, https://b/27930909
TEST: unit tests pass
Change-Id: Ida705491c6fbd18f987e5281bb278e0b1edef9ca
|
|
Convert most files in the commands/ folder to a 4 space indent
to comply with PEP8 style rules. This CL skips
commands/v2/build/image.py, to avoid merge conflicts with
http://r.android.com/216174. That file will be fixed up in
a later CL.
Bug: 28007659
Test: `python test_runner.py` passes.
Test: pylint passes.
Change-Id: I1344907a8b346e054b6b5b3c8201d9563142543f
|
|
VERSION: Updated to 11.1.0
bsp_manifest.json: Updated BSPs to 11.1 version
BUG=28247668
TEST=none
Change-Id: I5cf984525d3b89921a9dffc9ed5b903b0b4ced88
|
|
Convert all files in the cli/ folder to a 4 space indent
to comply with PEP8 style rules.
Bug: 28007659
Test: `python test_runner.py` passes.
Test: pylint passes.
Change-Id: I1820ae24afc85cecc65e8b3813dee023aa1682d3
|
|
The Android build usually passes the 'file_contexts.bin' file to
'make_ext4fs':
make_ext4fs -S out/target/product/brilloemulator_arm/root/file_contexts.bin
Passing the 'file_contexts' text file also works, but that file has not
been checked against the SELinux policy to see if labels are defined.
Fix this by:
1-Compiling SELinux policy files *before* calling _CreateBuildProps().
2-Skipping the hardcoded definition of
'{odm|system}(/.*)? u:object_r:system_file:s0'.
3-Including the 'file_contexts' text file found in the cache directory
when generating the 'file_contexts.bin' file.
4-Putting the compiled files in the cache directory.
5-Telling 'make_ext4fs' to use the newly-generated 'file_contexts.bin'
files from the cache directory.
Bug: 27409446
Change-Id: I33d8c8d9a843e5efca39042248b16a30b423f891
|