From: Jan Kiszka
Fix a logical inversion of the printed text.
Signed-off-by: Jan Kiszka
---
drivers/clk/clk-uclass.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/clk-uclass.c b/drivers/clk/clk-uclass.c
index ed6e60bc484..78d8ea94c65 100644
--- a/drivers/clk
On 21.02.24 10:10, Francesco Dolcini wrote:
> Hello Jan,
>
> On Mon, Feb 19, 2024 at 07:37:55PM +0100, Jan Kiszka wrote:
>> My personal observation is that continuous integration testings with
>> all-upstream components is not really a common thing. I saw that with
>>
On 19.02.24 19:37, Jan Kiszka wrote:
> On 17.02.24 12:36, Alexander Sverdlin wrote:
>> Hi Jan!
>>
>> On Sat, 2024-02-17 at 09:42 +0100, Jan Kiszka wrote:
>>>> U-Boot 2024.01 (Feb 15 2024 - 01:43:17 +0100)
>>>>
>>>> SoC: AM62X SR1.0 HS-FS
On 17.02.24 12:36, Alexander Sverdlin wrote:
> Hi Jan!
>
> On Sat, 2024-02-17 at 09:42 +0100, Jan Kiszka wrote:
>>> U-Boot 2024.01 (Feb 15 2024 - 01:43:17 +0100)
>>>
>>> SoC: AM62X SR1.0 HS-FS
>>> Model: Texas Instruments AM625 SK
>>> DRAM:
On 17.02.24 04:11, Alexander Sverdlin wrote:
> Hello Nishanth,
>
> On Fri, 2023-08-25 at 13:02 -0500, Nishanth Menon wrote:
>> Switch to using bootstd. Note with this change, we will stop using
>> distro_bootcmd and instead depend entirely on bootflow method of
>> starting the system up.
>>
>>
On 26.07.23 13:10, Nishanth Menon wrote:
> On 00:35-20230726, Francesco Dolcini wrote:
> [...]
At least the ones we have currently (I am not sure about toradex,
phytech etc), seem to operate the vdd_core at 0.85V .. (which is what
USB is dependent upon).
>>>
>>> For Toradex, we
From: Jan Kiszka
This restores support for IOT2050 by widely synchronizing its DT files
with the Linux kernel. We additionally need to add the alias restoration
that is still waiting for its upstream merge and the not-yet-upstreamed
bits needed for watchdog reboot detection.
Fixes: 4dbdc84754ea
On 06.01.24 12:57, Jan Kiszka wrote:
> On 29.12.23 18:46, Bryan Brattlof wrote:
>> Hello Again Everyone!
>>
>> This series gets the am65x booting again along with syncing the device
>> tree files with v6.7-rc1 Linux.
>>
>> The bulk of these patches unify
On 29.12.23 18:46, Bryan Brattlof wrote:
> Hello Again Everyone!
>
> This series gets the am65x booting again along with syncing the device
> tree files with v6.7-rc1 Linux.
>
> The bulk of these patches unify the WKUP SPL board file with the arm64
> files to make future syncs from Linux much
On 02.01.24 18:42, Tom Rini wrote:
> On Tue, Jan 02, 2024 at 08:27:34AM +0100, Jan Kiszka wrote:
>> On 27.12.23 13:39, Nishanth Menon wrote:
>>> On 15:00-20231221, Tom Rini wrote:
>>>> On Thu, Dec 21, 2023 at 11:43:46AM -0600, Bryan Brattlof wr
On 27.12.23 13:39, Nishanth Menon wrote:
> On 15:00-20231221, Tom Rini wrote:
>> On Thu, Dec 21, 2023 at 11:43:46AM -0600, Bryan Brattlof wrote:
>>
>>> Hello Everyone!
>>>
>>> This series gets the am65x booting again along with syncing the device
>>> tree files with v6.7-rc1 Linux.
>>>
>>> The
On 31.10.23 08:14, Stefan Roese wrote:
> On 10/30/23 17:20, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> We are not iterating CQSPI_REG_RETRY, we are waiting 'timeout' ms, since
>> day 1.
>>
>> Signed-off-by: Jan Kiszka
>
> Reviewed-by: Stefan Ro
From: Jan Kiszka
We are not iterating CQSPI_REG_RETRY, we are waiting 'timeout' ms, since
day 1.
Signed-off-by: Jan Kiszka
---
We are unfortunately seeing that message right now, rarely but then
prominently...
drivers/spi/cadence_qspi_apb.c | 3 +--
1 file changed, 1 insertion(+), 2
From: Jan Kiszka
This was lost in refactoring while some users of the IOT2050 expect it
to work: Make sure that up to 3 USB storage devices are probed.
Fixes: 53873974a4b0 ("include: armv7: Enable distroboot across all configs")
Signed-off-by: Jan Kiszka
Reviewed-by: Heinrich
From: Jan Kiszka
This was lost via 53873974a4b0 while some users of the IOT2050 expect it
to work: Make sure that up to 3 USB storage devices are probed.
Signed-off-by: Jan Kiszka
---
include/configs/iot2050.h | 9 +
1 file changed, 9 insertions(+)
diff --git a/include/configs
From: Jan Kiszka
The "simpler" the logic, the higher the probability to not test and get
things wrong, again: The absence of a "-PG2" suffix is not sufficient to
derive that we are on PG1. There is also "IOT2050-ADVANCED-M2".
Finally fix that by exactly matching ag
From: Jan Kiszka
This caused the wrong fdtfile to be set and was failing to apply M.2
settings.
Fixes: badaa1f6a7a9 ("boards: siemens: iot2050: Unify PG1 and PG2/M.2
configurations again")
Signed-off-by: Jan Kiszka
---
board/siemens/iot2050/board.c | 2 +-
1 file changed, 1 inser
From: Jan Kiszka
Since commit [1] A53 u-boot proper is broken. This is because nodes
marked as 'bootph-pre-ram' are not available at u-boot proper before
relocation.
To fix this we mark all nodes in u-boot.dtsi as 'bootph-all'.
[1] 9e644284ab812 ("dm: core: Report bootph-pre-ram/sram
On 04.10.23 14:15, Nishanth Menon wrote:
> On 22:26-20231003, Jan Kiszka wrote:
>> From: Jan Kiszka
>>
>> Since commit [1] A53 u-boot proper is broken. This is because nodes
>> marked as 'bootph-pre-ram' are not available at u-boot proper before
>> relocation.
&g
From: Jan Kiszka
Since commit [1] A53 u-boot proper is broken. This is because nodes
marked as 'bootph-pre-ram' are not available at u-boot proper before
relocation.
To fix this we mark all nodes as 'bootph-all'.
[1] 9e644284ab812 ("dm: core: Report bootph-pre-ram/sram node as pre-reloc
From: Jan Kiszka
We only have serial as console option, and leaving this on turns on
SYS_CONSOLE_IS_IN_ENV which is also not true for these devices, leaving
an ugly
In:No input devices available!
Out: No output devices available!
Err: No error devices available!
behind.
Signed-off
From: Jan Kiszka
When building in-tree, there is no source link.
Signed-off-by: Jan Kiszka
---
tools/iot2050-sign-fw.sh | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/tools/iot2050-sign-fw.sh b/tools/iot2050-sign-fw.sh
index 6b426c854c2..75ffd560823 100755
3-am6548-iot2050-advanced-m2-bkey-ekey-pcie-overlay.dtso
> diff --git a/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dts
> b/arch/arm/dts/k3-am6548-iot2050-advanced-m2-bkey-usb3-overlay.dtso
> similarity index 100%
> rename from arch/arm/dts/k3-am6548-iot2050-advanced-m2-bke
From: Jan Kiszka
At this point, system shutdown is not supported by the DM firmware that
TF-A calls. As we can't de-select only this feature, declare complete
PSCI reset support as non-functional so that we don't signal incomplete
support to the OS via EFI runtime services. This makes power-off
On 03.08.23 16:54, Andrew Davis wrote:
> All K3 boards now are secure by default, instead of setting this in each
> defconfig, make it implied by the ARCH config.
>
> The only exception is IOT2050, which I do not believe will have any
> problems with being a TI_SECURE_DEVICE, but for now turn it
From: Jan Kiszka
Only accept SPACE to stop autobooting. This is safer to avoid accidental
interruptions on unattended devices.
Signed-off-by: Jan Kiszka
---
configs/iot2050_defconfig | 4
1 file changed, 4 insertions(+)
diff --git a/configs/iot2050_defconfig b/configs/iot2050_defconfig
From: Jan Kiszka
This avoids having to maintain to defconfigs that are 99% equivalent.
The approach is to use binman to generate two flash images,
flash-pg1.bin and flash-pg2.bin. With the help of a template dtsi, we
can avoid duplicating the common binman image definitions.
Suggested
: Manorit Chawdhry
CC: Simon Glass
Jan Kiszka (5):
boards: siemens: iot2050: Fix boot configuration
iot2050: Use binman in signing script
boards: siemens: iot2050: Unify PG1 and PG2/M.2 configurations again
doc: board: siemens: iot2050: Update build env vars
configs: iot2050: Enabled keyed
From: Jan Kiszka
ATF is now called BL31, and OP-TEE since 3.21 suggests to use
tee-raw.bin instead of (the still identical) tee-pager_v2.bin.
Signed-off-by: Jan Kiszka
---
doc/board/siemens/iot2050.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/board/siemens
From: Jan Kiszka
The underlying issue was fixed in the meantime. Also signing the U-Boot
proper fit image now works. Just supporting custom cert templates
remains a todo.
Signed-off-by: Jan Kiszka
---
CC: Simon Glass
---
tools/iot2050-sign-fw.sh | 9 ++---
1 file changed, 2 insertions
From: Jan Kiszka
The common env bits now come via ti_armv7_common.env, include it.
Futhermore restore the board-specific boot targets and their ordering
that is now enforced k3-wide differently. Finally, enable
CONFIG_LEGACY_IMAGE_FORMAT explicitly which got lost while turning
FIT_SIGNATURE
On 26.07.23 09:25, Manorit Chawdhry wrote:
> On 12:17-20230726, Manorit Chawdhry wrote:
>> Hi Jan,
>>
>> On 08:42-20230726, Jan Kiszka wrote:
>>> On 14.07.23 07:52, Manorit Chawdhry wrote:
>>>> The series focuses on fixes for various boards along
On 14.07.23 07:52, Manorit Chawdhry wrote:
> The series focuses on fixes for various boards along with moving to
> standards and enabling the FIT_SIGNATURE for K3 Platforms towards the
> end.
>
> Dependencies:
> https://lore.kernel.org/u-boot/20230712183453.7623-1-n-fran...@ti.com/
>
>
On 18.07.23 18:20, Tom Rini wrote:
> We have a few places where defconfigs were added (or renamed) and not
> included in their previously listed MAINTAINERS entry, correct this.
>
> Signed-off-by: Tom Rini
> ---
> Cc: Adam Ford
> Cc: Chris Packham
> Cc: Jan Kiszka
&g
On 12.07.23 20:34, Neha Malcom Francis wrote:
> Move to using binman to generate tispl.bin which is used to generate the
> final flash.bin bootloader for iot2050 boards.
>
> Signed-off-by: Neha Malcom Francis
> Cc: Jan Kiszka
> Reviewed-by: Simon Glass
> ---
> arch
On 11.07.23 16:59, Simon Glass wrote:
> This series converts the mkimage entry type to be a section, i.e. based on
> the entry_Section class. This makes it more consistent in its behaviour,
> e.g. allowing symbol writing and expanded entries.
>
> A simple templating feature is also introduced, to
On 10.07.23 09:50, Neha Malcom Francis wrote:
> Hi Jan
>
> On 07/07/23 19:08, Jan Kiszka wrote:
>> On 07.07.23 14:34, Neha Malcom Francis wrote:
>>> Move to using binman to generate tispl.bin which is used to generate the
>>> final flash.bin bootloader for i
On 07.07.23 14:34, Neha Malcom Francis wrote:
> Added YAML configs for J721S2
>
> Signed-off-by: Neha Malcom Francis
> ---
> board/ti/j721s2/board-cfg.yaml | 37 +
> board/ti/j721s2/pm-cfg.yaml| 12 +
> board/ti/j721s2/rm-cfg.yaml| 2901
>
On 07.07.23 14:34, Neha Malcom Francis wrote:
> Added YAML configs for AM64xx
>
> Signed-off-by: Neha Malcom Francis
> ---
> board/ti/am64x/board-cfg.yaml | 37 +
> board/ti/am64x/pm-cfg.yaml| 12 +
> board/ti/am64x/rm-cfg.yaml| 1400 +
>
On 07.07.23 14:34, Neha Malcom Francis wrote:
> The ti-board-config entry loads and validates a given YAML config file
> against a given schema, and generates the board config binary. K3
> devices require these binaries to be packed into the final system
> firmware images.
>
> Signed-off-by: Neha
On 10.07.23 18:00, Simon Glass wrote:
> Hi Jan,
>
> On Sun, 9 Jul 2023 at 23:21, Jan Kiszka wrote:
>>
>> On 10.07.23 04:40, Simon Glass wrote:
>>> This series converts the mkimage entry type to be a section, i.e. based on
>>> the entry_Section clas
On 10.07.23 11:12, Neha Malcom Francis wrote:
> Hi Simon
>
> On 07/07/23 23:05, Simon Glass wrote:
>> Hi Neha,
>>
>> On Fri, 7 Jul 2023 at 13:36, Neha Malcom Francis
>> wrote:
>>>
>>> Support added for HS and GP boot binaries for AM64x.
>>>
>>> HS-SE:
>>> * tiboot3-am64x_sr2-hs-evm.bin
>>>
On 10.07.23 04:40, Simon Glass wrote:
> This series converts the mkimage entry type to be a section, i.e. based on
> the entry_Section class. This makes it more consistent in its behaviour,
> e.g. allowing symbol writing and expanded entries.
>
> A simple templating feature is also introduced, to
On 07.07.23 19:35, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 7 Jul 2023 at 17:03, Jan Kiszka wrote:
>>
>> On 07.07.23 17:35, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Fri, 7 Jul 2023 at 14:56, Jan Kiszka wrote:
>>>>
>>>> O
On 07.07.23 17:35, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 7 Jul 2023 at 14:56, Jan Kiszka wrote:
>>
>> On 07.07.23 14:42, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Fri, 7 Jul 2023 at 11:05, Jan Kiszka wrote:
>>>>
>>>> O
On 07.07.23 14:40, Simon Glass wrote:
> Allow a template to appear in the top level description when using
> multiple images.
>
> Signed-off-by: Simon Glass
> ---
>
> tools/binman/control.py | 5 ++--
> tools/binman/ftest.py| 12 ++
>
On 07.07.23 14:42, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 7 Jul 2023 at 11:05, Jan Kiszka wrote:
>>
>> On 05.07.23 00:14, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Mon, 3 Jul 2023 at 20:34, Jan Kiszka wrote:
>>>>
>>>> Hi
On 07.07.23 15:30, Jerome Forissier wrote:
>
>
> On 7/7/23 14:34, Neha Malcom Francis wrote:
>> Earlier documentation specified builds for generating bootloader images
>> using an external TI repository k3-image-gen and core-secdev-k3. Modify
>> this to using the binman flow so that user
On 07.07.23 14:34, Neha Malcom Francis wrote:
> Move to using binman to generate tispl.bin which is used to generate the
> final flash.bin bootloader for iot2050 boards.
>
> Signed-off-by: Neha Malcom Francis
> Cc: Jan Kiszka
> ---
> arch/arm/dts/k3-am65-iot2050
On 05.07.23 00:14, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 3 Jul 2023 at 20:34, Jan Kiszka wrote:
>>
>> Hi Simon,
>>
>> On 28.06.23 13:41, Simon Glass wrote:
>>> Collections can used to collect the contents of other entries into a
>>&
On 28.06.23 13:41, Simon Glass wrote:
> Sometimes multiple boards are built with binman and it is useful to
> specify a different FDT list for each. At present this is not possible
> without providing multiple values of the of-list entryarg (which is not
> supported in the U-Boot build system).
>
Hi Simon,
On 28.06.23 13:41, Simon Glass wrote:
> Collections can used to collect the contents of other entries into a
> single entry, but they result in a single entry, with the original entries
> 'left behind' in their old place.
>
> It is useful to be able to specific a set of entries ones
On 20.06.23 16:36, Simon Glass wrote:
> Hi Jan,
>
> On Tue, 20 Jun 2023 at 11:37, Jan Kiszka wrote:
>>
>> On 20.06.23 12:11, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Mon, 19 Jun 2023 at 16:09, Jan Kiszka wrote:
>>>>
>>>>
On 20.06.23 12:11, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 19 Jun 2023 at 16:09, Jan Kiszka wrote:
>>
>> On 19.06.23 16:09, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Mon, 19 Jun 2023 at 14:28, Jan Kiszka wrote:
>>>>
>>>>
On 19.06.23 16:09, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 19 Jun 2023 at 14:28, Jan Kiszka wrote:
>>
>> On 19.06.23 14:36, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Fri, 16 Jun 2023 at 16:42, Jan Kiszka wrote:
>>>>
>>>> O
On 19.06.23 14:36, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 16 Jun 2023 at 16:42, Jan Kiszka wrote:
>>
>> On 15.06.23 13:46, Jan Kiszka wrote:
>>> On 15.06.23 13:38, Simon Glass wrote:
>>>> Hi Jan,
>>>>
>>>> On Thu, 15 Jun 2023
On 15.06.23 13:46, Jan Kiszka wrote:
> On 15.06.23 13:38, Simon Glass wrote:
>> Hi Jan,
>>
>> On Thu, 15 Jun 2023 at 12:21, Jan Kiszka wrote:
>>>
>>> On 15.06.23 13:19, Simon Glass wrote:
>>>> Hi Jan,
>>>>
>>>> On Thu, 15
On 15.06.23 13:38, Simon Glass wrote:
> Hi Jan,
>
> On Thu, 15 Jun 2023 at 12:21, Jan Kiszka wrote:
>>
>> On 15.06.23 13:19, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Thu, 15 Jun 2023 at 12:09, Jan Kiszka wrote:
>>>>
>>>>
On 12.06.23 23:17, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 5 Jun 2023 at 15:40, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> This avoids having to maintain to defconfigs that are 99% equivalent.
>> The approach is to use binman to generate two flash ima
On 15.06.23 13:19, Simon Glass wrote:
> Hi Jan,
>
> On Thu, 15 Jun 2023 at 12:09, Jan Kiszka wrote:
>>
>> On 15.06.23 12:55, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Thu, 15 Jun 2023 at 11:26, Jan Kiszka wrote:
>>>>
>>>> O
On 15.06.23 12:55, Simon Glass wrote:
> Hi Jan,
>
> On Thu, 15 Jun 2023 at 11:26, Jan Kiszka wrote:
>>
>> On 12.06.23 23:17, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Mon, 5 Jun 2023 at 15:39, Jan Kiszka wrote:
>>>>
>>>>
On 12.06.23 23:17, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 5 Jun 2023 at 15:39, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> Introduce BINMAN_EXTRA_ARGS that can be set per board, e.g., to inject
>> specific settings. Will be used by IOT2050 first to de
On 07.06.23 04:19, yanhong wang wrote:
>
>
> On 2023/6/5 3:23, Jan Kiszka wrote:
>> On 25.05.23 11:36, Yanhong Wang wrote:
>>> Enabled ID_EEPROM and I2C configuration for StarFive VisionFive2 board.
>>>
>>> Signed-off-by: Yanhong Wang
>>> -
From: Jan Kiszka
This avoids having to maintain to defconfigs that are 99% equivalent.
The approach is to use binman to generate two flash images,
flash-pg1.bin and flash-pg2.bin. With the help of some macros, we can
avoid duplicating the common binman image definitions.
Suggested-by: Andrew
From: Jan Kiszka
The underlying issue was fixed in the meantime. Switching to fully
binman-based signing (script-free) remains a todo, though.
Signed-off-by: Jan Kiszka
---
CC: Simon Glass
---
tools/iot2050-sign-fw.sh | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git
it.
Jan
CC: Simon Glass
Jan Kiszka (3):
binman: Allow to define custom arguments
iot2050: Use binman in signing script
boards: siemens: iot2050: Unify PG1 and PG2/M.2 configurations again
Makefile | 1 +
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi
From: Jan Kiszka
Introduce BINMAN_EXTRA_ARGS that can be set per board, e.g., to inject
specific settings. Will be used by IOT2050 first to define multiple
of-lists.
Signed-off-by: Jan Kiszka
---
CC: Simon Glass
---
Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Makefile b
On 25.05.23 11:36, Yanhong Wang wrote:
> Enabled ID_EEPROM and I2C configuration for StarFive VisionFive2 board.
>
> Signed-off-by: Yanhong Wang
> ---
> configs/starfive_visionfive2_defconfig | 19 ++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git
On 25.05.23 11:36, Yanhong Wang wrote:
> Enable DWC_ETH_QOS and PHY_MOTORCOMM configuration to support ethernet
> function for StarFive VisionFive 2 board,including versions 1.2A and
> 1.3B.
>
> Signed-off-by: Yanhong Wang
> ---
> configs/starfive_visionfive2_defconfig | 13 +++--
> 1
On 05.05.23 00:50, Simon Glass wrote:
> The original function was only called once, before relocation. The new
> one is called again after relocation. This was not the intent of the
> original call. Fix this by renaming and updating the calling logic.
>
> With this, chromebook_link64 makes it
On 08.05.23 07:05, Neha Malcom Francis wrote:
> Hi Jan,
>
> On 07/05/23 17:41, Jan Kiszka wrote:
>> On 04.05.23 08:13, Neha Malcom Francis wrote:
>>> Hi Jan
>>>
>>> On 04/05/23 10:13, Neha Malcom Francis wrote:
>>>> Hi Jan,
>>>>
On 04.05.23 08:13, Neha Malcom Francis wrote:
> Hi Jan
>
> On 04/05/23 10:13, Neha Malcom Francis wrote:
>> Hi Jan,
>>
>> On 03/05/23 22:04, Jan Kiszka wrote:
>>> On 03.05.23 14:56, Neha Malcom Francis wrote:
>>>> Hi Jan,
>>>>
>
On 04.05.23 08:13, Neha Malcom Francis wrote:
> Hi Jan
>
> On 04/05/23 10:13, Neha Malcom Francis wrote:
>> Hi Jan,
>>
>> On 03/05/23 22:04, Jan Kiszka wrote:
>>> On 03.05.23 14:56, Neha Malcom Francis wrote:
>>>> Hi Jan,
>>>>
>
On 03.05.23 14:56, Neha Malcom Francis wrote:
> Hi Jan,
>
> On 03/05/23 12:57, Neha Malcom Francis wrote:
>> Hi Tom
>>
>> On 27/04/23 04:07, Tom Rini wrote:
>>> On Fri, Apr 21, 2023 at 06:01:44PM +0530, Neha Malcom Francis wrote:
>>>
This series aims to eliminate the use of additional custom
From: Jan Kiszka
Create *-u-boot.dtsi files for each target dtb of the IOT2050 series so
that we can drop the #include deviations from upstream dts[i] files
here.
Signed-off-by: Jan Kiszka
---
This was tested against most of our boards with the DTS synced from
kernel 6.3.
arch/arm/dts/k3
From: Jan Kiszka
importlib.resources became part of 3.7 only. Allow using distros with
3.6 and the importlib_resources backport.
Signed-off-by: Jan Kiszka
---
Tested on OpenSUSE 15.4 with importlib_resources 1.1.0.
tools/binman/control.py | 6 +-
tools/buildman/control.py | 6
On 02.03.23 00:38, Simon Glass wrote:
> Hi Jan,
>
> On Tue, 28 Feb 2023 at 11:20, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> Anything that is not boot-env related is better kept there by now.
>>
>> At this chance, also drop a stale comment f
On 02.03.23 00:38, Simon Glass wrote:
> Hi Jan,
>
> On Tue, 28 Feb 2023 at 11:23, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> The M.2 slots of the related IOT2050 variant need to be configured
>> according to the plugged cards. This tries to detect
On 01.03.23 19:34, Andrew Davis wrote:
> On 3/1/23 12:29 PM, Jan Kiszka wrote:
>> On 01.03.23 18:26, Andrew Davis wrote:
>>> On 2/28/23 12:19 PM, Jan Kiszka wrote:
>>>> From: Su Baocheng
>>>>
>>>> Due to different signature keys, the PG1 a
On 01.03.23 18:26, Andrew Davis wrote:
> On 2/28/23 12:19 PM, Jan Kiszka wrote:
>> From: Su Baocheng
>>
>> Due to different signature keys, the PG1 and the PG2 boards can no
>> longer use the same FSBL (tiboot3). This makes it impossible anyway to
>> maintaine a s
-off-by: chao zeng
[Jan: align DT to kernel, polish wording]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/Makefile | 3 +-
.../arm/dts/k3-am6548-iot2050-advanced-m2.dts | 121 ++
configs/iot2050_pg2_defconfig | 2 +-
doc/board/siemens/iot2050
From: Jan Kiszka
The M.2 slots of the related IOT2050 variant need to be configured
according to the plugged cards. This tries to detect the card using the
M.2 configuration pins of the B-key slot. If that fails, a U-Boot
environment variable can be set to configure manually. This variable
From: Jan Kiszka
This feature is desired on the platform.
Signed-off-by: Jan Kiszka
---
configs/iot2050_pg1_defconfig | 1 +
configs/iot2050_pg2_defconfig | 5 +
2 files changed, 2 insertions(+), 4 deletions(-)
diff --git a/configs/iot2050_pg1_defconfig b/configs/iot2050_pg1_defconfig
From: Jan Kiszka
This is enabled by default, thus should be described as well.
Signed-off-by: Jan Kiszka
---
doc/board/siemens/iot2050.rst | 4
1 file changed, 4 insertions(+)
diff --git a/doc/board/siemens/iot2050.rst b/doc/board/siemens/iot2050.rst
index cb49a0e36bf..efe94a448a9
From: Jan Kiszka
Use external blob otpcmd.bin to replace the 0xff filled OTP programming
command block to create a firmware image that provisions the OTP on
first boot. This otpcmd.bin is generated from the customer keys using
steps described in the meta-iot2050 integration layer for the device
From: Jan Kiszka
Allows to create a public key device tree dtsi for inclusion into U-Boot
SPL and proper during first build already. This can be achieved via
CONFIG_DEVICE_TREE_INCLUDES.
Signed-off-by: Jan Kiszka
---
tools/key2dtsi.py | 64 +++
1
From: Jan Kiszka
There are many ways to get a signed firmware for the IOT2050 devices,
namely for the parts under user-control. This script documents one way
of doing it, given a signing key. Augment the board documentation with
the required procedure around it.
Signed-off-by: Jan Kiszka
From: chao zeng
User-button is controlled by the mcu domain gpio number 25.
But main0 main1 mcu domain all have gpio number 25.
To identify where the gpio is from, Using gpio controll base as the prefix
to indicate the gpio resource.
Signed-off-by: chao zeng
---
board/siemens/iot2050/board.c
est master
- reworked patch 1 to be less invasive to the code
- added "iot2050: use the named gpio to control the user-button"
Jan
CC: chao zeng
CC: Su Baocheng
Jan Kiszka (11):
iot2050: Update firmware layout
iot2050: Migrate settings into board env file
iot2050: Add watch
From: Jan Kiszka
Will be needed when CONFIG_ENV_WRITEABLE_LIST is enabled. The listed
variables shall remain writable, for informational purposes - they have
to be considered untrusted because the persistent U-Boot env is not
protected.
Signed-off-by: Jan Kiszka
---
include/configs/iot2050.h
-add now required CONFIG_OF_LIST, update config matching]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 44
board/siemens/iot2050/board.c| 3 ++
configs/iot2050_pg1_defconfig| 1 +
configs/iot2050_pg2_defconfig
Baocheng
[Jan: refactor config option into targets, tweak some wordings]
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 80 ++-
board/siemens/iot2050/Kconfig | 28 ++-
board/siemens/iot2050/board.c | 12
From: Jan Kiszka
The latest version of the binary-only firmware parts come in a combined
form of FSBL and sysfw containers. This implies some layout changes to
the generated firmware image but also makes handling of artifacts much
simpler (4 files less). The env locations will not change, just
From: Jan Kiszka
Anything that is not boot-env related is better kept there by now.
At this chance, also drop a stale comment from iot2050.h
Signed-off-by: Jan Kiszka
---
board/siemens/iot2050/iot2050.env | 9 +
include/configs/iot2050.h | 11 ++-
2 files changed, 11
From: Jan Kiszka
Allows run-time control over watchdog auto-start and the timeout via
setting the environment variable watchdog_timeout_ms. A value of zero
means "do not start". Use CONFIG_WATCHDOG_TIMEOUT_MSECS as initial value
and this to zero by default. Users can then enable th
From: Jan Kiszka
Add hashes and configuration signature stubs to prepare verified boot
of main U-Boot by SPL.
Signed-off-by: Jan Kiszka
---
arch/arm/dts/k3-am65-iot2050-boot-image.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/dts/k3-am65-iot2050-boot
On 13.02.23 05:26, Simon Glass wrote:
> Hi Jan,
>
> On Tue, 7 Feb 2023 at 11:39, Simon Glass wrote:
>>
>> Hi Jan,
>>
>> On Tue, 7 Feb 2023 at 09:45, Jan Kiszka wrote:
>>>
>>> On 07.02.23 16:28, Simon Glass wrote:
>>>> H
On 07.02.23 16:28, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 6 Feb 2023 at 04:57, Jan Kiszka wrote:
>>
>> On 06.02.23 11:47, Jan Kiszka wrote:
>>> On 04.02.23 23:26, Simon Glass wrote:
>>>> Hi Jan,
>>>>
>>>> On Fri, 3 Feb 2023 at
On 07.02.23 05:02, Simon Glass wrote:
> Hi Jan,
>
> On Fri, 3 Feb 2023 at 05:23, Jan Kiszka wrote:
>>
>> From: Jan Kiszka
>>
>> This completes what 890feecaab72 started by selecting ENV_APPEND and
>> loading the default env before any other sources. This
On 07.02.23 05:02, Simon Glass wrote:
> Hi Jan,
>
> On Mon, 6 Feb 2023 at 03:42, Jan Kiszka wrote:
>>
>> On 04.02.23 23:23, Simon Glass wrote:
>>> Hi Jan,
>>>
>>> On Fri, 3 Feb 2023 at 23:35, Jan Kiszka wrote:
>>>>
>>>> O
1 - 100 of 705 matches
Mail list logo
