Message ID | d55c7bc7-e754-ea18-c112-fc9b4368e86a@denx.de |
---|---|
State | Accepted |
Delegated to: | Tom Rini |
Headers | show |
Series | Pull request: please pull u-boot-imx-20230503 | expand |
On Wed, May 03, 2023 at 01:37:28PM +0200, Stefano Babic wrote: > Hi Tom, > > please pull from u-boot-imx, thanks ! > > > The following changes since commit 50f64026f7a4c2d0a101c93916e01782e4fbbe7f: > > Merge branch 'master' of > https://source.denx.de/u-boot/custodians/u-boot-spi (2023-05-01 13:29:52 > -0400) > > are available in the Git repository at: > > https://gitlab.denx.de/u-boot/custodians/u-boot-imx.git > tags/u-boot-imx-20230503 > > for you to fetch changes up to bb6ea0fe9290b4d64df8e716b58515b5325c2ea5: > > usb: ehci-mx6: move phy setup before register access (2023-05-02 10:57:32 > +0200) > So, both my HW test and CI is fine, so I've applied this. But please note we now have this scary message to fix: +(imx8qm_dmsse20a1) aarch64-linux-ld.bfd: invalid origin for memory region .sdram
Hi Tom, On Wed, May 3, 2023 at 4:01 PM Tom Rini <trini@konsulko.com> wrote: > So, both my HW test and CI is fine, so I've applied this. But please > note we now have this scary message to fix: > +(imx8qm_dmsse20a1) aarch64-linux-ld.bfd: invalid origin for memory region .sdram I compared the imx8qm_dmsse20a1 against imx8qm_mek_defconfig and with the following changes the warning is gone: --- a/configs/imx8qm_dmsse20a1_defconfig +++ b/configs/imx8qm_dmsse20a1_defconfig @@ -16,6 +16,7 @@ CONFIG_SPL_SERIAL=y CONFIG_SPL_DRIVERS_MISC=y CONFIG_ENV_OFFSET=0x80000 CONFIG_ENV_SECT_SIZE=0x20000 +CONFIG_SPL_STACK=0x13e000 CONFIG_SPL=y CONFIG_SYS_LOAD_ADDR=0x80280000 CONFIG_SYS_MEMTEST_START=0xA0000000 @@ -38,11 +39,17 @@ CONFIG_USE_BOOTCOMMAND=y CONFIG_BOOTCOMMAND="mmc dev ${mmcdev}; if mmc rescan; then if run loadbootscript; then run bootscript; else if run loadimage; then run mmcboot; else run netboot; fi; fi; else booti ${loadaddr} - ${fdt_addr}; fi" CONFIG_LOG=y CONFIG_BOARD_EARLY_INIT_F=y -CONFIG_SPL_BSS_START_ADDR=0x00128000 CONFIG_SPL_MAX_SIZE=0x1f000 +CONFIG_SPL_HAS_BSS_LINKER_SECTION=y +CONFIG_SPL_BSS_START_ADDR=0x128000 CONFIG_SPL_BSS_MAX_SIZE=0x1000 CONFIG_SPL_BOARD_INIT=y -CONFIG_SPL_SEPARATE_BSS=y +CONFIG_SPL_SYS_MALLOC_SIMPLE=y +# CONFIG_SPL_SHARES_INIT_SP_ADDR is not set +CONFIG_SYS_SPL_MALLOC=y +CONFIG_HAS_CUSTOM_SPL_MALLOC_START=y +CONFIG_CUSTOM_SYS_SPL_MALLOC_ADDR=0x120000 +CONFIG_SYS_SPL_MALLOC_SIZE=0x3000 CONFIG_SPL_POWER_SUPPORT=y CONFIG_SPL_POWER_DOMAIN=y CONFIG_SPL_WATCHDOG_SUPPORT=y Oliver, could you please test this change? I can submit it formally if it works for you.
> Am 03.05.2023 um 23:25 schrieb Fabio Estevam <festevam@gmail.com>: > > --- a/configs/imx8qm_dmsse20a1_defconfig > +++ b/configs/imx8qm_dmsse20a1_defconfig > @@ -16,6 +16,7 @@ CONFIG_SPL_SERIAL=y > CONFIG_SPL_DRIVERS_MISC=y > CONFIG_ENV_OFFSET=0x80000 > CONFIG_ENV_SECT_SIZE=0x20000 > +CONFIG_SPL_STACK=0x13e000 > CONFIG_SPL=y > CONFIG_SYS_LOAD_ADDR=0x80280000 > CONFIG_SYS_MEMTEST_START=0xA0000000 > @@ -38,11 +39,17 @@ CONFIG_USE_BOOTCOMMAND=y > CONFIG_BOOTCOMMAND="mmc dev ${mmcdev}; if mmc rescan; then if run > loadbootscript; then run bootscript; else if run loadimage; then run > mmcboot; else run netboot; fi; fi; else booti ${loadaddr} - > ${fdt_addr}; fi" > CONFIG_LOG=y > CONFIG_BOARD_EARLY_INIT_F=y > -CONFIG_SPL_BSS_START_ADDR=0x00128000 > CONFIG_SPL_MAX_SIZE=0x1f000 > +CONFIG_SPL_HAS_BSS_LINKER_SECTION=y > +CONFIG_SPL_BSS_START_ADDR=0x128000 > CONFIG_SPL_BSS_MAX_SIZE=0x1000 > CONFIG_SPL_BOARD_INIT=y > -CONFIG_SPL_SEPARATE_BSS=y > +CONFIG_SPL_SYS_MALLOC_SIMPLE=y > +# CONFIG_SPL_SHARES_INIT_SP_ADDR is not set > +CONFIG_SYS_SPL_MALLOC=y > +CONFIG_HAS_CUSTOM_SPL_MALLOC_START=y > +CONFIG_CUSTOM_SYS_SPL_MALLOC_ADDR=0x120000 > +CONFIG_SYS_SPL_MALLOC_SIZE=0x3000 > CONFIG_SPL_POWER_SUPPORT=y > CONFIG_SPL_POWER_DOMAIN=y > CONFIG_SPL_WATCHDOG_SUPPORT=y Hello Fabio, just tested this change and its working fine on the dmsse20a1 board. Tested-by: Oliver Graute <oliver.graute@kococonnector.com> Best regards, Oliver