All of lore.kernel.org
 help / color / mirror / Atom feed
* Anbernic RGXX3 devices with later mainline kernels don't boot
@ 2024-07-13  9:33 ` Daniel Martin
  0 siblings, 0 replies; 8+ messages in thread
From: Daniel Martin @ 2024-07-13  9:33 UTC (permalink / raw)
  To: linux-arm-kernel, linux-rockchip, heiko

Hi,

I'm just putting this out there to see if this is known or has been
tested recently.
I have 3 test Anbernic devices based on the RK3566 and all are failing
to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).

Devices tested: RG353P, RG503 & RG353V

Issues seen:

Mainline kernel & u-boot = no start or boots to embedded Android
Previous kernel (6.4.16) & mainline u-boot = as above
Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.

Working:

Previous mainline kernel 6.4.x & previously supplied u-boot.

Note: The mainline u-boot is written to the 32k offset.
          rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.

Sorry I don't have any UART output as I don't have an appropriate
screw head to get into these devices and try to wire one up.

Has testing been done recently on these devices as per above?

Kind Regards,

Daniel

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Anbernic RGXX3 devices with later mainline kernels don't boot
@ 2024-07-13  9:33 ` Daniel Martin
  0 siblings, 0 replies; 8+ messages in thread
From: Daniel Martin @ 2024-07-13  9:33 UTC (permalink / raw)
  To: linux-arm-kernel, linux-rockchip, heiko

Hi,

I'm just putting this out there to see if this is known or has been
tested recently.
I have 3 test Anbernic devices based on the RK3566 and all are failing
to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).

Devices tested: RG353P, RG503 & RG353V

Issues seen:

Mainline kernel & u-boot = no start or boots to embedded Android
Previous kernel (6.4.16) & mainline u-boot = as above
Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.

Working:

Previous mainline kernel 6.4.x & previously supplied u-boot.

Note: The mainline u-boot is written to the 32k offset.
          rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.

Sorry I don't have any UART output as I don't have an appropriate
screw head to get into these devices and try to wire one up.

Has testing been done recently on these devices as per above?

Kind Regards,

Daniel


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Anbernic RGXX3 devices with later mainline kernels don't boot
  2024-07-13  9:33 ` Daniel Martin
@ 2024-07-15 16:59   ` Chris Morgan
  -1 siblings, 0 replies; 8+ messages in thread
From: Chris Morgan @ 2024-07-15 16:59 UTC (permalink / raw)
  To: Daniel Martin; +Cc: linux-arm-kernel, linux-rockchip, heiko

On Sat, Jul 13, 2024 at 07:33:17PM +1000, Daniel Martin wrote:
> Hi,
> 
> I'm just putting this out there to see if this is known or has been
> tested recently.
> I have 3 test Anbernic devices based on the RK3566 and all are failing
> to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).
> 
> Devices tested: RG353P, RG503 & RG353V
> 
> Issues seen:
> 
> Mainline kernel & u-boot = no start or boots to embedded Android
> Previous kernel (6.4.16) & mainline u-boot = as above
> Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.
> 
> Working:
> 
> Previous mainline kernel 6.4.x & previously supplied u-boot.
> 
> Note: The mainline u-boot is written to the 32k offset.
>           rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.
> 
> Sorry I don't have any UART output as I don't have an appropriate
> screw head to get into these devices and try to wire one up.
> 
> Has testing been done recently on these devices as per above?
> 
> Kind Regards,
> 
> Daniel

What U-Boot commit are you using? See if this patch has been applied:

https://source.denx.de/u-boot/u-boot/-/commit/25e4aafd20589f8f8166a6d0dc565c39738b4ec1

I kind of broke it when I did some work trying to improve the
reliability of booting on emmc devices.

Thank you,
Chris

> 
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Anbernic RGXX3 devices with later mainline kernels don't boot
@ 2024-07-15 16:59   ` Chris Morgan
  0 siblings, 0 replies; 8+ messages in thread
From: Chris Morgan @ 2024-07-15 16:59 UTC (permalink / raw)
  To: Daniel Martin; +Cc: linux-arm-kernel, linux-rockchip, heiko

On Sat, Jul 13, 2024 at 07:33:17PM +1000, Daniel Martin wrote:
> Hi,
> 
> I'm just putting this out there to see if this is known or has been
> tested recently.
> I have 3 test Anbernic devices based on the RK3566 and all are failing
> to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).
> 
> Devices tested: RG353P, RG503 & RG353V
> 
> Issues seen:
> 
> Mainline kernel & u-boot = no start or boots to embedded Android
> Previous kernel (6.4.16) & mainline u-boot = as above
> Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.
> 
> Working:
> 
> Previous mainline kernel 6.4.x & previously supplied u-boot.
> 
> Note: The mainline u-boot is written to the 32k offset.
>           rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.
> 
> Sorry I don't have any UART output as I don't have an appropriate
> screw head to get into these devices and try to wire one up.
> 
> Has testing been done recently on these devices as per above?
> 
> Kind Regards,
> 
> Daniel

What U-Boot commit are you using? See if this patch has been applied:

https://source.denx.de/u-boot/u-boot/-/commit/25e4aafd20589f8f8166a6d0dc565c39738b4ec1

I kind of broke it when I did some work trying to improve the
reliability of booting on emmc devices.

Thank you,
Chris

> 
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Anbernic RGXX3 devices with later mainline kernels don't boot
  2024-07-15 16:59   ` Chris Morgan
@ 2024-07-18  8:35     ` Daniel Martin
  -1 siblings, 0 replies; 8+ messages in thread
From: Daniel Martin @ 2024-07-18  8:35 UTC (permalink / raw)
  To: Chris Morgan; +Cc: linux-arm-kernel, linux-rockchip, heiko

Thanks Chris, no this hasn't been applied.
I will try it out & report back

On Tue, 16 Jul 2024 at 02:59, Chris Morgan <macroalpha82@gmail.com> wrote:
>
> On Sat, Jul 13, 2024 at 07:33:17PM +1000, Daniel Martin wrote:
> > Hi,
> >
> > I'm just putting this out there to see if this is known or has been
> > tested recently.
> > I have 3 test Anbernic devices based on the RK3566 and all are failing
> > to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).
> >
> > Devices tested: RG353P, RG503 & RG353V
> >
> > Issues seen:
> >
> > Mainline kernel & u-boot = no start or boots to embedded Android
> > Previous kernel (6.4.16) & mainline u-boot = as above
> > Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.
> >
> > Working:
> >
> > Previous mainline kernel 6.4.x & previously supplied u-boot.
> >
> > Note: The mainline u-boot is written to the 32k offset.
> >           rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.
> >
> > Sorry I don't have any UART output as I don't have an appropriate
> > screw head to get into these devices and try to wire one up.
> >
> > Has testing been done recently on these devices as per above?
> >
> > Kind Regards,
> >
> > Daniel
>
> What U-Boot commit are you using? See if this patch has been applied:
>
> https://source.denx.de/u-boot/u-boot/-/commit/25e4aafd20589f8f8166a6d0dc565c39738b4ec1
>
> I kind of broke it when I did some work trying to improve the
> reliability of booting on emmc devices.
>
> Thank you,
> Chris
>
> >
> > _______________________________________________
> > Linux-rockchip mailing list
> > Linux-rockchip@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-rockchip



-- 

Kind Regards,

Daniel

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Anbernic RGXX3 devices with later mainline kernels don't boot
@ 2024-07-18  8:35     ` Daniel Martin
  0 siblings, 0 replies; 8+ messages in thread
From: Daniel Martin @ 2024-07-18  8:35 UTC (permalink / raw)
  To: Chris Morgan; +Cc: linux-arm-kernel, linux-rockchip, heiko

Thanks Chris, no this hasn't been applied.
I will try it out & report back

On Tue, 16 Jul 2024 at 02:59, Chris Morgan <macroalpha82@gmail.com> wrote:
>
> On Sat, Jul 13, 2024 at 07:33:17PM +1000, Daniel Martin wrote:
> > Hi,
> >
> > I'm just putting this out there to see if this is known or has been
> > tested recently.
> > I have 3 test Anbernic devices based on the RK3566 and all are failing
> > to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).
> >
> > Devices tested: RG353P, RG503 & RG353V
> >
> > Issues seen:
> >
> > Mainline kernel & u-boot = no start or boots to embedded Android
> > Previous kernel (6.4.16) & mainline u-boot = as above
> > Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.
> >
> > Working:
> >
> > Previous mainline kernel 6.4.x & previously supplied u-boot.
> >
> > Note: The mainline u-boot is written to the 32k offset.
> >           rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.
> >
> > Sorry I don't have any UART output as I don't have an appropriate
> > screw head to get into these devices and try to wire one up.
> >
> > Has testing been done recently on these devices as per above?
> >
> > Kind Regards,
> >
> > Daniel
>
> What U-Boot commit are you using? See if this patch has been applied:
>
> https://source.denx.de/u-boot/u-boot/-/commit/25e4aafd20589f8f8166a6d0dc565c39738b4ec1
>
> I kind of broke it when I did some work trying to improve the
> reliability of booting on emmc devices.
>
> Thank you,
> Chris
>
> >
> > _______________________________________________
> > Linux-rockchip mailing list
> > Linux-rockchip@lists.infradead.org
> > http://lists.infradead.org/mailman/listinfo/linux-rockchip



-- 

Kind Regards,

Daniel


^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Anbernic RGXX3 devices with later mainline kernels don't boot
  2024-07-18  8:35     ` Daniel Martin
@ 2024-07-18  9:12       ` Daniel Martin
  -1 siblings, 0 replies; 8+ messages in thread
From: Daniel Martin @ 2024-07-18  9:12 UTC (permalink / raw)
  To: Chris Morgan; +Cc: linux-arm-kernel, linux-rockchip, heiko

Unfortunately this patch doesn't fix it.
I'm using u-boot 2024.07 as a base.

