Hi,
As described in the subject. We have an x86 image with U-boot as a EFI
Payload.
It crashes the VM in VMware (Player 16) with a x86 triple fault.
I have tried with a clean U-boot build with efi-x86_payload64_defconfig.
I can see in the VM it prints U-boot EFI Payload and then throws the
triple
On Thu, May 12, 2022 at 08:41:15PM +0200, Pali Rohár wrote:
> On Thursday 12 May 2022 20:02:33 Sean Nyekjaer wrote:
> > On Thu, May 12, 2022 at 12:24:01PM +0200, Pali Rohár wrote:
> > > On Thursday 12 May 2022 12:19:01 Pali Rohár wrote:
> > > > On Monday 09 May 202
From: Sean Nyekjaer
When compling for x86:
ld.bfd: fs/squashfs/sqfs.o: in function `sqfs_read':
u-boot/fs/squashfs/sqfs.c:1443: undefined reference to `__udivmoddi4'
ld.bfd: u-boot/fs/squashfs/sqfs.c:1521: undefined reference to `__udivmoddi4'
Signed-off-by: Sean Nyekjaer
Revi
> >
> > > > On Thu, May 05, 2022 at 11:26:37AM +0200, Sean Nyekjaer wrote:
> > > >
> > > > > From: Sean Nyekjaer
> > > > >
> > > > > When compling for x86:
> > > > > ld.bfd: fs/squashfs/sqfs.o: in function
From: Sean Nyekjaer
When compling for x86:
ld.bfd: fs/squashfs/sqfs.o: in function `sqfs_read':
u-boot/fs/squashfs/sqfs.c:1443: undefined reference to `__udivmoddi4'
ld.bfd: u-boot/fs/squashfs/sqfs.c:1521: undefined reference to `__udivmoddi4'
Signed-off-by: Sean Nyekjaer
-
Hi,
I'm trying to build Squashfs for u-boot for x86.
Looks like we are missing some libgcc helper function.
ld.bfd: fs/squashfs/sqfs.o: in function `sqfs_read':
/home/sean/development/siemens/u-boot/fs/squashfs/sqfs.c:1443: undefined
reference to `__udivmoddi4'
ld.bfd: /home/sean/development/si
legacy bch geometry
> Fixes: 616f03daba mtd: gpmi: change the BCH layout setting for large oob NAND
> Tested-by: Tim Harvey
Tested-by: Sean Nyekjaer
> Signed-off-by: Han Xu
>
> Changes in v2:
> -- change the commit log about backward compatible issue is in u-boot
> -- removed th
Hi Han,
On Mon, Mar 21, 2022 at 03:18:34PM -0500, Han Xu wrote:
> The code change fixed the kernel gpmi bch setting not aligned with
> u-boot settings issue. It still uses the legacy bch geometry as the
AFAIK there is no merged changes in the kernel regarding this.
The breaking change was done in
Hi Frieder,
On Thu, Mar 17, 2022 at 01:59:07PM +0100, Frieder Schrempf wrote:
> Am 17.03.22 um 09:06 schrieb Frieder Schrempf:
> > Hi Tim,
> >
> > Am 16.03.22 um 17:34 schrieb Tim Harvey:
> >> On Wed, Mar 16, 2022 at 7:09 AM Fabio Estevam wrote:
> >>>
> >>> Adding Han Xu's NXP email on Cc.
> >>>
On 13/05/2021 22.02, han.xu wrote:
> On 21/05/11 07:08AM, Sean Nyekjaer wrote:
>> Caution: EXT Email
>>
>> On 11/05/2021 04.49, han.xu wrote:
>>> On 21/05/10 12:00PM, Sean Nyekjaer wrote:
>>>> Caution: EXT Email
>>>>
>>>> Li
On 11/05/2021 04.49, han.xu wrote:
> On 21/05/10 12:00PM, Sean Nyekjaer wrote:
>> Caution: EXT Email
>>
>> Linux kernel defaults to use legacy bch setting, this was creating a
>> mismatch between U-boot and Linux default settings.
> Kernel uses the NAND chip spec
Linux kernel defaults to use legacy bch setting, this was creating a
mismatch between U-boot and Linux default settings.
Fixes: 51cdf83eea ("mtd: gpmi: provide the option to use legacy bch geometry")
Signed-off-by: Sean Nyekjaer
---
drivers/mtd/nand/raw/mxs_nand.c| 2 +-
driver
On 19/04/2021 09.32, Miquel Raynal wrote:
Hi Sean,
+ u-boot ML
Sean Nyekjaer wrote on Wed, 14 Apr 2021 15:13:39
+0200:
Hi,
I have two boards with a iMX6ULL SoC one attached to a Micron NAND flash
(MT29F4G08ABAFAWP) and one a Toshiba (TC58BVG2S0HTAI0).
After updating the boards from u
, it resets the bootcount variable for the booted
slot using "fw_setenv":
fw_setenv bootcount_a 3
When the non-booted slot is updated, the order is updated by setting the
bootslots variable with "fw_setenv":
fw_setenv bootslots=b a
Signed-off-by: Martin Hundebøll
Tested-by: Se
On 28.01.2019 11.13, Patrick Delaunay wrote:
Update generation of spl binaries
- continue to generate all SPL files in spl sub-directory
- copy in root folder the needed file for user (YOCTO, buildroot):
u-boot-spl.stm32
Signed-off-by: Patrick Delaunay
---
Hi,
This patch update http://pat
Hi Patrick
I checked with Patrice the other boards and most of the cases the modified spl
binay
(u-boot-spl.bin/ u-boot-spl.ais / u-boot-spl.img / u-boot-spl.pbl /
u-boot-spl.gph)
are generated in spl directory.
So I done the same for u-boot-spl.stm32.
All the NXP iMX6 variant boards deploy
Watchdog is not handled while waiting for fastboot commands.
Tested on a i.MX6 ULL EVK board.
Signed-off-by: Sean Nyekjaer
---
cmd/fastboot.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/cmd/fastboot.c b/cmd/fastboot.c
index e6ae0570d5..f520d907ff 100644
--- a/cmd/fastboot.c
+++ b/cmd
Hi Patrice
What about keeping spl binary in /spl directory and copying it in root
directory instead ? It would avoid us to update our environment
regarding your proposal.
You didn't answer to the above question.
Patrice
Sorry.
I really don't care how it's done :-)
But the I think the best
wrote:
Deploy u-boot-spl.stm32 binary in u-boot root folder like
the rest of the boards.
This makes it more streamlined when building in Yocto, Buildroot etc..
Signed-off-by: Sean Nyekjaer
---
arch/arm/mach-stm32mp/config.mk | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a
This enables us to detect if the i.MX6 SoC
is booting from USB.
Signed-off-by: Sean Nyekjaer
---
arch/arm/include/asm/arch-mx6/imx-regs.h | 7 +++
1 file changed, 7 insertions(+)
diff --git a/arch/arm/include/asm/arch-mx6/imx-regs.h
b/arch/arm/include/asm/arch-mx6/imx-regs.h
index
Add entry for Spansion s25fl208k part.
Signed-off-by: Sean Nyekjaer
---
drivers/mtd/spi/spi_flash_ids.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/spi/spi_flash_ids.c b/drivers/mtd/spi/spi_flash_ids.c
index b789219e4e..8d07d7ad7f 100644
--- a/drivers/mtd/spi/spi_flash_ids.c
e tried to make the accepted format the same as the one the
mkenvimage tool accepts. I have no idea how portable the sed script
implementing the "allow embedded newlines in values" is. Nor do I know
if one can expect xxd to be available.
Signed-off-by: Rasmus Villemoes
Tested-by: Sean
This spi-nor is 4Mbit/512KB
Fixes: b4fbcbc5a5 ("mtd/spi: add support for is25lq040b")
Signed-off-by: Sean Nyekjaer
---
drivers/mtd/spi/spi_flash_ids.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/spi/spi_flash_ids.c b/drivers/mtd/spi/spi_flash_i
Check if we are booting from NAND and let the bootrom
continue to load the rest of the bootloader
Signed-off-by: Sean Nyekjaer
---
arch/arm/mach-mvebu/include/mach/soc.h | 1 +
arch/arm/mach-mvebu/spl.c | 16 ++--
2 files changed, 15 insertions(+), 2 deletions(-)
diff
It's the first 8 bits of the bootrom error register that
contains the boot error/fallback error code. Lets check that
and continue to boot from UART.
Signed-off-by: Sean Nyekjaer
---
arch/arm/mach-mvebu/include/mach/soc.h | 6 ++
arch/arm/mach-mvebu/spl.c | 9 +
2
Signed-off-by: Sean Nyekjaer
---
arch/arm/dts/armada-38x.dtsi | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/arch/arm/dts/armada-38x.dtsi b/arch/arm/dts/armada-38x.dtsi
index dc8a1a66c1..5e5a158551 100644
--- a/arch/arm/dts/armada-38x.dtsi
+++ b/arch/arm/dts
bbt_mirror_descr and bbt_main_descr is defined but not used
when compiling without CONFIG_SYS_NAND_USE_FLASH_BBT set.
Signed-off-by: Sean Nyekjaer
---
drivers/mtd/nand/pxa3xx_nand.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mtd/nand/pxa3xx_nand.c b/drivers/mtd/nand
Signed-off-by: Sean Nyekjaer
---
v1:
1: removed SECT_4K as the chip are supporting 32K and bulk erase
drivers/mtd/spi/spi_flash_ids.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/spi/spi_flash_ids.c b/drivers/mtd/spi/spi_flash_ids.c
index 13f64e773f..32c6123a03 100644
--- a
Signed-off-by: Sean Nyekjaer
---
drivers/mtd/spi/spi_flash_ids.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mtd/spi/spi_flash_ids.c b/drivers/mtd/spi/spi_flash_ids.c
index 13f64e773f..2cb0196065 100644
--- a/drivers/mtd/spi/spi_flash_ids.c
+++ b/drivers/mtd/spi/spi_flash_ids.c
Signed-off-by: Sean Nyekjaer
---
- I have just noticed that the RTC driver for this device have been merged,
should the watchdog part be included in the rtc driver or standalone?
- The hw_watchdog_reset is called far too often the device here is on i2c,
with what i have done the reset is
30 matches
Mail list logo
