U-Boot issueshttps://source.denx.de/groups/u-boot/-/issues2024-03-01T12:57:54Zhttps://source.denx.de/u-boot/u-boot/-/issues/11Sandbox requires -d argument now2024-03-01T12:57:54ZTom RiniSandbox requires -d argument nowSince:
```
commit 059df5624b49c8f4935b634acebe9cdacfb5cab3
Author: Philippe Reynes <philippe.reynes@softathome.com>
Date: Mon Mar 28 22:56:53 2022 +0200
arch: Kconfig: imply BINMAN for SANDBOX
```
Running "./u-boot" by itself lead...Since:
```
commit 059df5624b49c8f4935b634acebe9cdacfb5cab3
Author: Philippe Reynes <philippe.reynes@softathome.com>
Date: Mon Mar 28 22:56:53 2022 +0200
arch: Kconfig: imply BINMAN for SANDBOX
```
Running "./u-boot" by itself leads to:
```
U-Boot 2022.04-rc5-00247-g059df5624b49 (Apr 25 2022 - 20:00:02 -0400)
DRAM: 128 MiB
binman_init failed:-2
initcall sequence 000055ff6b909c20 failed at call 0000000000167ac3 (err=-2)
### ERROR ### Please RESET the board ###
```
And you have to use `-d path/to/sandbox.dtb` as part of running.https://source.denx.de/u-boot/u-boot/-/issues/10awk incompatibility in tests2024-03-01T12:57:53ZSimon Glasssjg@chromium.orgawk incompatibility in testsFrom Patrick DELAUNAY <patrick.delaunay@foss.st.com>
For information, it seems the new test "test_env_text" failed when the
gawk is not installed on Ubuntu distribution,
or when /usr/bin/mawk is used as alternative (sudo update-alterna...From Patrick DELAUNAY <patrick.delaunay@foss.st.com>
For information, it seems the new test "test_env_text" failed when the
gawk is not installed on Ubuntu distribution,
or when /usr/bin/mawk is used as alternative (sudo update-alternatives
--config awk)
The test result is
test/py/tests/test_env.py:556: in test_env_text
check_script('''fred=123
test/py/tests/test_env.py:542: in check_script
assert result == expect
E assert '#define CONF...red=123\\0"\n' == '#define CONF...nie=456\\0"\n'
E - #define CONFIG_EXTRA_ENV_TEXT "ernie=456\0fred=123\0"
E ? ----------
E + #define CONFIG_EXTRA_ENV_TEXT "fred=123\0ernie=456\0"
E ? ++++++++++
------------------------------------------------------------ Captured
stdout call -------------------------------------------------------------
+awk -f <PATH>/u-boot/scripts/env2string.awk /tmp/tmp0zgiwrd9/infile
#define CONFIG_EXTRA_ENV_TEXT "fred=123\0"
+awk -f <PATH>/u-boot/scripts/env2string.awk /tmp/tmpq6xej0ct/infile
+awk -f <PATH>/u-boot/scripts/env2string.awk /tmp/tmpyrn10apn/infile
#define CONFIG_EXTRA_ENV_TEXT "ernie=456\0fred=123\0"
=> the env variables are sorted in alphabetic order in mawk output / in
creation order in gawk ouput
I don't found solution to be POSIX compliant and to guarantee the output
order
>> By default, when a for loop traverses an array, the order is undefined,
>> meaning that the awk implementation determines the order in which
>> the array is traversed. This order is usually based on the internal
>> implementation of arrays and will vary from one version of awk to
the next.
References:
https://www.gnu.org/software/gawk/manual/html_node/Controlling-Scanning.html
https://www.gnu.org/software/gawk/manual/html_node/Controlling-Array-Traversal.html
...
> +
> +END {
> + # Record the value of the variable now completed. If the variable is
> + # empty it is not set.
> + if (length(env) != 0) {
> + vars[var] = env
> + }
> +
> + if (length(vars) != 0) {
> + printf("%s", "#define CONFIG_EXTRA_ENV_TEXT \"")
> +
> + # Print out all the variables
ORDER is not guarantee here by awk for the loop on the "vars" array
Here according the awk implementation the test result can be
'fred=123\\0ernie=456\\0' => creation order
'ernie=456\\0fred=123\\0' => alphabetic order
and perhaps other order for other awk ?
do you think you can have a solution with POSIX awk ?
today I found only solution for gawk:
---------------------------- scripts/env2string.awk ----------------------------
index 1bfe9ed07a..f3215c369a 100644
@@ -81,7 +81,8 @@ END {
if (do_output) {
printf("%s", "#define CONFIG_EXTRA_ENV_TEXT \"")
- # Print out all the variables
+ # Print out all the variables by alphabetic order
+ PROCINFO["sorted_in"] = "@ind_str_asc"
for (var in vars) {
env = vars[var]
print var "=" vars[var] "\\0"
But this GNU feature must be avoid,
see commit 7acb32256831 ("env: Avoid using GNU features in awk")
Regardhttps://source.denx.de/u-boot/custodians/u-boot-marvell/-/issues/1D-link DNS325: U-boot only initializes one hard drive.2024-02-10T23:23:23ZPeter GranillaD-link DNS325: U-boot only initializes one hard drive.Problem:
The DNS325 is a 2-bay NAS. U-boot only sets the first hard drives "GPIO enable" line to high, not the second. This sometimes can cause issues with the Linux kernel in minimal environments where the kernel wont add the drive into...Problem:
The DNS325 is a 2-bay NAS. U-boot only sets the first hard drives "GPIO enable" line to high, not the second. This sometimes can cause issues with the Linux kernel in minimal environments where the kernel wont add the drive into the /dev directory automatically.
Solution I've found:
In the file `board/d-link/dns325/dns325.c` on line 92, add the following code to enable the second hard drive slot:
`kw_gpio_set_value(DNS325_GPIO_SATA1_EN , 1);`
(The macro `DNS325_GPIO_SATA1_EN` is already defined in `board/d-link/dns325/dns325.h`)
I tested this solution myself on real hardware, and confirmed that once i applied the patch, the second hard drive started working as expected.Stefan RoeseStefan Roesehttps://source.denx.de/u-boot/u-boot/-/issues/1Implement distro boot using bootflow2024-02-09T20:26:34ZSimon Glasssjg@chromium.orgImplement distro boot using bootflowAt present distro boot relies on lots of scripts.
We should be able to implement this with the bootflow design and drop the scripts.At present distro boot relies on lots of scripts.
We should be able to implement this with the bootflow design and drop the scripts.https://source.denx.de/u-boot/u-boot/-/issues/34Issues with CROSS_COMPILE in U-Boot Build2024-01-27T02:41:46ZWow WowIssues with CROSS_COMPILE in U-Boot BuildI'm encountering difficulties while attempting to build U-Boot with the specified CROSS_COMPILE configuration. Below is my build commands:
```bash
export PATH="/home/vagrant/x-tools/aarch64-rpi3-linux-gnu/bin/:$PATH"
export CROSS_COMPIL...I'm encountering difficulties while attempting to build U-Boot with the specified CROSS_COMPILE configuration. Below is my build commands:
```bash
export PATH="/home/vagrant/x-tools/aarch64-rpi3-linux-gnu/bin/:$PATH"
export CROSS_COMPILE=aarch64-rpi3-linux-gnu-
make CROSS_COMPILE=aarch64-rpi3-linux-gnu- poplar_defconfig
make CROSS_COMPILE=aarch64-rpi3-linux-gnu-
```
However, I'm facing an error:
```bash
/usr/bin/ld: skipping incompatible /home/vagrant/crosstool/ssl/lib/libssl.so when searching for -lssl
```
It appears that the ld program is not selecting the correct LD from the specified x-tools path. Could this issue be considered a bug, as LD or CC is not choosing the appropriate binary?https://source.denx.de/u-boot/u-boot/-/issues/33Raspberry Pi 4 cannot boot when two devices of the same model and capacity ar...2024-01-25T23:30:50ZDouglas SilvaRaspberry Pi 4 cannot boot when two devices of the same model and capacity are plugged in### To reproduce
You'll need two identical USB sticks - same size, same brand and model. Let's assume you would boot the OS from one of them, while the other would be just a removable storage medium. Also, remove the SD card from the slo...### To reproduce
You'll need two identical USB sticks - same size, same brand and model. Let's assume you would boot the OS from one of them, while the other would be just a removable storage medium. Also, remove the SD card from the slot, if present. Let's go USB-only.
When you turn on the Pi with both sticks connected, it will first throw up these errors:
```
ERROR: failure to add disk device usb_mass_storage.lun0, r = 20
Cannot initialize UEFI sub-system, r = 20
```
> I see the output from the serial console.
And then it will give up on USB and attempt to do a network-boot, at which point I can press `Ctrl + C` until I'm dropped to the U-Boot prompt.
OK, turn it off now. We'll start it again, but this time leaving only the bootable OS disk. With only one USB device plugged in, it should boot successfully from it.
### System info
- U-Boot 2021.10 (Sep 08 2023 - 11:13:24 -0600)
- Latest EEPROM version installed with raspi-config on Raspberry Pi OS (bookworm).
- Boot order set to boot from USB/NVMe first.
- OS: OpenBSD 7.4 (with full-disk encryption)
- Device: Raspberry Pi 4B (4GB)
### Additional info
The second (not-bootable) disk does not have the bootable MBR flag - I removed it. [OpenBSD's version] of `fdisk` automatically adds it. But it didn't make any difference.
I've experimented a bit with the U-Boot CLI, in an attempt to manually boot the OS. For example, when I run `bootefi bootmgr` I get the error `Cannot initialize UEFI sub-system`.
I will later gather and upload more detailed logs to this issue.
I believe the same problem was reported before on the [FreeBSD Bugzilla tracker](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256441).https://source.denx.de/u-boot/custodians/u-boot-dfu/-/issues/1Typos reported on GitHub2024-01-18T08:33:27ZTom RiniTypos reported on GitHubOver at https://github.com/Maalobs/u-boot/commit/9a21ed8ba722d904b68945f40ca6697b4b1cc4d4 as user has reported and fixed / enhanced the dfu documentation. These changes should be brought over and posted properly, crediting the original u...Over at https://github.com/Maalobs/u-boot/commit/9a21ed8ba722d904b68945f40ca6697b4b1cc4d4 as user has reported and fixed / enhanced the dfu documentation. These changes should be brought over and posted properly, crediting the original user for the work.Mattijs KorpershoekMattijs Korpershoekhttps://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/12bootph tags should be transistive to parents2024-01-03T13:32:45ZSimon Glasssjg@chromium.orgbootph tags should be transistive to parentsA bootph-all tag in a child should result in the same tag in the parent.
This is actually how the binding is written. While there is no obvious, elegant way to implement this, a brute-force approach would be to pre-process the .dtb to a...A bootph-all tag in a child should result in the same tag in the parent.
This is actually how the binding is written. While there is no obvious, elegant way to implement this, a brute-force approach would be to pre-process the .dtb to add imputed tags in the parents, before doing anything else.2023-12-31https://source.denx.de/u-boot/custodians/u-boot-imx/-/issues/1'make' error when building flash.bin target for imx93 11x11 evk2023-12-12T21:32:42ZAndrian Belinski'make' error when building flash.bin target for imx93 11x11 evkHello,
I am trying to build an u-boot flash.bin artifact on Ubuntu 20.04 using imx93_11x11_evk_defconfig with these commands:
```
export ARCH=arm64
export CROSS_COMPILE=/usr/bin/aarch64-linux-gnu-
make clean
make imx93_11x11_evk_defcon...Hello,
I am trying to build an u-boot flash.bin artifact on Ubuntu 20.04 using imx93_11x11_evk_defconfig with these commands:
```
export ARCH=arm64
export CROSS_COMPILE=/usr/bin/aarch64-linux-gnu-
make clean
make imx93_11x11_evk_defconfig
make flash.bin
```
The build process fails displaying the following output:
```
...
mkdir -p spl/dts/
FDTGREP spl/dts/dt-spl.dtb
COPY spl/u-boot-spl.dtb
CAT spl/u-boot-spl-dtb.bin
COPY spl/u-boot-spl.bin
SYM spl/u-boot-spl.sym
OBJCOPY u-boot-nodtb.bin
RELOC u-boot-nodtb.bin
CAT u-boot-dtb.bin
COPY u-boot.bin
echo "@make -f ./scripts/Makefile.build obj=arch/arm/mach-imx u-boot.cnt"
@make -f ./scripts/Makefile.build obj=arch/arm/mach-imx u-boot.cnt
make[1]: *** No rule to make target 'u-boot.cnt'. Stop.
make: *** [Makefile:1521: u-boot.cnt] Error 2
```Stefano BabicStefano Babichttps://source.denx.de/u-boot/u-boot/-/issues/26Fails to install patch-manager / patman2023-11-15T13:16:32ZSimon Glasssjg@chromium.orgFails to install patch-manager / patmanFrom: NishanthMenon Nishanth Menon
I think we may forgotten to deploy func_test.py (following log from a container that did python -m pip install patch-manager)
https://www.irccloud.com/pastebin/gO78fFtF/
```
> swuser@85618259d376:~/...From: NishanthMenon Nishanth Menon
I think we may forgotten to deploy func_test.py (following log from a container that did python -m pip install patch-manager)
https://www.irccloud.com/pastebin/gO78fFtF/
```
> swuser@85618259d376:~/u-boot$ git grep func_test tools/patman/
> tools/patman/__init__.py:__all__ = ['checkpatch', 'commit', 'control', 'func_test', 'get_maintainer',
> tools/patman/__main__.py:from patman import func_test
> tools/patman/__main__.py:if os.path.exists(func_test.TEST_DATA_DIR):
> tools/patman/__main__.py: from patman import func_test
> tools/patman/__main__.py: [test_checkpatch.TestPatch, func_test.TestFunctional,
> swuser@85618259d376:~/u-boot$ patman
> Traceback (most recent call last):
> File "/usr/local/bin/patman", line 5, in <module>
> from patman.__main__ import run_patman
> File "/usr/local/lib/python3.10/dist-packages/patman/__main__.py", line 23, in <module>
> from patman import func_test
> ImportError: cannot import name 'func_test' from 'patman' (/usr/local/lib/python3.10/dist-packages/patman/__init__.py)
> swuser@85618259d376:~/u-boot$ find tools/patman/ -iname func_test
> swuser@85618259d376:~/u-boot$ git grep func_test tools/patman
> tools/patman/__init__.py:__all__ = ['checkpatch', 'commit', 'control', 'func_test', 'get_maintainer',
> tools/patman/__main__.py:from patman import func_test
> tools/patman/__main__.py:if os.path.exists(func_test.TEST_DATA_DIR):
> tools/patman/__main__.py: from patman import func_test
> tools/patman/__main__.py: [test_checkpatch.TestPatch, func_test.TestFunctional,
> swuser@85618259d376:~/u-boot$ ls tools/patman/
> README.rst __main__.py checkpatch.py control.py get_maintainer.py patchstream.py patman.rst pyproject.toml series.py setup.py test test_settings.py
> __init__.py __pycache__ commit.py func_test.py gitutil.py patman project.py pytest.ini settings.py status.py test_checkpatch.py
> swuser@85618259d376:~/u-boot$ ls /usr/local/lib/python3.10/dist-packages/patman/
> README.rst __main__.py checkpatch.py control.py gitutil.py patman.rst series.py setup.py
> __init__.py __pycache__ commit.py get_maintainer.py patchstream.py project.py settings.py status.py
```https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/3buildman --branch doesn't handle ranges quite right2023-11-09T15:06:29ZTom Rinibuildman --branch doesn't handle ranges quite rightConsider the following:
```shell
$ git checkout -b first-branch aaeaef253619
Switched to a new branch 'first-branch'
$ git checkout -b second-branch e5b082a3c594
Switched to a new branch 'second-branch'
$ git branch -u first-branch
Branc...Consider the following:
```shell
$ git checkout -b first-branch aaeaef253619
Switched to a new branch 'first-branch'
$ git checkout -b second-branch e5b082a3c594
Switched to a new branch 'second-branch'
$ git branch -u first-branch
Branch 'second-branch' set up to track local branch 'first-branch'.
$ ./tools/buildman/buildman --dry-run --step 0 -b first-branch..
Dry run, so not doing much. But I would do this:
Building 2 commits for 1289 boards (16 threads, 1 job per thread)
Build directory: ../first-branch..
08ece5b3 dm: video: Cosmetic style fix
e5b082a3 Merge tag 'video-20230801' of https://source.denx.de/u-boot/custodians/u-boot-video
Total boards to build for each commit: 1289
$ git log --oneline first-branch..
e5b082a3c594 (HEAD -> second-branch) Merge tag 'video-20230801' of https://source.denx.de/u-boot/custodians/u-boot-video
b8d3a6c7d12f drivers: video: tidss: tidss_drv: Use kconfig VIDEO_REMOVE to remove video
3f9b5a7ffa75 drivers: video: tidss: tidss_drv: Change remove method
e1a0cafcfb85 video: bochs: Set the frame buffer size per configuration
f91f0e74df81 video: kconfig: Set default FB size for Bochs
185ae84af0cb video: kconfig: Drop the superfluous dependency
17cd80237b09 video: kconfig: Fix wrong text for the PCI default FB size
e1b46977dedd video: bochs: Remove the x86 dependency
ffe1c8379e82 video: bochs: Avoid using IO instructions to access VGA IO port
caae795a1c6a video: bochs: Drop the useless argument of bochs_vga_write()
5ee029a190d5 video: bochs: Drop inclusion of <asm/mtrr.h>
08ece5b3ec6c dm: video: Cosmetic style fix
```
This, thus far, is doing what I said, even if it's not perhaps what I meant. What I really want is the first commit to build be the top of `first-branch`:
```shell
$ git log -n1 --oneline first-branch
aaeaef253619 (first-branch) Merge https://source.denx.de/u-boot/custodians/u-boot-marvell
```
But I can't get that:
```shell
$ ./tools/buildman/buildman --dry-run --step 0 -b first-branch^..
Dry run, so not doing much. But I would do this:
Building 2 commits for 1289 boards (16 threads, 1 job per thread)
Build directory: ../first-branch^..
414236b8 i2c: i2c-gpio: Correctly handle new {sda, scl}-gpios bindings
e5b082a3 Merge tag 'video-20230801' of https://source.denx.de/u-boot/custodians/u-boot-video
Total boards to build for each commit: 1289
$ git log -n1 --oneline first-branch^
4e619e8d4fd6 Merge tag 'u-boot-rockchip-20230731' of https://source.denx.de/u-boot/custodians/u-boot-rockchip
```
So I don't see why `first-branch^` is different to buildman and to git. If I try to use `aaeaef253619` it uses `08ece5b3` again and `aaeaef253619^` is once again `414236b8`.
The use case I have here is that since I'm doing a size comparison I want the first build to be the upstream commit so that I can see changes introduced by the first commit in this branch (and so the commits used here are how I would review the video PR).Simon Glasssjg@chromium.orgSimon Glasssjg@chromium.orghttps://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/5binman: Limt the file extensions allowed on output images2023-11-09T15:05:39ZSimon Glasssjg@chromium.orgbinman: Limt the file extensions allowed on output imagesIt is hard to know what output files binman produces. Leaving aside that it produces various intermediate files (for which a list should be generated at some point), the images themselves should be easily identifiable.
Suggestion to sta...It is hard to know what output files binman produces. Leaving aside that it produces various intermediate files (for which a list should be generated at some point), the images themselves should be easily identifiable.
Suggestion to start:
.bin
.rom
.img
.itb
.fit2023-10-03https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/6buildman size check doesn't fully understand rodata2023-11-09T14:54:16ZTom Rinibuildman size check doesn't fully understand rodataWhen moving the long help text from "data" to "rodata" (by marking it as const), I see:
```
thunderx_88xx : all -2 data -3928 rodata +3926
u-boot: add: 0/-6, grow: 0/0 bytes: 0/-3926 (-3926)
f...When moving the long help text from "data" to "rodata" (by marking it as const), I see:
```
thunderx_88xx : all -2 data -3928 rodata +3926
u-boot: add: 0/-6, grow: 0/0 bytes: 0/-3926 (-3926)
function old new delta
source_help_text 40 - -40
imgextract_help_text 85 - -85
env_help_text 330 - -330
booti_help_text 728 - -728
bootm_help_text 910 - -910
fdt_help_text 1833 - -1833
```
Which is mostly, but not entirely right. If we build by hand and examine u-boot.map we see:
```
.rodata.fdt_help_text
0x000000000052411e 0x729 cmd/fdt.o
```
Which is what's expected. It seems that examining the rodata section is missing from the bloat-related options, in some cases.Simon Glasssjg@chromium.orgSimon Glasssjg@chromium.orghttps://source.denx.de/u-boot/u-boot/-/issues/23`wget` cmd's data is garbled and isn't equal to the file on the server2023-10-16T15:08:24ZTom Fitzhenry`wget` cmd's data is garbled and isn't equal to the file on the serverBackground:
* This occurs on commit "25edd247a84a31298c22a34ec5cf2851cbf61f70" (master as of 2023-10-14).
* U-boot is running on an RK3588 QuartzPro64, soon to be mainlined, similar to the evb-rk3588_defconfig.
* My desktop machine 192....Background:
* This occurs on commit "25edd247a84a31298c22a34ec5cf2851cbf61f70" (master as of 2023-10-14).
* U-boot is running on an RK3588 QuartzPro64, soon to be mainlined, similar to the evb-rk3588_defconfig.
* My desktop machine 192.168.1.101 runs a HTTP and TFTP server, serving a kernel iamge (sha1sum bbc059b2e3e34b7941ea378f82cb4ce7607a25e0) from the same directory.
The problem: If I load this image via u-boot's wget cmd, the sha1sum of the output doesn't match. OTOH, the TFTP output matches the expected sha1sum.
This manifested itself to me as kernel oops on most boots when I loaded the kernel over HTTP, perhaps expected for corrupted memory.
Please observe below the steps producing this:
```
=> setenv serverip 192.168.1.101
=> setenv bootfile Image
=> dhcp
ethernet@fe1b0000 Waiting for PHY auto negotiation to complete....... done
BOOTP broadcast 1
DHCP client bound to address 192.168.1.109 (715 ms)
Using ethernet@fe1b0000 device
TFTP from server 192.168.1.101; our IP address is 192.168.1.109
Filename 'Image'.
Load address: 0xc00800
Loading: #################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
##################################################
24.1 MiB/s
done
Bytes transferred = 41752584 (27d1808 hex)
=> echo $?
0
=> sha1sum 0xc00800 27d1808
sha1 for 00c00800 ... 033d2007 ==> bbc059b2e3e34b7941ea378f82cb4ce7607a25e0
=> wget 0xa000800 192.168.1.101:/Image
HTTP/1.0 200 OK| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |
Packets received 28899, Transfer Successful
Bytes transferred = 41752584 (27d1808 hex)
=> echo $?
0
=> sha1sum 0xa000800 27d1808
sha1 for 0a000800 ... 0c7d2007 ==> 5163de4e24ec7edd982bac5bfe9d5083fcb61bf4
=> sha1sum 0xc00800 808
sha1 for 00c00800 ... 00c01007 ==> 64ac9532ed551972a5e2c3cb4aaf84449dcbea64
=> sha1sum 0xa000800 808
sha1 for 0a000800 ... 0a001007 ==> 64ac9532ed551972a5e2c3cb4aaf84449dcbea64
=> sha1sum 0xc00800 d808
sha1 for 00c00800 ... 00c0e007 ==> c8e583ee0df2f85c1dd4a54799eaa7f76fce85f2
=> sha1sum 0xa000800 d808
sha1 for 0a000800 ... 0a00e007 ==> c3b9be07aa08880bc7e90ea712f9a663b5ff5cf3
```
This shows that:
* at least up to the first 0x808 bytes, the two outputs match.
* beyond 0xd808 bytes, the two outputs differ.
Relevant enabled config: CONFIG_PROT_TCP_SACK=y
Shall I check whether this reproduces on the proposed "net/lwip: add lwip library for the network stack"[0]?
0. https://lore.kernel.org/u-boot/20230914161828.3662-1-maxim.uvarov@linaro.org/https://source.denx.de/u-boot/u-boot/-/issues/22Build error in "rk3568_common.h" using "soquartz-model-a-rk3566" defconfig in...2023-09-06T21:35:57ZParzival WolframBuild error in "rk3568_common.h" using "soquartz-model-a-rk3566" defconfig in version "v2023.10-rc4"Using v2023.10-rc2 through rc4 tags, trying to build using the `soquartz-model-a-rk3566` defconfig results in the following error:
```plaintext
In file included from include/configs/quartz64_rk3566.h:8,
from include/con...Using v2023.10-rc2 through rc4 tags, trying to build using the `soquartz-model-a-rk3566` defconfig results in the following error:
```plaintext
In file included from include/configs/quartz64_rk3566.h:8,
from include/config.h:3,
from include/common.h:16,
from env/common.c:10:
include/configs/rk3568_common.h:33:23: error: expected ‘}’ before ‘PARTS_DEFAULT’
33 | "partitions=" PARTS_DEFAULT \
| ^~~~~~~~~~~~~
include/env_default.h:120:9: note: in expansion of macro ‘CFG_EXTRA_ENV_SETTINGS’
120 | CFG_EXTRA_ENV_SETTINGS
| ^~~~~~~~~~~~~~~~~~~~~~
In file included from env/common.c:32:
include/env_default.h:27:36: note: to match this ‘{’
27 | const char default_environment[] = {
| ^
```https://source.denx.de/u-boot/custodians/u-boot-efi/-/issues/8efi_delete_handle must delete handle from events2023-08-30T07:16:47ZHeinrich Schuchardtxypron.glpk@gmx.deefi_delete_handle must delete handle from eventsWhen a protocol interface is installed a reference to the handle is added to events that have been registered with RegisterProtocolNotify(). The same handle may be referenced multiple times in an event and in multiple events.
Before del...When a protocol interface is installed a reference to the handle is added to events that have been registered with RegisterProtocolNotify(). The same handle may be referenced multiple times in an event and in multiple events.
Before deleting a handle in efi_delete_handle() we must remove all handle references in events.Heinrich Schuchardtxypron.glpk@gmx.deHeinrich Schuchardtxypron.glpk@gmx.dehttps://source.denx.de/u-boot/custodians/u-boot-rockchip/-/issues/1rk3568 build failed2023-08-18T07:48:34ZAnton Valuyskikhrk3568 build failedDear sirs,
when I try to build u-boot for Rockchip's RK3568 evaluation board I have the following error:
CC arch/arm/mach-rockchip/rk3568/clk_rk3568.o
arch/arm/mach-rockchip/cpu-info.c: In function 'get_reset_cause':
arch/arm/ma...Dear sirs,
when I try to build u-boot for Rockchip's RK3568 evaluation board I have the following error:
CC arch/arm/mach-rockchip/rk3568/clk_rk3568.o
arch/arm/mach-rockchip/cpu-info.c: In function 'get_reset_cause':
arch/arm/mach-rockchip/cpu-info.c:24:13: error: invalid use of undefined type 'struct rockchip_cru'
24 | switch (cru->glb_rst_st) {
make[1]: *** [scripts/Makefile.build:256: arch/arm/mach-rockchip/cpu-info.o] Error 1
make[1]: *** Waiting for unfinished jobs....
While investigating the problem I've found that:
1) in included file asm/arch-rockchip/cru.h there's no any links to file asm/arch-rockchip/cru_rk3568.h where the similar struct is defined. I've made a modification into asm/arch-rockchip/cru.h as:
--- a/arch/arm/include/asm/arch-rockchip/cru.h
+++ b/arch/arm/include/asm/arch-rockchip/cru.h
@@ -15,6 +15,8 @@
#include <asm/arch-rockchip/cru_rk3288.h>
#elif defined(CONFIG_ROCKCHIP_RK3399)
#include <asm/arch-rockchip/cru_rk3399.h>
+#elif defined(CONFIG_ROCKCHIP_RK3568)
+#include <asm/arch-rockchip/cru_rk3568.h>
#endif
/* CRU_GLB_RST_ST */
and then
2) there's no any mention of rockchip_cru struct there, in cru-rk3568.h
I've modified it as:
--- a/arch/arm/include/asm/arch-rockchip/cru_rk3568.h
+++ b/arch/arm/include/asm/arch-rockchip/cru_rk3568.h
@@ -106,6 +106,8 @@ struct rk3568_cru {
unsigned int emmc_con[2];/* Address Offset: 0x0598 */
};
+#define rockchip_cru rk3568_cru
check_member(rk3568_cru, mode_con00, 0xc0);
check_member(rk3568_cru, softrst_con[0], 0x400);
Am I doing something wrong and there's a better way how to get rid of an error?
Thank you!Kever Yangkever.yang@rock-chips.comKever Yangkever.yang@rock-chips.comhttps://source.denx.de/u-boot/u-boot/-/issues/21D-link DNS325: U-boot only initializes one hard drive.2023-08-10T19:26:17ZPeter GranillaD-link DNS325: U-boot only initializes one hard drive.Problem:
The DNS325 is a 2-bay NAS. U-boot only sets the first hard drives "GPIO enable" line to high, not the second. This sometimes can cause issues with the Linux kernel in minimal environments where the kernel wont add the drive into...Problem:
The DNS325 is a 2-bay NAS. U-boot only sets the first hard drives "GPIO enable" line to high, not the second. This sometimes can cause issues with the Linux kernel in minimal environments where the kernel wont add the drive into the /dev directory automatically.
Solution I've found:
In the file `board/d-link/dns325/dns325.c` on line 92, add the following code to enable the second hard drive slot:
`kw_gpio_set_value(DNS325_GPIO_SATA1_EN , 1);`
(The macro `DNS325_GPIO_SATA1_EN` is already defined in `board/d-link/dns325/dns325.h`)
I tested this solution myself on real hardware, and confirmed that once i applied the patch, the second hard drive started working as expected.https://source.denx.de/u-boot/u-boot/-/issues/20'make' error when building flash.bin target for imx93 11x11 evk2023-08-09T23:30:10ZAndrian Belinski'make' error when building flash.bin target for imx93 11x11 evkHello,
I am trying to build an u-boot flash.bin artifact on Ubuntu 20.04 using imx93_11x11_evk_defconfig with these commands:
```
export ARCH=arm64
export CROSS_COMPILE=/usr/bin/aarch64-linux-gnu-
make clean
make imx93_11x11_evk_defcon...Hello,
I am trying to build an u-boot flash.bin artifact on Ubuntu 20.04 using imx93_11x11_evk_defconfig with these commands:
```
export ARCH=arm64
export CROSS_COMPILE=/usr/bin/aarch64-linux-gnu-
make clean
make imx93_11x11_evk_defconfig
make flash.bin
```
The build process fails displaying the following output:
```
...
mkdir -p spl/dts/
FDTGREP spl/dts/dt-spl.dtb
COPY spl/u-boot-spl.dtb
CAT spl/u-boot-spl-dtb.bin
COPY spl/u-boot-spl.bin
SYM spl/u-boot-spl.sym
OBJCOPY u-boot-nodtb.bin
RELOC u-boot-nodtb.bin
CAT u-boot-dtb.bin
COPY u-boot.bin
echo "@make -f ./scripts/Makefile.build obj=arch/arm/mach-imx u-boot.cnt"
@make -f ./scripts/Makefile.build obj=arch/arm/mach-imx u-boot.cnt
make[1]: *** No rule to make target 'u-boot.cnt'. Stop.
make: *** [Makefile:1521: u-boot.cnt] Error 2
```https://source.denx.de/u-boot/custodians/u-boot-dm/-/issues/2`./tools/buildman/buildman --maintainer-check` dislikes case of no configs li...2023-08-04T02:42:02ZTom Rini`./tools/buildman/buildman --maintainer-check` dislikes case of no configs listedOne message I see right now is:
```
WARNING: orphaned defconfig in board/mikrotik/crs3xx-98dx3236/MAINTAINERS ending at line 7
```
And the file is:
```text
CRS3XX-98DX3236 BOARD
M: Luka Kovacic <luka.kovacic@sartura.hr>
M: Luka Perkov <l...One message I see right now is:
```
WARNING: orphaned defconfig in board/mikrotik/crs3xx-98dx3236/MAINTAINERS ending at line 7
```
And the file is:
```text
CRS3XX-98DX3236 BOARD
M: Luka Kovacic <luka.kovacic@sartura.hr>
M: Luka Perkov <luka.perkov@sartura.hr>
S: Maintained
F: board/mikrotik/crs3xx-98dx3236/
F: include/configs/crs3xx-98dx3236.h
CRS305-1G-4S BOARD
M: Luka Kovacic <luka.kovacic@sartura.hr>
M: Luka Perkov <luka.perkov@sartura.hr>
S: Maintained
F: configs/crs305-1g-4s_defconfig
F: configs/crs305-1g-4s-bit_defconfig
F: arch/arm/dts/armada-xp-crs305-1g-4s.dts
F: arch/arm/dts/armada-xp-crs305-1g-4s-bit.dts
CRS326-24G-2S BOARD
M: Luka Kovacic <luka.kovacic@sartura.hr>
M: Luka Perkov <luka.perkov@sartura.hr>
S: Maintained
F: configs/crs326-24g-2s_defconfig
F: configs/crs326-24g-2s-bit_defconfig
F: arch/arm/dts/armada-xp-crs326-24g-2s.dts
F: arch/arm/dts/armada-xp-crs326-24g-2s-bit.dts
CRS328-4C-20S-4S BOARD
M: Luka Kovacic <luka.kovacic@sartura.hr>
M: Luka Perkov <luka.perkov@sartura.hr>
S: Maintained
F: configs/crs328-4c-20s-4s_defconfig
F: configs/crs328-4c-20s-4s-bit_defconfig
F: arch/arm/dts/armada-xp-crs328-4c-20s-4s.dts
F: arch/arm/dts/armada-xp-crs328-4c-20s-4s-bit.dts
```
And if I just delete the blank line at line 7 it's now happy as I guess it parses the next entry too. If I add a configs/ line it is also now happy.