Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
On Tue, Jul 12, 2016 at 12:54 AM, Andreas Färberwrote: > Am 12.07.2016 um 00:52 schrieb Carlo Caione: >> On Mon, Jul 11, 2016 at 11:38 PM, Andreas Färber wrote: >>> Am 11.07.2016 um 22:36 schrieb Carlo Caione: On Mon, Jul 11, 2016 at 10:15 PM, Andreas Färber wrote: >> >> [...] >> > > DRAM: 2 GiB > No maUsing default environment > > In:serial@4c0 > Out: serial@4c0 > Err: serial@4c0 > Net: No ethernet found. > => > > The eth_designware line (twice, if counting "No ma") is due to what Tom > mentioned wrt DM GPIO, I guess. > > Shouldn't we get a version line from SPL, too? A serial driver issue? AFAIKT there is no SPL. U-Boot is loaded by BL3-1 also in the U-Boot shipped by amlogic. >>> >>> You're right, Hardkernel's version is without SPL, too. >>> >>> Still I wonder about that "No ma" (after the DRAM line). >> >> drivers/core/lists.c: dm_warn("No match for driver >> '%s'\n", entry->name); >> >> :) > > How does that explain the incomplete "No ma"? The only thing I can think of is a shitty queueing by the UART driver / hardware. -- Carlo Caione ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
Am 12.07.2016 um 00:52 schrieb Carlo Caione: > On Mon, Jul 11, 2016 at 11:38 PM, Andreas Färberwrote: >> Am 11.07.2016 um 22:36 schrieb Carlo Caione: >>> On Mon, Jul 11, 2016 at 10:15 PM, Andreas Färber wrote: > > [...] > DRAM: 2 GiB No maUsing default environment In:serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: No ethernet found. => The eth_designware line (twice, if counting "No ma") is due to what Tom mentioned wrt DM GPIO, I guess. Shouldn't we get a version line from SPL, too? A serial driver issue? >>> >>> AFAIKT there is no SPL. U-Boot is loaded by BL3-1 also in the U-Boot >>> shipped by amlogic. >> >> You're right, Hardkernel's version is without SPL, too. >> >> Still I wonder about that "No ma" (after the DRAM line). > > drivers/core/lists.c: dm_warn("No match for driver > '%s'\n", entry->name); > > :) How does that explain the incomplete "No ma"? Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
On Mon, Jul 11, 2016 at 11:38 PM, Andreas Färberwrote: > Am 11.07.2016 um 22:36 schrieb Carlo Caione: >> On Mon, Jul 11, 2016 at 10:15 PM, Andreas Färber wrote: [...] >>> >>> DRAM: 2 GiB >>> No maUsing default environment >>> >>> In:serial@4c0 >>> Out: serial@4c0 >>> Err: serial@4c0 >>> Net: No ethernet found. >>> => >>> >>> The eth_designware line (twice, if counting "No ma") is due to what Tom >>> mentioned wrt DM GPIO, I guess. >>> >>> Shouldn't we get a version line from SPL, too? A serial driver issue? >> >> AFAIKT there is no SPL. U-Boot is loaded by BL3-1 also in the U-Boot >> shipped by amlogic. > > You're right, Hardkernel's version is without SPL, too. > > Still I wonder about that "No ma" (after the DRAM line). drivers/core/lists.c: dm_warn("No match for driver '%s'\n", entry->name); :) -- Carlo Caione ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
Am 11.07.2016 um 22:36 schrieb Carlo Caione: > On Mon, Jul 11, 2016 at 10:15 PM, Andreas Färberwrote: >> [...] >> NOTICE: BL3-1: v1.0(debug):4d2e34d >> NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 >> INFO:BL3-1: Initializing runtime services >> INFO:BL3-1: Preparing for EL3 exit to normal world >> INFO:BL3-1: Next image address = 0x100 >> INFO:BL3-1: Next image spsr = 0x3c9 >> No match for driver 'eth_designware' >> Some drivers were not found >> >> >> U-Boot 2016.07-1-g10a9e48 (Jul 11 2016 - 21:58:13 +0200) odroid-c2 >> >> DRAM: 2 GiB >> No maUsing default environment >> >> In:serial@4c0 >> Out: serial@4c0 >> Err: serial@4c0 >> Net: No ethernet found. >> => >> >> The eth_designware line (twice, if counting "No ma") is due to what Tom >> mentioned wrt DM GPIO, I guess. >> >> Shouldn't we get a version line from SPL, too? A serial driver issue? > > AFAIKT there is no SPL. U-Boot is loaded by BL3-1 also in the U-Boot > shipped by amlogic. You're right, Hardkernel's version is without SPL, too. Still I wonder about that "No ma" (after the DRAM line). Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
On Mon, Jul 11, 2016 at 10:15 PM, Andreas Färberwrote: > Am 11.07.2016 um 21:48 schrieb Beniamino Galvani: >> On Mon, Jul 11, 2016 at 05:23:15AM +0100, Peter Robinson wrote: >>> On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färber wrote: Last output: NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO:BL3-1: Initializing runtime services INFO:BL3-1: Preparing for EL3 exit to normal world INFO:BL3-1: Next image address = 0x100 INFO:BL3-1: Next image spsr = 0x3c9 I.e., no U-Boot SPL output on serial. >>> >>> I see similar on Pine64 with 2016.07rc3 >> >> Here the first non-booting commit is: >> >> commit d73718f3236c520a92efa401084c658e6cc067f3 >> Author: Mingkai Hu >> Date: Thu Jul 7 12:22:12 2016 +0800 >> >> armv8: Enable CPUECTLR.SMPEN for coherency > > Thanks! With that reverted I get: > > [...] > NOTICE: BL3-1: v1.0(debug):4d2e34d > NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 > INFO:BL3-1: Initializing runtime services > INFO:BL3-1: Preparing for EL3 exit to normal world > INFO:BL3-1: Next image address = 0x100 > INFO:BL3-1: Next image spsr = 0x3c9 > No match for driver 'eth_designware' > Some drivers were not found > > > U-Boot 2016.07-1-g10a9e48 (Jul 11 2016 - 21:58:13 +0200) odroid-c2 > > DRAM: 2 GiB > No maUsing default environment > > In:serial@4c0 > Out: serial@4c0 > Err: serial@4c0 > Net: No ethernet found. > => > > The eth_designware line (twice, if counting "No ma") is due to what Tom > mentioned wrt DM GPIO, I guess. > > Shouldn't we get a version line from SPL, too? A serial driver issue? AFAIKT there is no SPL. U-Boot is loaded by BL3-1 also in the U-Boot shipped by amlogic. -- Carlo Caione ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
Am 11.07.2016 um 21:48 schrieb Beniamino Galvani: > On Mon, Jul 11, 2016 at 05:23:15AM +0100, Peter Robinson wrote: >> On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färberwrote: >>> Last output: >>> >>> NOTICE: BL3-1: v1.0(debug):4d2e34d >>> NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 >>> INFO:BL3-1: Initializing runtime services >>> INFO:BL3-1: Preparing for EL3 exit to normal world >>> INFO:BL3-1: Next image address = 0x100 >>> INFO:BL3-1: Next image spsr = 0x3c9 >>> >>> I.e., no U-Boot SPL output on serial. >> >> I see similar on Pine64 with 2016.07rc3 > > Here the first non-booting commit is: > > commit d73718f3236c520a92efa401084c658e6cc067f3 > Author: Mingkai Hu > Date: Thu Jul 7 12:22:12 2016 +0800 > > armv8: Enable CPUECTLR.SMPEN for coherency Thanks! With that reverted I get: [...] NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO:BL3-1: Initializing runtime services INFO:BL3-1: Preparing for EL3 exit to normal world INFO:BL3-1: Next image address = 0x100 INFO:BL3-1: Next image spsr = 0x3c9 No match for driver 'eth_designware' Some drivers were not found U-Boot 2016.07-1-g10a9e48 (Jul 11 2016 - 21:58:13 +0200) odroid-c2 DRAM: 2 GiB No maUsing default environment In:serial@4c0 Out: serial@4c0 Err: serial@4c0 Net: No ethernet found. => The eth_designware line (twice, if counting "No ma") is due to what Tom mentioned wrt DM GPIO, I guess. Shouldn't we get a version line from SPL, too? A serial driver issue? Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
On Mon, Jul 11, 2016 at 05:23:15AM +0100, Peter Robinson wrote: > On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färberwrote: > > Last output: > > > > NOTICE: BL3-1: v1.0(debug):4d2e34d > > NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 > > INFO:BL3-1: Initializing runtime services > > INFO:BL3-1: Preparing for EL3 exit to normal world > > INFO:BL3-1: Next image address = 0x100 > > INFO:BL3-1: Next image spsr = 0x3c9 > > > > I.e., no U-Boot SPL output on serial. > > I see similar on Pine64 with 2016.07rc3 Here the first non-booting commit is: commit d73718f3236c520a92efa401084c658e6cc067f3 Author: Mingkai Hu Date: Thu Jul 7 12:22:12 2016 +0800 armv8: Enable CPUECTLR.SMPEN for coherency Mingkai, any ideas about how to debug or fix this? Beniamino ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
Am 11.07.2016 um 06:23 schrieb Peter Robinson: > On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färberwrote: >> P.S. The upstream arm-trusted-firmware fip_create tool doesn't know >> about --bl30 and --bl301 btw, anyone any insights? > > If you find details on the upstream ATF support I'd love a link for more > details https://github.com/ARM-software/arm-trusted-firmware/tree/master/tools/fip_create I found a commit renaming BL3-0 to SCP_BL2, but no mention of BL3-0-1 beyond Hardkernel and this patchset. https://github.com/ARM-software/arm-trusted-firmware/commit/f59821d51255f14e0ac00eef7bc98ef75c686876 $ make -C u-boot-hardkernel fip_create $ ./u-boot-hardkernel/tools/fip_create/fip_create --dump fip.bin Firmware Image Package ToC: --- - SCP Firmware BL3-0: offset=0x4000, size=0x9E88 - SCP Firmware BL3-0-1: offset=0x1, size=0x1758 - EL3 Runtime Firmware BL3-1: offset=0x14000, size=0x110D0 - Non-Trusted Firmware BL3-3: offset=0x28000, size=0x36AF6 --- $ make -C arm-trusted-firmware fiptool $ ./arm-trusted-firmware/tools/fip_create/fip_create --dump fip.bin Firmware Image Package ToC: --- - SCP Firmware SCP_BL2: offset=0xD8, size=0x9E88 - Unknown entry: offset=0x9F60, size=0x1758 - EL3 Runtime Firmware BL31: offset=0xB6B8, size=0x110D0 - Non-Trusted Firmware BL33: offset=0x1C788, size=0x36AF6 --- Note that the offsets for BL30[1] are shown differently. Regards, Andreas -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
On Mon, Jul 11, 2016 at 4:57 AM, Andreas Färberwrote: > Hi, > > Am 08.05.2016 um 08:30 schrieb Beniamino Galvani: >> this series adds a very basic support for Amlogic S905 SoC (GXBaby) >> and for the ODROID-C2 board [1], and is based on u-boot sources >> available from the board vendor [2]. At the moment the only supported >> devices are the integrated UART and Ethernet adapter. > > On current master with these four patches merged, should I expect to see > any output after BL31? o.O > > Note that the README is outdated in that Hardkernel now has sources for > fip_create and no binary any more. I've verified that the behavior is > the same when using the binary and the self-compiled tool. Last output: > > NOTICE: BL3-1: v1.0(debug):4d2e34d > NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 > INFO:BL3-1: Initializing runtime services > INFO:BL3-1: Preparing for EL3 exit to normal world > INFO:BL3-1: Next image address = 0x100 > INFO:BL3-1: Next image spsr = 0x3c9 > > I.e., no U-Boot SPL output on serial. I see similar on Pine64 with 2016.07rc3 > P.S. The upstream arm-trusted-firmware fip_create tool doesn't know > about --bl30 and --bl301 btw, anyone any insights? If you find details on the upstream ATF support I'd love a link for more details ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
Hi, Am 08.05.2016 um 08:30 schrieb Beniamino Galvani: > this series adds a very basic support for Amlogic S905 SoC (GXBaby) > and for the ODROID-C2 board [1], and is based on u-boot sources > available from the board vendor [2]. At the moment the only supported > devices are the integrated UART and Ethernet adapter. On current master with these four patches merged, should I expect to see any output after BL31? o.O Note that the README is outdated in that Hardkernel now has sources for fip_create and no binary any more. I've verified that the behavior is the same when using the binary and the self-compiled tool. Last output: NOTICE: BL3-1: v1.0(debug):4d2e34d NOTICE: BL3-1: Built : 17:08:35, Oct 29 2015 INFO:BL3-1: Initializing runtime services INFO:BL3-1: Preparing for EL3 exit to normal world INFO:BL3-1: Next image address = 0x100 INFO:BL3-1: Next image spsr = 0x3c9 I.e., no U-Boot SPL output on serial. Regards, Andreas P.S. The upstream arm-trusted-firmware fip_create tool doesn't know about --bl30 and --bl301 btw, anyone any insights? -- SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
On 08/05/16 08:30, Beniamino Galvani wrote: > Hi, > > this series adds a very basic support for Amlogic S905 SoC (GXBaby) > and for the ODROID-C2 board [1], and is based on u-boot sources > available from the board vendor [2]. At the moment the only supported > devices are the integrated UART and Ethernet adapter. Hey guys, what's left for this patchset to be merged? -- Carlo Caione ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
Re: [U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
On Sun, May 29, 2016 at 06:38:14PM +0200, Carlo Caione wrote: > On 08/05/16 08:30, Beniamino Galvani wrote: > > Hi, > > > > this series adds a very basic support for Amlogic S905 SoC (GXBaby) > > and for the ODROID-C2 board [1], and is based on u-boot sources > > available from the board vendor [2]. At the moment the only supported > > devices are the integrated UART and Ethernet adapter. > > Hey guys, > what's left for this patchset to be merged? Good timing. I've got this locally and just need to finish my unit tests before I can merge. But, due to the DM PR I've had to disable eth as you'll need to address GPIO for this platform next. Thanks! -- Tom signature.asc Description: Digital signature ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
[U-Boot] [PATCH v7 0/4] Amlogic Meson GXBaby and ODROID-C2 support
Hi, this series adds a very basic support for Amlogic S905 SoC (GXBaby) and for the ODROID-C2 board [1], and is based on u-boot sources available from the board vendor [2]. At the moment the only supported devices are the integrated UART and Ethernet adapter. Changes since v6: - documented ARCH_MESON Kconfig entry Changes since v5: - used default CONFIG_SYS_BAUDRATE_TABLE - removed check for CONFIG_IDENT_STRING Changes since v4: - added patch to implement generic PSCI reset - used min() macro from linux/kernel.h Changes since v3: - designware eth: added check that buffer addresses are in first 4GiB as suggested by Marek (and thus removed the ack tags) - consolidated pinmux and gpio macros - used get_unaligned_be64() to avoid alignment faults in dram_init() - uint32_t -> u32 in serial_meson.c - implemented reboot and read from e-fuse through secure monitor Changes since v2: - squashed all platform patches into a single one - got rid of additional non-upstream DTS node for ethernet - improved board README - added macros for SoC registers fields Changes since v1: - updated DTS files from Linux kernel - added Ethernet support - first 16MiB of RAM are now marked as unavailable; this seems to be required to successfully boot Linux - fixed typo in config file [1] http://www.hardkernel.com/main/products/prdt_info.php?g_code=G145457216438 [2] https://github.com/hardkernel/u-boot/tree/odroidc2-v2015.01 Beniamino Galvani (4): arm: implement generic PSCI reset call for armv8 net: designware: fix descriptor layout and warnings on 64-bit archs arm: add initial support for Amlogic Meson and ODROID-C2 arm: meson: implement calls to secure monitor arch/arm/Kconfig | 9 ++ arch/arm/Makefile | 1 + arch/arm/cpu/armv8/fwcall.c| 16 +++ arch/arm/dts/Makefile | 2 + arch/arm/dts/meson-gxbb-odroidc2.dts | 69 + arch/arm/dts/meson-gxbb.dtsi | 178 + arch/arm/include/asm/arch-meson/gxbb.h | 52 ++ arch/arm/include/asm/arch-meson/sm.h | 12 +++ arch/arm/include/asm/psci.h| 17 +++- arch/arm/include/asm/system.h | 2 + arch/arm/mach-meson/Kconfig| 31 ++ arch/arm/mach-meson/Makefile | 7 ++ arch/arm/mach-meson/board.c| 67 + arch/arm/mach-meson/sm.c | 57 +++ board/hardkernel/odroid-c2/Kconfig | 12 +++ board/hardkernel/odroid-c2/MAINTAINERS | 6 ++ board/hardkernel/odroid-c2/Makefile| 7 ++ board/hardkernel/odroid-c2/README | 60 +++ board/hardkernel/odroid-c2/odroid-c2.c | 67 + configs/odroid-c2_defconfig| 23 + drivers/net/designware.c | 59 ++- drivers/net/designware.h | 4 +- drivers/serial/Kconfig | 15 +++ drivers/serial/Makefile| 1 + drivers/serial/serial_meson.c | 162 ++ include/configs/odroid-c2.h| 51 ++ 26 files changed, 957 insertions(+), 30 deletions(-) create mode 100644 arch/arm/dts/meson-gxbb-odroidc2.dts create mode 100644 arch/arm/dts/meson-gxbb.dtsi create mode 100644 arch/arm/include/asm/arch-meson/gxbb.h create mode 100644 arch/arm/include/asm/arch-meson/sm.h create mode 100644 arch/arm/mach-meson/Kconfig create mode 100644 arch/arm/mach-meson/Makefile create mode 100644 arch/arm/mach-meson/board.c create mode 100644 arch/arm/mach-meson/sm.c create mode 100644 board/hardkernel/odroid-c2/Kconfig create mode 100644 board/hardkernel/odroid-c2/MAINTAINERS create mode 100644 board/hardkernel/odroid-c2/Makefile create mode 100644 board/hardkernel/odroid-c2/README create mode 100644 board/hardkernel/odroid-c2/odroid-c2.c create mode 100644 configs/odroid-c2_defconfig create mode 100644 drivers/serial/serial_meson.c create mode 100644 include/configs/odroid-c2.h -- 2.7.3 ___ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot