Hi Macpaul, Fabien,
I'm referring to patch series
https://patchwork.ozlabs.org/project/uboot/patch/20230804110448.24589-1-macpaul@mediatek.com/
where support for the mediatek mt8195 SOC is introduced into u-boot. We are
developing a board based on the mt8195 as well but we want to use UART1
>El 2023-12-08 17:06, Thomas Schaefer va escriure:
>> Hi Macpaul, Fabien,
>>
>> I'm referring to patch series
>> https://patc/
>> hwork.ozlabs.org%2Fproject%2Fuboot%2Fpatch%2F20230804110448.24589-1-ma
>> cpaul.lin%40mediatek.com%2F&
Hi all,
We are trying to enable FIELD RETURN on the NXP i.MX8MNano LPD4 EVK board.
We enabled Secure Boot in u-boot in the first step. After checking proper
execution of a signed bootloader image we closed the board blowing the
SEC_CONFIG fuse.
In the next step we created the board specific si
: Peng Fan (OSS) ; Thomas Schaefer
; 'u-boot@lists.denx.de'
Cc: Peng Fan
Betreff: RE: FIELD_RETURN on i.MX8MNANOLPD4 EVK
[You don't often get email from ye...@nxp.com. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
I think there is no particular SW s
: sba...@denx.de; u-boot@lists.denx.de; peng@nxp.com; uboot-...@nxp.com;
Thomas Schaefer
Betreff: Re: [PATCH] arm: imx: imx8m: Enable the SError exception
Hi Ye Li,
On Fri, Jan 12, 2024 at 4:07 AM Ye Li wrote:
>
> To work with commit 2f3c920(imx8m: workaround ROM serror), we need to
&g
Hi all,
We are trying to boot our i.MX8MNano UltraLite DDR3L EVK via USB using Serial
Download Mode. We are using u-boot v2022.04-rc3 with patches to support DDR3L
memory on this eval system.
ATF firmware used is built using imx_5.4.47_2.2.0 branch of imx-atf firmware.
In addition we are using
Hi Fabio,
>Hi Thomas,
>On Mon, May 30, 2022 at 9:01 AM Thomas Schaefer
>wrote:
>>
>> Hi all,
>>
>> We are trying to boot our i.MX8MNano UltraLite DDR3L EVK via USB using
>> Serial Download Mode. We are using u-boot v2022.04-rc3 with patches to
>
Hi York,
with commit 5605dc6135f6f26560ef3b0c6ebc5141c531179a you fix wr_lat bits of
timing_cfg_2 register for FSL ddr driver. Unfortunately this fix is wrong as
(wr_lat & 0x10) is already 5 bits. To make things clearer maybe it is better to
set wr_lat this way
diff --git a/drivers/ddr/fsl/ctr
Hi Stefan,
I have applied your set of 13 patches to fix ext4 into my 2016.07 u-boot tree.
Endianess fixes as provided by Michael Walle are also applied. I'm building for
a Freescale T1024RDB eval system.
When trying to write into a directory on MMC/SD card using ext4write, I get
error message
Hi Stefan,
applying patch [U-Boot,v4,06/13]ext4 and Michael Walles patch
[U-Boot,v4,3/4]ext4, I'm now able to write into directories on ext4 fs from
u-boot. However, when deleting a given file (i.e. when writing to an existing
filename), u-boot crashes when ext4 extents are enabled.
Some debug
> From: york sun [mailto:york@nxp.com]
> Sent: Samstag, 25. März 2017 16:35
> To: Thomas Schaefer; Tom Rini
> Cc: u-boot@lists.denx.de
> Re: Re: AW: [U-Boot] unused-const-variable warnings in FSL DDR driver
>
> Thomas,
>
> Can you put your patch together wit
Hi York,
When compiling latest u-boot with gcc 6.3 compiler, I get several
'unused-const-variable' warnings in options.c file of FSL DDR driver. Affected
variables are for (DIMM_SLOTS_PER_CTLR==2) configuration (e.g. dual_0S[4]) and
warnings could be fixed with the patch applied.
What do you t
Hi all,
When compiling latest u-boot with gcc 6.3 for a T1024RDB system, I get a
'unused-const-variable' warning in the FSL I2C driver. Affected variable is
fsl_i2c_speed_map.
I guess this warning can be fixed with the patch applied, but I'm not sure.
What do you think?
Best regards,
Thomas
> On 02/09/2017 02:32 AM, Thomas Schaefer wrote:
>> Hi York,
>>
>>
>>
>> When compiling latest u-boot with gcc 6.3 compiler, I get several
>> 'unused-const-variable' warnings in options.c file of FSL DDR driver.
>> Affected variables are for
>>
>>> On 02/09/2017 02:32 AM, Thomas Schaefer wrote:
>>>> Hi York,
>>>>
>>>>
>>>>
>>>> When compiling latest u-boot with gcc 6.3 compiler, I get several
>>>> 'unused-const-variable' warn
> On Thu, Feb 09, 2017 at 05:51:36PM +, york sun wrote:
>> On 02/09/2017 09:46 AM, Thomas Schaefer wrote:
>> >>>
>> >>>> On 02/09/2017 02:32 AM, Thomas Schaefer wrote:
>> >>>>> Hi York,
>> >>>>>
Vasut; u-boot@lists.denx.de; Simon Glass; Tom Rini; Heinrich
Schuchardt; Thomas Schaefer; Masahiro Yamada; Robert P . J . Day;
alexander.mer...@lauterbach.com; Joakim Tjernlund; Curt Brune; Valentin
Longchamp; Anatolij Gustschin; Ira W . Snyder; Kyle Moffett; Sebastien Carlier;
Stefan Roese
Hi Joe et. al.
After setting MAC address to invalid value 00:00:00:00:00:00 and resetting to a
valid one, u-boot will run into a recursive endless loop until no memory is
left to allocate a new MAC address:
=> print eth1addr
eth1addr=00:a0:a5:10:20:31
=> setenv eth1addr 00:00:00:00:00:00
=> set
Hi all,
I've built current u-boot (v2019.07-rc4) with QSPI support for our i.MX7D Sabre
eval system. I am using mx7dsabresd_qspi_defconfig.
The resulting u-boot fails to read from QSPI, i.e. the data read is not the
same than that written before with a previous (v2018) version.
After some inve
Hi Fabio,
> Hi Thomas,
>
> On Wed, Jun 19, 2019 at 10:04 AM Thomas Schaefer
> wrote:
> >
> > Hi all,
> >
> > I've built current u-boot (v2019.07-rc4) with QSPI support for our i.MX7D
> > Sabre eval system. I am using mx7dsabresd_qspi_defconfig.
Hi all,
> Hi Fabio,
>
> > Hi Thomas,
> >
> > On Wed, Jun 19, 2019 at 10:04 AM Thomas Schaefer
> > wrote:
> > >
> > > Hi all,
> > >
> > > I've built current u-boot (v2019.07-rc4) with QSPI support for our i.MX7D
> >
> On Mon, Jun 24, 2019 at 10:34 PM Fabio Estevam wrote:
> >
> > From: Thomas Schaefer
> >
> > During QSPI reads, current is_busy_controller function sporadically
> > fails with -ETIMEDOUT due to fixed number of 5 test loops. This
> > patch fixes this b
During QSPI reads, current is_controller_busy function sporadically
fails with -ETIMEDOUT due to fixed number of 5 test loops. Using
timer functions to wait 1000 us instead will fix this.
Signed-off-by: Thomas Schaefer
---
drivers/spi/fsl_qspi.c | 9 -
1 file changed, 4 insertions(+), 5
Use readl_poll_timeout instead of explicit calculation.
Signed-off-by: Thomas Schaefer
---
drivers/spi/fsl_qspi.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/spi/fsl_qspi.c b/drivers/spi/fsl_qspi.c
index 2c5937509f..41abe1996f 100644
--- a
Hi all,
The following patchset will fix QSPI flash read error discovered on i.MX7D
Sabre eval system. Could you please check and apply to upcoming v2019.07
release?
Best regards,
Thomas Schaefer
[PATCH 1/2] drivers/spi: fsl_qspi: fix read timeout
[PATCH 2/2] drivers/spi: fsl_qspi: improve
Use readl_poll_timeout instead of explicit calculation
Signed-off-by: Thomas Schaefer
---
drivers/spi/fsl_qspi.c | 17 ++---
1 file changed, 6 insertions(+), 11 deletions(-)
diff --git a/drivers/spi/fsl_qspi.c b/drivers/spi/fsl_qspi.c
index 2c5937509f..41abe1996f 100644
--- a
During QSPI reads, current is_controller_busy function sporadically
fails with -ETIMEDOUT due to fixed number of 5 test loops. Using
timer functions to wait 1000 us instead will fix this.
Signed-off-by: Thomas Schaefer
---
drivers/spi/fsl_qspi.c | 9 -
1 file changed, 4 insertions(+), 5
: Prabhakar Kushwaha
Gesendet: Mittwoch, 14. August 2019 08:53
An: Thomas Schaefer ; ja...@amarulasolutions.com;
feste...@gmail.com
Cc: tr...@konsulko.com; Thomas Schaefer ;
u-boot@lists.denx.de
Betreff: RE: [U-Boot] [PATCH 2/2] drivers/spi: fsl_qspi: fix controller busy
check
Dear Thomas
> Von: Jagan Teki
> Gesendet: Dienstag, 2. Juli 2019 13:12
>
> On Mon, Jul 1, 2019 at 9:07 PM Thomas Schaefer
> wrote:
> >
> > Use readl_poll_timeout instead of explicit calculation
> >
> > Signed-off-by: Thomas Schaefer
> > ---
> > driver
Mon Sep 17 00:00:00 2001
From: Thomas Schaefer
Date: Thu, 29 Aug 2019 11:36:53 +0200
Subject: [PATCH] dts: arm: fix USB controller 'size' parameter
With introduction of bind method in ehci-mx6 driver, usb device
sequence number is calculated using the base address and size
paramters
Hi Fabio,
> Hi Thomas,
>
> On Thu, Aug 29, 2019 at 10:40 AM Thomas Schaefer
> wrote:
>
> > arch/arm/dts/imx7d.dtsi | 2 +-
> > arch/arm/dts/imx7s.dtsi | 4 ++--
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/arm/d
Hi Marek,
I have ported u-boot v2019.07 to our i.MX7 base custom board. When testing, I
found that 'usb start' command results in board reset due to data abort
exception.
Our board has usbotg1, usbotg2 and usbh ports enabled. It works fine with older
u-boot versions.
I did some investigation
32 matches
Mail list logo