On Thu, 18 Jul 2024 at 18:35, Daniel Martin <dmanlfc@gmail.com> wrote:
>
> Thanks Chris, no this hasn't been applied.
> I will try it out & report back
>
> On Tue, 16 Jul 2024 at 02:59, Chris Morgan <macroalpha82@gmail.com> wrote:
> >
> > On Sat, Jul 13, 2024 at 07:33:17PM +1000, Daniel Martin wrote:
> > > Hi,
> > >
> > > I'm just putting this out there to see if this is known or has been
> > > tested recently.
> > > I have 3 test Anbernic devices based on the RK3566 and all are failing
> > > to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).
> > >
> > > Devices tested: RG353P, RG503 & RG353V
> > >
> > > Issues seen:
> > >
> > > Mainline kernel & u-boot = no start or boots to embedded Android
> > > Previous kernel (6.4.16) & mainline u-boot = as above
> > > Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.
> > >
> > > Working:
> > >
> > > Previous mainline kernel 6.4.x & previously supplied u-boot.
> > >
> > > Note: The mainline u-boot is written to the 32k offset.
> > >           rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.
> > >
> > > Sorry I don't have any UART output as I don't have an appropriate
> > > screw head to get into these devices and try to wire one up.
> > >
> > > Has testing been done recently on these devices as per above?
> > >
> > > Kind Regards,
> > >
> > > Daniel
> >
> > What U-Boot commit are you using? See if this patch has been applied:
> >
> > https://source.denx.de/u-boot/u-boot/-/commit/25e4aafd20589f8f8166a6d0dc565c39738b4ec1
> >
> > I kind of broke it when I did some work trying to improve the
> > reliability of booting on emmc devices.
> >
> > Thank you,
> > Chris
> >
> > >
> > > _______________________________________________
> > > Linux-rockchip mailing list
> > > Linux-rockchip@lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
>
>
> --
>
> Kind Regards,
>
> Daniel



-- 

Kind Regards,

Daniel

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Anbernic RGXX3 devices with later mainline kernels don't boot
@ 2024-07-18  9:12       ` Daniel Martin
  0 siblings, 0 replies; 8+ messages in thread
From: Daniel Martin @ 2024-07-18  9:12 UTC (permalink / raw)
  To: Chris Morgan; +Cc: linux-arm-kernel, linux-rockchip, heiko

Unfortunately this patch doesn't fix it.
I'm using u-boot 2024.07 as a base.

On Thu, 18 Jul 2024 at 18:35, Daniel Martin <dmanlfc@gmail.com> wrote:
>
> Thanks Chris, no this hasn't been applied.
> I will try it out & report back
>
> On Tue, 16 Jul 2024 at 02:59, Chris Morgan <macroalpha82@gmail.com> wrote:
> >
> > On Sat, Jul 13, 2024 at 07:33:17PM +1000, Daniel Martin wrote:
> > > Hi,
> > >
> > > I'm just putting this out there to see if this is known or has been
> > > tested recently.
> > > I have 3 test Anbernic devices based on the RK3566 and all are failing
> > > to start if I use the mainline U-Boot (2024.07) & Kernel (6.9.8).
> > >
> > > Devices tested: RG353P, RG503 & RG353V
> > >
> > > Issues seen:
> > >
> > > Mainline kernel & u-boot = no start or boots to embedded Android
> > > Previous kernel (6.4.16) & mainline u-boot = as above
> > > Mainline kernel (6.6 or 6.9) & supplied u-boot = failing to start kernel.
> > >
> > > Working:
> > >
> > > Previous mainline kernel 6.4.x & previously supplied u-boot.
> > >
> > > Note: The mainline u-boot is written to the 32k offset.
> > >           rk3566_ddr_1056MHz_v1.21.bin & rk3568_bl31_v1.44.elf used for u-boot.
> > >
> > > Sorry I don't have any UART output as I don't have an appropriate
> > > screw head to get into these devices and try to wire one up.
> > >
> > > Has testing been done recently on these devices as per above?
> > >
> > > Kind Regards,
> > >
> > > Daniel
> >
> > What U-Boot commit are you using? See if this patch has been applied:
> >
> > https://source.denx.de/u-boot/u-boot/-/commit/25e4aafd20589f8f8166a6d0dc565c39738b4ec1
> >
> > I kind of broke it when I did some work trying to improve the
> > reliability of booting on emmc devices.
> >
> > Thank you,
> > Chris
> >
> > >
> > > _______________________________________________
> > > Linux-rockchip mailing list
> > > Linux-rockchip@lists.infradead.org
> > > http://lists.infradead.org/mailman/listinfo/linux-rockchip
>
>
>
> --
>
> Kind Regards,
>
> Daniel



-- 

Kind Regards,

Daniel


^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2024-07-18  9:13 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-07-13  9:33 Anbernic RGXX3 devices with later mainline kernels don't boot Daniel Martin
2024-07-13  9:33 ` Daniel Martin
2024-07-15 16:59 ` Chris Morgan
2024-07-15 16:59   ` Chris Morgan
2024-07-18  8:35   ` Daniel Martin
2024-07-18  8:35     ` Daniel Martin
2024-07-18  9:12     ` Daniel Martin
2024-07-18  9:12       ` Daniel Martin

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.