July 2016 - U-Boot

[U-Boot] Please pull u-boot-dm
by Simon Glass 08 Jul '16

08 Jul '16

Hi Tom, A little fix. The following changes since commit e8009beff6d5c55c1bf1ae8184791f167e6378b0: Merge git://git.denx.de/u-boot-arc (2016-07-04 11:46:21 -0400) are available in the git repository at: git://git.denx.de/u-boot-dm.git for you to fetch changes up to 3cc5cda761c14628b25131bfc0db5dee433a52aa: mmc: msm_sdhci: Set mmc->dev pointer in msm_sdc_probe() (2016-07-07 10:10:29 -0600) ---------------------------------------------------------------- Mateusz Kulikowski (1): mmc: msm_sdhci: Set mmc->dev pointer in msm_sdc_probe() drivers/mmc/msm_sdhci.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) Regards, Simon

2 1

[U-Boot] [PATCH] test/py: fix CONFIG_ tests
by Stephen Warren 08 Jul '16

08 Jul '16

From: Stephen Warren <swarren(a)nvidia.com> Some CONFIG_ variables were recently renamed, but test/py wasn't updated to match. This causes some tests to be skipped. Fix test/py so the tests are run. Fixes: 11636258981a ("Rename reset to sysreset") Fixes: f1f9d4fac527 ("hush: complete renaming CONFIG_SYS_HUSH_PARSER to CONFIG_HUSH_PARSER") Cc: Masahiro Yamada <yamada.masahiro(a)socionext.com> Signed-off-by: Stephen Warren <swarren(a)nvidia.com> --- test/py/tests/test_hush_if_test.py | 8 ++++---- test/py/tests/test_sandbox_exit.py | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/test/py/tests/test_hush_if_test.py b/test/py/tests/test_hush_if_test.py index 1eeaa5b0471a..b572538528e1 100644 --- a/test/py/tests/test_hush_if_test.py +++ b/test/py/tests/test_hush_if_test.py @@ -109,27 +109,27 @@ def exec_hush_if(u_boot_console, expr, result): response = u_boot_console.run_command(cmd) assert response.strip() == str(result).lower() -(a)pytest.mark.buildconfigspec('sys_hush_parser') +(a)pytest.mark.buildconfigspec('hush_parser') def test_hush_if_test_setup(u_boot_console): """Set up environment variables used during the "if" tests.""" u_boot_console.run_command('setenv ut_var_nonexistent') u_boot_console.run_command('setenv ut_var_exists 1') -(a)pytest.mark.buildconfigspec('sys_hush_parser') +(a)pytest.mark.buildconfigspec('hush_parser') @pytest.mark.parametrize('expr,result', subtests) def test_hush_if_test(u_boot_console, expr, result): """Test a single "if test" condition.""" exec_hush_if(u_boot_console, expr, result) -(a)pytest.mark.buildconfigspec('sys_hush_parser') +(a)pytest.mark.buildconfigspec('hush_parser') def test_hush_if_test_teardown(u_boot_console): """Clean up environment variables used during the "if" tests.""" u_boot_console.run_command('setenv ut_var_exists') -(a)pytest.mark.buildconfigspec('sys_hush_parser') +(a)pytest.mark.buildconfigspec('hush_parser') # We might test this on real filesystems via UMS, DFU, 'save', etc. # Of those, only UMS currently allows file removal though. @pytest.mark.boardspec('sandbox') diff --git a/test/py/tests/test_sandbox_exit.py b/test/py/tests/test_sandbox_exit.py index d1aa3083f458..4e333ecedbf8 100644 --- a/test/py/tests/test_sandbox_exit.py +++ b/test/py/tests/test_sandbox_exit.py @@ -7,7 +7,7 @@ import pytest import signal @pytest.mark.boardspec('sandbox') -(a)pytest.mark.buildconfigspec('reset') +(a)pytest.mark.buildconfigspec('sysreset') def test_reset(u_boot_console): """Test that the "reset" command exits sandbox process.""" -- 2.9.0

2 1

[U-Boot] [PATCH 00/11] buildman: Make the tool friendlier for first-time users
by Simon Glass 08 Jul '16

08 Jul '16

This makes a few minor improvements to buildman to make it work more easiler for first-time users: - Improve progress and warning messages when fetching toolchains - Fix a bug where toolchain paths can be overwritten when fetching - Note at the top of the help how to get started Also this series removes MAKEALL. Since buildman has been around for 3 years it may be time to do this. If not, we can leave it for now. Simon Glass (11): buildman: Tidy up the README a little buildman: Automatically create a config file if needed buildman: Fix the 'help' test to use the correct path buildman: Allow the toolchain error to be suppressed buildman: Improve the toolchain progress/error output buildman: Fix a typo in TestSettingsHasPath() buildman: Drop the toolchain error when downloading toolchains buildman: Avoid overwriting existing toolchain entries buildman: Add a quick-start note Drop the MAKEALL tool Drop references to MAKEALL in the documentation MAKEALL | 850 ------------------------------------- README | 35 +- board/Barix/ipam390/README.ipam390 | 12 +- doc/README.sha1 | 5 +- tools/buildman/README | 67 ++- tools/buildman/bsettings.py | 64 +++ tools/buildman/control.py | 26 +- tools/buildman/func_test.py | 2 +- tools/buildman/toolchain.py | 73 +++- 9 files changed, 194 insertions(+), 940 deletions(-) delete mode 100755 MAKEALL -- 2.8.0.rc3.226.g39d4020

3 24

[U-Boot] what are valid formats for initrd image downloaded and used by "bootm"
by Robert P. J. Day 08 Jul '16

08 Jul '16

using yocto project to build artifacts to tftp down to a board for "bootm" command -- what are the valid formats for the "initrd" object that can be recognized by "bootm"? since YP can generate a *ton* of different image types. thanks. rday -- ======================================================================== Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ========================================================================

2 6

[U-Boot] [PATCH] mmc: msm_sdhci: Set mmc->dev pointer in msm_sdc_probe()
by Mateusz Kulikowski 08 Jul '16

08 Jul '16

MMC core expects (now) valid mmc->dev pointer. During conversion in commit cffe5d86 not every driver was updated. This patch fixes crash while accessing MMC on boards using Qualcomm SDHCI controller. Signed-off-by: Mateusz Kulikowski <mateusz.kulikowski(a)gmail.com> --- This patch fixes MMC support on dragonboard. Without it attempts to access MMC caused null-pointer derefernece. drivers/mmc/msm_sdhci.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/mmc/msm_sdhci.c b/drivers/mmc/msm_sdhci.c index 64bbf0c..96dcdbe 100644 --- a/drivers/mmc/msm_sdhci.c +++ b/drivers/mmc/msm_sdhci.c @@ -136,7 +136,12 @@ static int msm_sdc_probe(struct udevice *dev) host->version = sdhci_readw(host, SDHCI_HOST_VERSION); /* automatically detect max and min speed */ - return add_sdhci(host, 0, 0); + ret = add_sdhci(host, 0, 0); + if (ret) + return ret; + host->mmc->dev = dev; + + return 0; } static int msm_sdc_remove(struct udevice *dev) -- 2.7.4

3 3

[U-Boot] BayTrail PCIe x4 slot (Soft-Strap?)
by Stefan Roese 08 Jul '16

08 Jul '16

Hi! I do have BayTrail / FSP related question. I'm currently trying to use a DFI QSeven SoM which has one x4 PCIe slot instead of the usual 4 x1 slots. So all 4 PCIe lanes are used by the first PCIe controller. With the current U-Boot, all 4 PCIe controllers are enabled by the FSP : 00:1c.0 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 1 (rev 11) 00:1c.1 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 2 (rev 11) 00:1c.2 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 3 (rev 11) 00:1c.3 PCI bridge: Intel Corporation Atom Processor E3800 Series PCI Express Root Port 4 (rev 11) In this configuration, the x4 PCIe card that is installed in the PCIe slot is not detected. The system always generated hotplug events for all for ports, but the link is not established. The original DFI BIOS only enables the first PCIe controller. The controllers 1...3 are not visible via lspci. Here the 4x link is established and the 4x PCIe card is detected correctly. My question now is, how can I enable this 4x link on the first PCIe controller via U-Boot / FSP? I have found no option on how to configure the PCIe controllers in the FSP dts properties. So that only the first controller is enabled and visible via lspci etc. The BayTrail datasheet mentions this to configure the PCIe setup in chapter "23.2.1 Root Port Configurations": " Root port configurations are set by SoftStraps stored in SPI flash, and the default option is “(4) x1”. Links for each root port will train automatically to the maximum possible for each port. " Where is this SoftStraps in the SPI flash located? I've found this page mentioning that its a offset 0x100: https://embedded.communities.intel.com/thread/8539 But I fail to find any documentation for all those Soft-Strap Registers / Values in the SPI flash. Does anyone have some further infos / documentation on this? How to enable 4x PCIe lanes for one PCIe controller on BayTrail / Atom? Thanks, Stefan

2 6

Re: [U-Boot] Problem loading boot script from ext4 mmc on sunxi H3
by Michal Suchanek 08 Jul '16

08 Jul '16

Hello, On 29 June 2016 at 10:45, Karsten Merker <merker(a)debian.org> wrote: > On Wed, Jun 29, 2016 at 09:30:33AM +0200, Michal Suchanek wrote: > >> I tried loading system with recent u-boot but it does not work. >> >> Trying some ext4ls shows there is some problem accessing the filesystem. >> >> Not sure if this should be attributed to the ext driver or to the mmc >> driver or something else entirely. > > I haven't tested that myself, but I have seen reports on other > platforms that the u-boot ext4 driver has problems with ext4 > filesystems which use the "flex_bg" filesystem feature, as that > causes certain changes to the on-disk layout compared to ext4 > without this feature. From what people have reported, it appears > that "flex_bg" is enabled by default on ext4 filesystems created > with a recent mkfs.ext4 version. > Reformatting without flex_bg does not seem to have any effect. However, ls seems to give some random stuff for directories other than / so some similar remapping feature could cause this. Thanks Michal

2 2

[U-Boot] [PATCH] mmc: sdhci: clean up time out detection
by Masahiro Yamada 08 Jul '16

08 Jul '16

The current timeout detection logic is not very nice; it calls get_timer(start) in the while() loop, and then calls it again after the loop to check if a timeout error happened. Because of the time difference between the two calls of get_time(), the reason detected after the loop may not be really true. Signed-off-by: Masahiro Yamada <yamada.masahiro(a)socionext.com> --- drivers/mmc/sdhci.c | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/drivers/mmc/sdhci.c b/drivers/mmc/sdhci.c index 604f18d..0a1882d 100644 --- a/drivers/mmc/sdhci.c +++ b/drivers/mmc/sdhci.c @@ -243,17 +243,17 @@ static int sdhci_send_command(struct mmc *mmc, struct mmc_cmd *cmd, stat = sdhci_readl(host, SDHCI_INT_STATUS); if (stat & SDHCI_INT_ERROR) break; - } while (((stat & mask) != mask) && - (get_timer(start) < SDHCI_READ_STATUS_TIMEOUT)); - if (get_timer(start) >= SDHCI_READ_STATUS_TIMEOUT) { - if (host->quirks & SDHCI_QUIRK_BROKEN_R1B) - return 0; - else { - printf("%s: Timeout for status update!\n", __func__); - return TIMEOUT; + if (get_timer(start) >= SDHCI_READ_STATUS_TIMEOUT) { + if (host->quirks & SDHCI_QUIRK_BROKEN_R1B) { + return 0; + } else { + printf("%s: Timeout for status update!\n", + __func__); + return TIMEOUT; + } } - } + } while ((stat & mask) != mask); if ((stat & (SDHCI_INT_ERROR | mask)) == mask) { sdhci_cmd_done(host, cmd); -- 1.9.1

2 1

[U-Boot] Brotli Compression to Fit Image/bzImage
by vinoth eswaran 08 Jul '16

08 Jul '16

Hello, I am working on an embedded project using Minnowboard Max with U-boot and customised Linux kernel. To optimize boot time, currently I am comparing the different comparison algorithms and have read about Brotli compression, which seems to be good. So I have planned to test and see how good is Brotli compression for my use case? The current Linux kernel and U-boot doesn't support this compression, so I have to add this compression algorithm code. I am seeing two ways of doing this, 1. In U-Boot Fit Image creation from vmlinux. Adding Brotli compression to mkimage tool and decompressor to U-Boot. Here we are using mkimage tool to create the image.fit. I can do some changes in mkimage and add the decompressor to the U-boot code 2. In Linux Kernel bzImage --> adding the Brotli compression and decompression to Linux Kernel and change the default compression from gzip to brotli in the Linux kernel Configuration. I don't know which way is comparably easier to implement, any suggestions on these topic will be of great help. Have any body tried this algorithm for the Linux Kernel?? Mit Freundlichen Grüßen VinothKumar +49 1798909072

3 3

[U-Boot] [PATCH] sunxi: mmc: increase status register polling rate for data transfers
by Tobias Doerffel 08 Jul '16

08 Jul '16

With a recent bunch of SD3.0 cards in our A20-based board we experienced data transfer rates of about 250 KiB/s instead of 10 MiB/s with previous cards from the same vendor (both 4 GB/class 10). By increasing status register polling rate from 1 kHz to 1 MHz we were able to reach the original transfer rates again. With the old cards we now even reach about 16 MiB/s. Signed-off-by: Tobias Doerffel <tobias.doerffel(a)ed-chemnitz.de> --- drivers/mmc/sunxi_mmc.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/drivers/mmc/sunxi_mmc.c b/drivers/mmc/sunxi_mmc.c index ce2dc4a..36da3b3 100644 --- a/drivers/mmc/sunxi_mmc.c +++ b/drivers/mmc/sunxi_mmc.c @@ -269,18 +269,18 @@ static int mmc_trans_data_by_cpu(struct mmc *mmc, struct mmc_data *data) unsigned i; unsigned *buff = (unsigned int *)(reading ? data->dest : data->src); unsigned byte_cnt = data->blocksize * data->blocks; - unsigned timeout_msecs = byte_cnt >> 8; - if (timeout_msecs < 2000) - timeout_msecs = 2000; + unsigned timeout_usecs = ( byte_cnt >> 8 ) * 1000; + if (timeout_usecs < 2000000) + timeout_usecs = 2000000; /* Always read / write data through the CPU */ setbits_le32(&mmchost->reg->gctrl, SUNXI_MMC_GCTRL_ACCESS_BY_AHB); for (i = 0; i < (byte_cnt >> 2); i++) { while (readl(&mmchost->reg->status) & status_bit) { - if (!timeout_msecs--) + if (!timeout_usecs--) return -1; - udelay(1000); + udelay(1); } if (reading) -- 2.1.4

2 1