Hi Pali,
On Mon, 2 Aug 2021 at 23:04, Heinrich Schuchardt wrote:
>
> +cc Ilias
>
> On 8/2/21 3:18 PM, Pali Rohár wrote:
> > Macro U_BOOT_VERSION_STRING is already stored in variable version_string.
> > So use directly this variable instead of storing U_BOOT_VERSION_STRING into
> > temporary varia
Hi Rasmus,
On 02.08.21 17:00, Rasmus Villemoes wrote:
A board can have and make use of more than one watchdog device, say
one built into the SOC and an external gpio-petted one. Having
wdt-uclass only handle the first is both a little arbitrary and
unexpected.
So change initr_watchdog() so we v
Add support for disabling AHB bus and read entire flash contents via IP
bus only. Please note, this enables IP bus read using a quirk which can
be enabled directly in device-type data or in existence of an errata
where AHB bus may need to be disabled.
Signed-off-by: Kuldeep Singh
Acked-by: Jagan
Errata ERR050568 description says that "Flash access by FlexSPI AHB
command may not work with platform frequency equal to 300 MHz" on
LS1028A.
By default, smaller length reads(equal to RX FIFO size) are done by IP
bus and larger length reads using AHB bus. For adding errata workaround,
use IP bus
Le Tue, 3 Aug 2021 08:58:17 +,
a écrit :
> On 8/2/21 3:39 PM, Clément Léger wrote:
> > sama5d2 support from DRAM will be modified to use device tree
> > instead of hardcoded addresses. In order to prepare that, add the
> > memory node to sama5d2.dtsi file since the boards supported by
> > U-B
Parse DT in ofdata_to_platdata() callback instead of probe().
Signed-off-by: Patrice Chotard
---
drivers/spi/stm32_spi.c | 224 +++-
1 file changed, 132 insertions(+), 92 deletions(-)
diff --git a/drivers/spi/stm32_spi.c b/drivers/spi/stm32_spi.c
index bd851
This is the baseline support for the SIMATIC IOT2050 devices.
Changes in v6:
- rebased
- converted board README to docs/board/siemens/iot2050.rst
Changes in v5:
- rebased
- use DEFAULT_LINUX_BOOT_ENV from ti_armv7_common.h, rather than
home-grown values
- avoids misaligned kernel load
From: Jan Kiszka
Prepares for the addition of the IOT2050 board which is based on the TI
AM65x. The board comes in two variants, Basic and Advanced, so there are
separate dts files. Furthermore, the SPL has its own device tree.
Based on original board support by Le Jin, Gao Nian and Chao Zeng.
From: Jan Kiszka
This allows to use the watchdog in custom scripts but does not enforce
that the OS has to support it as well.
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 16
configs/iot2050_defconfig| 6 ++
2 files cha
From: Jan Kiszka
Add the DT entry for a watchdog based on RTI1. It requires additional
firmware on the MCU R5F cores to handle the expiry, e.g.
https://github.com/siemens/k3-rti-wdt. As this firmware will also lock
the power domain to protect it against premature shutdown, mark it
shared.
Aligns
From: Jan Kiszka
This adds support for the IOT2050 Basic and Advanced devices. The Basic
used the dual-core AM6528 GP processor, the Advanced one the AM6548 HS
quad-core version.
Both variants are booted via a Siemens-provided FSBL that runs on the R5
cores. Consequently, U-Boot support is targe
From: Jan Kiszka
To avoid the need of extra boot scripting on AM65x for loading a
watchdog firmware, add the required rproc init and loading logic for the
first R5F core to the watchdog start handler. In case the R5F cluster is
in lock-step mode, also initialize the second core. The firmware itse
Add i2c-analog-filter property in I2C nodes to enable analog
filter feature.
Signed-off-by: Patrice Chotard
---
arch/arm/dts/stm32f746.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/dts/stm32f746.dtsi b/arch/arm/dts/stm32f746.dtsi
index ba9b3cd03c..78facde2b5 100644
--- a
From: Patrick Delaunay
Today all the I2C instance point on the same global
variable stm32_i2c_setup according the compatible: i2c_priv->setup =
pointer to the same driver data.
This patch changes this driver data (stm32f7_setup and stm32mp15_setup)
to a const struct and move the timing struct 's
Add i2c-analog-filter property in I2C nodes to enable analog
filter feature.
Signed-off-by: Patrice Chotard
---
arch/arm/dts/stm32h743.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/dts/stm32h743.dtsi b/arch/arm/dts/stm32h743.dtsi
index ed6857512f..dbfebf07f2 100644
--- a
From: Patrick Delaunay
Replace driver internally coded enabling/disabling of the
analog-filter with the DT binding "i2c-analog-filter".
Signed-off-by: Patrick Delaunay
Signed-off-by: Patrice Chotard
---
drivers/i2c/stm32f7_i2c.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff -
This series is adding/updating several driver's feature:
- each I2C instance has its own private data
- add DT i2c-analog-filter property support
- implement digital filter setting
- add DT i2c-digital-filter-width-ns and i2c-digital-filter properties support
- i2cclk is computed only one
From: Patrick Delaunay
Compute i2cclk only one time in stm32_i2c_compute_timing()
and remove setup parameter (accessible in i2c_priv).
Signed-off-by: Patrick Delaunay
Signed-off-by: Patrice Chotard
---
drivers/i2c/stm32f7_i2c.c | 18 --
1 file changed, 8 insertions(+), 10 de
From: Patrick Delaunay
Add the support for the i2c-digital-filter binding, allowing to enable
the digital filter via the device-tree and indicate its value in the DT
Signed-off-by: Patrick Delaunay
Signed-off-by: Patrice Chotard
---
drivers/i2c/stm32f7_i2c.c | 11 +--
1 file changed,
From: Patrick Delaunay
The digital filter related computation are present in the driver
however the programming of the filter within the IP is missing.
The maximum value for the DNF is wrong and should be 15 instead of 16.
Signed-off-by: Patrick Delaunay
Signed-off-by: Patrice Chotard
---
dr
At the moment U-Boot produces an empty MAC address (02:00:00:00:00:00)
if the eMMC is not used by anything in U-Boot (e.g. with
CONFIG_ENV_IS_NOWHERE=y instead of having the environment on eMMC).
This happens because then there is nothing that actually initializes
the eMMC and reads the "cid" that
The logic in msm_generate_mac_addr() was originally taken from the LK
bootloader where the serial number is a string and must be parsed first.
However, in U-Boot msm_board_serial() returns an u32 and
msm_generate_mac_addr() has quite complicated code that will first
print it as a hex string and the
Enable SeaBIOS support for any kernel that requires legacy BIOS
services.
Signed-off-by: Bin Meng
---
configs/crownbay_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/crownbay_defconfig b/configs/crownbay_defconfig
index d7ee0fe45e..1923f89b9a 100644
--- a/configs/crownbay
Update SeaBIOS build instructions using exact command that involves
"make olddefconfig", and mention SeaBIOS release 1.14.0 has been
used for testing.
Signed-off-by: Bin Meng
---
doc/arch/x86.rst | 21 -
1 file changed, 8 insertions(+), 13 deletions(-)
diff --git a/doc/arch
This resyncs us with the version found in v5.13 of the Linux kernel with
the following exceptions:
- Keep our u-boot specific tests / code area.
- Change the location of checkpatch.rst (which we now import)
- Drop the "use strscpy" test as we don't have that, but do have strlcpy
and want that use
On 8/2/21 3:39 PM, Clément Léger wrote:
> sama5d2 support from DRAM will be modified to use device tree instead of
> hardcoded addresses. In order to prepare that, add the memory node to
> sama5d2.dtsi file since the boards supported by U-Boot with sama5d2 all
> contains 512Mb of DDR.
>
> Signed-o
On Tue, Aug 03, 2021 at 07:35:22AM +0800, Bin Meng wrote:
> Hi Tom,
>
> This PR includes the following x86 changes for v2021.10:
>
> - Fixed broken ICH SPI driver in software sequencer mode
> - Added "m25p,fast-read" to SPI flash node for x86 boards
> - Drop ROM_NEEDS_BLOBS and BUILD_ROM for x86
On Tue, Aug 3, 2021 at 1:12 PM Stephan Gerhold wrote:
>
> The logic in msm_generate_mac_addr() was originally taken from the LK
> bootloader where the serial number is a string and must be parsed first.
> However, in U-Boot msm_board_serial() returns an u32 and
> msm_generate_mac_addr() has quite
Hi Tom,
Thanks for the quick notes.
As I already mentioned, unfortunately, I did not notice any "warnings"
in time - we haven’t been building the bootloader recently, but our
customer is using it.
My only concern is the removal of support for the uCP1020 board. This
product is not dead and
On Tue, Aug 03, 2021 at 11:26:55AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This adds support for the IOT2050 Basic and Advanced devices. The Basic
> used the dual-core AM6528 GP processor, the Advanced one the AM6548 HS
> quad-core version.
>
> Both variants are booted via a Siemens-pro
On 03.08.21 15:27, Tom Rini wrote:
> On Tue, Aug 03, 2021 at 11:26:55AM +0200, Jan Kiszka wrote:
>
>> From: Jan Kiszka
>>
>> This adds support for the IOT2050 Basic and Advanced devices. The Basic
>> used the dual-core AM6528 GP processor, the Advanced one the AM6548 HS
>> quad-core version.
>>
>
On Tue, Aug 03, 2021 at 03:42:30PM +0200, Jan Kiszka wrote:
> On 03.08.21 15:27, Tom Rini wrote:
> > On Tue, Aug 03, 2021 at 11:26:55AM +0200, Jan Kiszka wrote:
> >
> >> From: Jan Kiszka
> >>
> >> This adds support for the IOT2050 Basic and Advanced devices. The Basic
> >> used the dual-core AM65
On 03.08.21 15:45, Tom Rini wrote:
> On Tue, Aug 03, 2021 at 03:42:30PM +0200, Jan Kiszka wrote:
>> On 03.08.21 15:27, Tom Rini wrote:
>>> On Tue, Aug 03, 2021 at 11:26:55AM +0200, Jan Kiszka wrote:
>>>
From: Jan Kiszka
This adds support for the IOT2050 Basic and Advanced devices. T
On 03.08.21 16:14, Jan Kiszka wrote:
> On 03.08.21 15:45, Tom Rini wrote:
>> On Tue, Aug 03, 2021 at 03:42:30PM +0200, Jan Kiszka wrote:
>>> On 03.08.21 15:27, Tom Rini wrote:
On Tue, Aug 03, 2021 at 11:26:55AM +0200, Jan Kiszka wrote:
> From: Jan Kiszka
>
> This adds support
On Tue, Aug 03, 2021 at 04:14:05PM +0200, Jan Kiszka wrote:
> On 03.08.21 15:45, Tom Rini wrote:
> > On Tue, Aug 03, 2021 at 03:42:30PM +0200, Jan Kiszka wrote:
> >> On 03.08.21 15:27, Tom Rini wrote:
> >>> On Tue, Aug 03, 2021 at 11:26:55AM +0200, Jan Kiszka wrote:
> >>>
> From: Jan Kiszka
>
This is the baseline support for the SIMATIC IOT2050 devices.
Changes in v7:
- rebased
- registered board doc with index
Changes in v6:
- rebased
- converted board README to docs/board/siemens/iot2050.rst
Changes in v5:
- rebased
- use DEFAULT_LINUX_BOOT_ENV from ti_armv7_common.h, rather
From: Jan Kiszka
This adds support for the IOT2050 Basic and Advanced devices. The Basic
used the dual-core AM6528 GP processor, the Advanced one the AM6548 HS
quad-core version.
Both variants are booted via a Siemens-provided FSBL that runs on the R5
cores. Consequently, U-Boot support is targe
From: Jan Kiszka
Add the DT entry for a watchdog based on RTI1. It requires additional
firmware on the MCU R5F cores to handle the expiry, e.g.
https://github.com/siemens/k3-rti-wdt. As this firmware will also lock
the power domain to protect it against premature shutdown, mark it
shared.
Aligns
From: Jan Kiszka
This allows to use the watchdog in custom scripts but does not enforce
that the OS has to support it as well.
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 16
configs/iot2050_defconfig| 6 ++
2 files cha
From: Jan Kiszka
To avoid the need of extra boot scripting on AM65x for loading a
watchdog firmware, add the required rproc init and loading logic for the
first R5F core to the watchdog start handler. In case the R5F cluster is
in lock-step mode, also initialize the second core. The firmware itse
From: Jan Kiszka
Prepares for the addition of the IOT2050 board which is based on the TI
AM65x. The board comes in two variants, Basic and Advanced, so there are
separate dts files. Furthermore, the SPL has its own device tree.
Based on original board support by Le Jin, Gao Nian and Chao Zeng.
This patch series fixes U-Boot crash during cancellation of x/y-modem
transfers and contains other various fixes related to finishing
transfers.
Pali Rohár (7):
xyz-modem: Fix crash after cancelling transfer
xyz-modem: Fix x-modem "xyzModem_eof error" at the end of file
xyz-modem: Put xyzMod
Variable xyz.len is set to -1 on error. At the end xyzModem_stream_read()
function calls memcpy() with length from variable xyz.len. If this variable
is set to -1 then value passed to memcpy is casted to unsigned value, which
means to copy whole address space. Which then cause U-Boot crash. E.g. on
Transfer termination tries to instruct sender that transfer was terminated.
Print error message and indicates aborted transfer in return value.
Signed-off-by: Pali Rohár
---
cmd/load.c | 14 +-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/cmd/load.c b/cmd/load.c
ind
This is how all other debug / diagnostic messages are handled.
Signed-off-by: Pali Rohár
---
common/xyzModem.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/common/xyzModem.c b/common/xyzModem.c
index 631c44e11adf..c200c9ff9177 100644
--- a/common/xyzModem.c
+++ b/commo
Show "## Start Addr" or "## Binary (...) download aborted" information like
in Kermit "loadb" command.
Signed-off-by: Pali Rohár
---
cmd/load.c | 16
1 file changed, 16 insertions(+)
diff --git a/cmd/load.c b/cmd/load.c
index 1ed05a9cd21e..573c44b912fd 100644
--- a/cmd/load.c
+
In x-modem protocol EOF is not an error state at the end of file.
Signed-off-by: Pali Rohár
---
common/xyzModem.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/common/xyzModem.c b/common/xyzModem.c
index b1b72aae0baf..631c44e11adf 100644
--- a/common/xyzModem.c
+++ b/common/xyzModem.c
@@
Obviously it is not possible to send terminate sequence over stream after
closing stream.
Signed-off-by: Pali Rohár
---
cmd/load.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cmd/load.c b/cmd/load.c
index b7894d7db02a..fb8c191fb64f 100644
--- a/cmd/load.c
+++ b/cmd/load.c
Currently it is possible to cancel loadx and loady commands by pressing
CTRL+X (CAN character) at least 3 times quickly.
All other U-Boot commands, including loadb and loads can be cancelled by
CTRL+C. So allow it also in xyz-modem code used by loadx and loady
commands. Implement it by handling CT
Hi,
Agenda today at [1]:
Marek - Should we compress U-Boot? (to save flash when you have plenty of RAM)
Marek - Could of-platdata be used in U-Boot proper
Ilias - Public keys in DT
Regards,
Simon
[1] https://bit.ly/3bFvwA1
or
https://docs.google.com/document/d/1YBOMsbM19uSFyoJWnt7-PsOLBaevzQUg
On Mon, Jul 26, 2021 at 07:37:53AM +, Z.Q. Hou wrote:
> Hi Micheal,
>
> Pasted the log below, the direct cause seems the u-boot DTB doesn't have
> /cpus node.
>
> => run bootcmd_mmc0
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> libfdt fdt_check_header(): FD
Having to use the -K option to mkimage to populate U-Boot's .dtb with the
public key while signing the kernel FIT image is often a little
awkward. In particular, when using a meta-build system such as
bitbake/Yocto, having the tasks of the kernel and U-Boot recipes
intertwined, modifying deployed a
Yes, this is the old discussion and triggered again now since we had a
discussion on the last U-Boot contributor call.
I will brief the main points here, as most of the details are
mentioned in previous threads.
Here are the couple of old and new implementations on the SPI-NOR side.
http://u-boo
Hi Ilias,
On Mon, 2 Aug 2021 at 23:46, Ilias Apalodimas
wrote:
>
> On Mon, Aug 02, 2021 at 01:22:18PM -0600, Simon Glass wrote:
> > Hi Heinrich,
> >
> > On Mon, 2 Aug 2021 at 11:35, Heinrich Schuchardt wrote:
> > >
> > >
> > >
> > > On 8/2/21 4:44 PM, Simon Glass wrote:
> > > > The changes to mo
HI Ilias,
On Mon, 2 Aug 2021 at 23:43, Ilias Apalodimas
wrote:
>
> On Mon, Aug 02, 2021 at 02:02:56PM -0600, Simon Glass wrote:
> > Hi Ilias,
> >
> > On Mon, 2 Aug 2021 at 09:37, Ilias Apalodimas
> > wrote:
> > >
> > > Hi Simon,
> > >
> > > On Mon, Aug 02, 2021 at 08:44:28AM -0600, Simon Glass w
On Tue, Aug 03, 2021 at 01:10:26PM +0900, Minkyu Kang wrote:
> Dear Tom,
>
> The following changes since commit b70b9b07463db2f6937c7ea6d7fb5122feb7ba1b:
>
> Prepare v2021.10-rc1 (2021-07-26 20:57:18 -0400)
>
> are available in the git repository at:
>
> g...@source.denx.de:u-boot/custodia
Hi Tom,
Please pull this PR.
Summary:
- SPI-NOR fix (Big Meng)
- XMC XM25QH64C flash (Reto Schneider)
CI:
https://source.denx.de/u-boot/custodians/u-boot-spi/-/pipelines/8565
thanks,
Jagan.
The following changes since commit 51aef405550e603ff702c034f0e2cd0f15bdf2bb:
Merge branch '2021-08-02
On Mon, Aug 02, 2021 at 05:27:59PM -0400, Tom Rini wrote:
> On Thu, Jul 29, 2021 at 09:22:02AM +0200, Jan Kiszka wrote:
>
> > From: Jan Kiszka
> >
> > This reverts commit 2359fa7a87848626bcbd3399e92c657595880cd7.
> >
> > While the goal is valid and there is surely unused memory in that area,
>
On Tue, Aug 03, 2021 at 09:54:20PM +0530, Jagan Teki wrote:
> Hi Tom,
>
> Please pull this PR.
>
> Summary:
> - SPI-NOR fix (Big Meng)
> - XMC XM25QH64C flash (Reto Schneider)
>
> CI:
> https://source.denx.de/u-boot/custodians/u-boot-spi/-/pipelines/8565
>
> thanks,
> Jagan.
>
> The following
Now that the spi-nor fix has been made in u-boot/master via:
commit 87e7219f9c6a ("mtd: spi-nor: Respect flash's hwcaps in
spi_nor_adjust_hwcaps()")
enable CONFIG_SPI_FLASH_SMART_HWCAPS on Intel Crown Bay again.
Signed-off-by: Bin Meng
---
configs/crownbay_defconfig | 1 -
1 file changed,
Dear Tom,
In message <20210802213100.GG9379@bill-the-cat> you wrote:
>
> I think that if nothing changes the banner not changing is the right
> behavior.
Hm... is it? How about "external" changes like building with a
different tool chain? Then at least the "version" command should
produce a cor
61 matches
Mail list logo