November 2023 - U-Boot

[PATCH] sunxi: h616: (really) lower SPL stack address to avoid BROM data
by Andre Przywara 06 Nov '23

06 Nov '23

When using the USB OTG FEL mode on the Allwinner H616, the BootROM stores some data at the end of SRAM C. This is also the location where we place the initial SPL stack, so it will overwrite this data. We still need the BROM code after running the SPL, so should leave that area alone. Interestingly this does not seem to have an adverse effect, I guess on the "way out" (when we return to FEL after the SPL has run), this data is not needed by the BROM, for just the trailing end of the USB operation. However this is still wrong, and we should not clobber BROM data. Lower the SPL stack address to be situated right below the swap buffers we use in sunxi-fel: that should be out of the way of everyone else. This obsoletes a previous commit (eb53e7743c8f) with the same name: that one was changing the address in an *unused* macro in sunxi_common.h, so the previous patch didn't have any effect at all. Fixes: eb53e7743c8f ("sunxi: h616: lower SPL stack address to avoid BROM data") Signed-off-by: Andre Przywara <andre.przywara(a)arm.com> --- Hi, sorry for the blunder with that previous patch! This issue came up when cleaning up some SPL code: LOW_LEVEL_SRAM_STACK, as changed in the previous patch, is not used anywhere. I have a patch to remove that whole section from sunxi-common.h, and will send that as part of some bigger SPL clean-up series later. Cheers, Andre common/spl/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/common/spl/Kconfig b/common/spl/Kconfig index 25cd18afda7..c521b02f4a3 100644 --- a/common/spl/Kconfig +++ b/common/spl/Kconfig @@ -370,7 +370,7 @@ config SPL_STACK default 0x93ffb8 if ARCH_MX6 && MX6_OCRAM_256KB default 0x91ffb8 if ARCH_MX6 && !MX6_OCRAM_256KB default 0x118000 if MACH_SUN50I_H6 - default 0x58000 if MACH_SUN50I_H616 + default 0x52a00 if MACH_SUN50I_H616 default 0x40000 if MACH_SUN8I_R528 default 0x54000 if MACH_SUN50I || MACH_SUN50I_H5 default 0x18000 if MACH_SUN9I -- 2.35.8

1 0

uboot reports adding disk failed(EFI_NOT_FOUND) and first disk is gone in next scsi scan
by Hongxing Zhu 06 Nov '23

06 Nov '23

Hi Simon: Nice to meet you. The u-boot I used is based on v2023.04 tagged version. Layerscape LX2160A RDB board has four SATA controllers. Based on LX2160A RDB board and two or more SATA disks connected. I encounter one "scsi scan" problem. After the first SATA disk is detected and probed properly in the first "scsi scan". The other disks would complain that "EFI_NOT_FOUND" error listed below, when run the first "scsi scan" command in uboot environment. Does this error matter? BTW, "scsi info" says that all disk info can be dumped, and all disks are works well, after the first "scsi scan" In the consecutive rescan operations issued by "scsi reset" or "scsi scan" commends, the disks would report "unable to unbind devices (-1E)" error. The first disk is disappeared at all after the next "scsi scan" operations is finished. Did you used to encounter such kind of issue? Any suggestions and guidance are very appreciated. Logs: => scsi scan scanning bus for devices... Target spinup took 0 ms. AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst Device 0: (0:0) Vendor: ATA Prod.: ST1000DM010-2EP1 Rev: CC43 Type: Hard Disk Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) Target spinup took 0 ms. AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst Adding disk for ahci_scsi.id0lun0 failed (err=-9223372036854775788/0x8000000000000014) SATA link 0 timeout. AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst SATA link 0 timeout. AHCI 0001.0301 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: 64bit ncq pm clo only pmp fbss pio slum part ccc apst => scsi info Device 0: (0:0) Vendor: ATA Prod.: ST1000DM010-2EP1 Rev: CC43 Type: Hard Disk Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512) Device 1: (0:0) Vendor: ATA Prod.: ST500DM002-1BD14 Rev: KC45 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) => ls scsi 0:1 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found <snip> <DIR> 4096 var <SYM> 12 linuxrc => ls scsi 1:1 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found <snip> <DIR> 4096 usr <DIR> 4096 var => scsi reset Reset SCSI scanning bus for devices... unable to unbind devices (-1E) => ls scsi 0:1 ** Bad device specification scsi 0 ** Couldn't find partition scsi 0:1 => ls scsi 1:1 <DIR> 4096 . <DIR> 4096 .. <DIR> 16384 lost+found <snip> <DIR> 4096 var => scsi info Device 1: (0:0) Vendor: ATA Prod.: ST500DM002-1BD14 Rev: KC45 Type: Hard Disk Capacity: 476940.0 MB = 465.7 GB (976773168 x 512) Best Regards Richard Zhu

3 4

[PATCH 1/2] dt-bindings: phy-mtk-tphy: add properties for phy tuning
by Chunfeng Yun 06 Nov '23

06 Nov '23

Add properties to improve eye diagram which sometimes need adjust some parameters of u2phy; Add a property to tune disconnect threshold; Signed-off-by: Chunfeng Yun <chunfeng.yun(a)mediatek.com> --- doc/device-tree-bindings/phy/phy-mtk-tphy.txt | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/doc/device-tree-bindings/phy/phy-mtk-tphy.txt b/doc/device-tree-bindings/phy/phy-mtk-tphy.txt index 3042c39d09..300e236b5b 100644 --- a/doc/device-tree-bindings/phy/phy-mtk-tphy.txt +++ b/doc/device-tree-bindings/phy/phy-mtk-tphy.txt @@ -52,6 +52,15 @@ Optional properties (port (child) node): "da_ref": the reference clock of analog phy, used if the clocks of analog and digital phys are separated, otherwise uses "ref" clock only if needed. +- mediatek,eye-vrt : The selection of VRT reference voltage (U2 phy), + the value is [1, 7] +- mediatek,eye-term : The selection of HS_TX TERM reference voltage (U2 phy), + the value is [1, 7] +- mediatek,discth : The selection of disconnect threshold (U2 phy), + the value is [1, 15] +- mediatek,pre-emphasis : The level of pre-emphasis which used to widen + the eye opening and boost eye swing, + the value is [1, 3] Example: -- 2.25.1

1 1

[PATCH v2] x86: serial: ns16550: Allow the UART to be silently disabled
by Simon Glass 05 Nov '23

05 Nov '23

U-Boot normally requires a UART. When booting from coreboot it is sometimes just not available, e.g. when no sysinfo or DBG2 information is provided. In this case we need to continue running, since the display can be used. Add a flag to disable serial for this case. This allows U-Boot to start up and operation from the display, instead of hanging on start-up. This could perhaps be hidden behind a Kconfig option to reduce code size. Signed-off-by: Simon Glass <sjg(a)chromium.org> --- Changes in v2: - Drop RFC tag since there were no comments drivers/serial/ns16550.c | 17 +++++++++++++++-- drivers/serial/serial_coreboot.c | 1 + include/ns16550.h | 1 + 3 files changed, 17 insertions(+), 2 deletions(-) diff --git a/drivers/serial/ns16550.c b/drivers/serial/ns16550.c index 6deb1d8ddc5..a0545f37cb6 100644 --- a/drivers/serial/ns16550.c +++ b/drivers/serial/ns16550.c @@ -385,6 +385,8 @@ static int ns16550_serial_putc(struct udevice *dev, const char ch) { struct ns16550 *const com_port = dev_get_priv(dev); + if (com_port->plat->flags & NS16550_FLAG_DISABLE) + return 0; if (!(serial_in(&com_port->lsr) & UART_LSR_THRE)) return -EAGAIN; serial_out(ch, &com_port->thr); @@ -405,6 +407,9 @@ static int ns16550_serial_pending(struct udevice *dev, bool input) { struct ns16550 *const com_port = dev_get_priv(dev); + if (com_port->plat->flags & NS16550_FLAG_DISABLE) + return 0; + if (input) return (serial_in(&com_port->lsr) & UART_LSR_DR) ? 1 : 0; else @@ -415,6 +420,9 @@ static int ns16550_serial_getc(struct udevice *dev) { struct ns16550 *const com_port = dev_get_priv(dev); + if (com_port->plat->flags & NS16550_FLAG_DISABLE) + return 0; + if (!(serial_in(&com_port->lsr) & UART_LSR_DR)) return -EAGAIN; @@ -429,7 +437,8 @@ static int ns16550_serial_setbrg(struct udevice *dev, int baudrate) clock_divisor = ns16550_calc_divisor(com_port, plat->clock, baudrate); - ns16550_setbrg(com_port, clock_divisor); + if (!(plat->flags & NS16550_FLAG_DISABLE)) + ns16550_setbrg(com_port, clock_divisor); return 0; } @@ -442,6 +451,9 @@ static int ns16550_serial_setconfig(struct udevice *dev, uint serial_config) uint bits = SERIAL_GET_BITS(serial_config); uint stop = SERIAL_GET_STOP(serial_config); + if (com_port->plat->flags & NS16550_FLAG_DISABLE) + return 0; + /* * only parity config is implemented, check if other serial settings * are the default one. @@ -534,7 +546,8 @@ int ns16550_serial_probe(struct udevice *dev) reset_deassert_bulk(&reset_bulk); com_port->plat = dev_get_plat(dev); - ns16550_init(com_port, -1); + if (!(plat->flags & NS16550_FLAG_DISABLE)) + ns16550_init(com_port, -1); return 0; } diff --git a/drivers/serial/serial_coreboot.c b/drivers/serial/serial_coreboot.c index 23066e4d054..cdf9afc1739 100644 --- a/drivers/serial/serial_coreboot.c +++ b/drivers/serial/serial_coreboot.c @@ -120,6 +120,7 @@ static int coreboot_of_to_plat(struct udevice *dev) * there is no UART, which may panic. So stay silent and * pray that the video console will work. */ + plat->flags |= NS16550_FLAG_DISABLE; log_debug("Cannot detect UART\n"); } diff --git a/include/ns16550.h b/include/ns16550.h index 7f481300083..3c4f3e7539a 100644 --- a/include/ns16550.h +++ b/include/ns16550.h @@ -52,6 +52,7 @@ enum ns16550_flags { NS16550_FLAG_IO = 1 << 0, /* Use I/O access (else mem-mapped) */ NS16550_FLAG_ENDIAN = 1 << 1, /* Use out_le/be_32() */ NS16550_FLAG_BE = 1 << 2, /* Big-endian access (else little) */ + NS16550_FLAG_DISABLE = BIT(3), /* No output or input */ }; /** -- 2.42.0.820.g83a721a137-goog

2 1

[PATCH V2] doc: falcon: riscv: Falcon Mode boot on RISC-V
by Randolph 05 Nov '23

05 Nov '23

Add documentation to introduce the Falcon Mode on RISC-V. In this mode, the boot sequence is SPL -> OpenSBI -> Linux kernel. Signed-off-by: Randolph <randolph(a)andestech.com> --- doc/develop/falcon.rst | 159 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 159 insertions(+) diff --git a/doc/develop/falcon.rst b/doc/develop/falcon.rst index 2f25fc8532..b553f0d0ea 100644 --- a/doc/develop/falcon.rst +++ b/doc/develop/falcon.rst @@ -256,3 +256,162 @@ the following command: Falcon Mode was presented at the RMLL 2012. Slides are available at: http://schedule2012.rmll.info/IMG/pdf/LSM2012_UbootFalconMode_Babic.pdf + +Falcon Mode Boot on RISC-V +-------------------------- + +Introduction +------------ + +In the RISC-V environment, OpenSBI is required to enable a supervisor mode +to execute certain privileged operations. The typical boot sequence on +RISC-V is SPL -> OpenSBI -> U-Boot -> Linux kernel. SPL will load and start +the OpenSBI initializations, then OpenSBI will bring up the next image, U-Boot. +The OpenSBI binary must be prepared in advance of the U-Boot build process +and it will be packed together with U-Boot into a file called u-boot.itb. + +The Falcon Mode on RISC-V platforms is a distinct boot process. Borrowing +ideas from the U-Boot Falcon Mode on ARM, it skips the U-Boot proper phase +in the normal boot process and allows OpenSBI to load and start the Linux +kernel. Its boot sequence is SPL -> OpenSBI -> Linux kernel. The OpenSBI +binary and Linux kernel binary must be prepared prior to the U-Boot build +process and they will be packed together as linux.itb in this process. + +CONFIG_SPL_LOAD_FIT_OPENSBI_OS_BOOT enables the Falcon Mode boot on RISC-V. +This configuration tells OpenSBI that Linux kernel is its next OS image and +makes it load and start the kernel afterwards. + +Note that the Falcon Mode boot bypasses a lot of initializations by U-Boot. +If the Linux kernel expects hardware initializations by U-Boot, make sure to +port the relevant code to the SPL build process. + +Configurations +-------------- + +CONFIG_SPL_LOAD_FIT_ADDRESS + Specifies the address to load u-boot.itb in a normal boot. When the Falcon + Mode boot is enabled, it specifies the load address of linux.itb. + +CONFIG_SYS_TEXT_BASE + Specifies the address of the text section for a u-boot proper in a normal + boot. When the Falcon Mode boot is enabled, it specifies the text section + address for the Linux kernel image. + +CONFIG_SPL_LOAD_FIT_OPENSBI_OS_BOOT + Activates the Falcon Mode boot on RISC-V. + +Function that a board must implement +------------------------------------ + +Initially, SPL places the FDT blob right after the kernel. As the kernel does +not include the BSS section in its size calculation, SPL ends up placing the +FDT blob within the BSS section of the kernel. This may cause the FDT blob to +be cleared during kernel BSS initialization. To avoid the issue, be sure to +move the FDT blob out of the kernel first. + +void spl_perform_fixups(struct spl_image_info *spl_image) + required, necessary action to move the FDT blob out of the Linux kernel BSS + section + +Example for Andes AE350 Board +----------------------------- + +A FDT blob is required to boot the Linux kernel from the SPL. Andes AE350 +platforms generally come with a builtin dtb. If you want to load a custom DTB, +follow the steps below: + +1. Load the custom DTB to SDRAM:: + + => fatload mmc 0:1 0x20000000 user_custom.dtb + +2. Set the SPI speed:: + + => sf probe 0:0 50000000 0 + +3. Erase sectors from the SPI Flash:: + + => sf erase 0xf0000 0x10000 + +4. Write the FDT blob to the erased sectors of the Flash:: + + => sf write 0x20000000 0xf0000 0x10000 + +Console Log of AE350 Falcon Mode Boot +------------------------------------- + +U-Boot SPL 2023.01-00031-g777ecdea66 (Oct 31 2023 - 18:41:36 +0800) +Trying to boot from RAM + +OpenSBI v1.2-51-g7304e42 + ____ _____ ____ _____ + / __ \ / ____| _ \_ _| + | | | |_ __ ___ _ __ | (___ | |_) || | + | | | | '_ \ / _ \ '_ \ \___ \| _ < | | + | |__| | |_) | __/ | | |____) | |_) || |_ + \____/| .__/ \___|_| |_|_____/|____/_____| + | | + |_| + +Platform Name : andestech,ax25 +Platform Features : medeleg +Platform HART Count : 1 +Platform IPI Device : andes_plicsw +Platform Timer Device : andes_plmt @ 60000000Hz +Platform Console Device : uart8250 +Platform HSM Device : andes_smu +Platform PMU Device : andes_pmu +Platform Reboot Device : atcwdt200 +Platform Shutdown Device : --- +Firmware Base : 0x0 +Firmware Size : 196 KB +Runtime SBI Version : 1.0 + +Domain0 Name : root +Domain0 Boot HART : 0 +Domain0 HARTs : 0* +Domain0 Region00 : 0x0000000000000000-0x000000000003ffff () +Domain0 Region01 : 0x00000000e6000000-0x00000000e60fffff (I,R) +Domain0 Region02 : 0x00000000e6400000-0x00000000e67fffff (I) +Domain0 Region03 : 0x0000000000000000-0xffffffffffffffff (R,W,X) +Domain0 Next Address : 0x0000000001800000 +Domain0 Next Arg1 : 0x0000000001700000 +Domain0 Next Mode : S-mode +Domain0 SysReset : yes + +Boot HART ID : 0 +Boot HART Domain : root +Boot HART Priv Version : v1.11 +Boot HART Base ISA : rv64imafdcx +Boot HART ISA Extensions : none +Boot HART PMP Count : 8 +Boot HART PMP Granularity : 4 +Boot HART PMP Address Bits: 31 +Boot HART MHPM Count : 4 +Boot HART MHPM Bits : 64 +Boot HART MIDELEG : 0x0000000000000222 +Boot HART MEDELEG : 0x000000000000b109 +[ 0.000000] Linux version 6.1.47-09019-g0584b09ad862-dirty +[ 0.000000] OF: fdt: Ignoring memory range 0x0 - 0x1800000 +[ 0.000000] Machine model: andestech,ax25 +[ 0.000000] earlycon: sbi0 at I/O port 0x0 (options '') +[ 0.000000] printk: bootconsole [sbi0] enabled +[ 0.000000] Disabled 4-level and 5-level paging +[ 0.000000] efi: UEFI not found. +[ 0.000000] Zone ranges: +[ 0.000000] DMA32 [mem 0x0000000001800000-0x000000003fffffff] +[ 0.000000] Normal empty +[ 0.000000] Movable zone start for each node +[ 0.000000] Early memory node ranges +[ 0.000000] node 0: [mem 0x0000000001800000-0x000000003fffffff] +[ 0.000000] Initmem setup node 0 [mem 0x0000000001800000-0x000000003fffffff] +[ 0.000000] SBI specification v1.0 detected +[ 0.000000] SBI implementation ID=0x1 Version=0x10002 +[ 0.000000] SBI TIME extension detected +[ 0.000000] SBI IPI extension detected +[ 0.000000] SBI RFENCE extension detected +[ 0.000000] SBI SRST extension detected +[ 0.000000] SBI HSM extension detected +[ 0.000000] riscv: base ISA extensions acim +[ 0.000000] riscv: ELF capabilities acim +[ 0.000000] percpu: Embedded 18 pages/cpu s35000 r8192 d30536 u73728 +[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 252500 -- 2.34.1

2 1

[PATCH 1/1] dm: fix misleading messages
by Heinrich Schuchardt 04 Nov '23

04 Nov '23

When no RNG device exists for a driver referenced via U_BOOT_DRVINFO() we get messages like: No match for driver 'arm-rndr' Some drivers were not found This is misleading as it is not the driver that was not found, it is the device that is not found. Correct the messages. Reported-by: Andre Przywara <andre.przywara(a)arm.com> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt(a)canonical.com> --- drivers/core/lists.c | 2 +- drivers/core/root.c | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/core/lists.c b/drivers/core/lists.c index 8034a8f48d..e39d3acc97 100644 --- a/drivers/core/lists.c +++ b/drivers/core/lists.c @@ -97,7 +97,7 @@ static int bind_drivers_pass(struct udevice *parent, bool pre_reloc_only) if (CONFIG_IS_ENABLED(OF_PLATDATA)) drt->dev = dev; } else if (ret != -EPERM) { - dm_warn("No match for driver '%s'\n", entry->name); + dm_warn("No device for driver '%s'\n", entry->name); if (!result || ret != -ENOENT) result = ret; } diff --git a/drivers/core/root.c b/drivers/core/root.c index d4ae652bcf..29c918eb73 100644 --- a/drivers/core/root.c +++ b/drivers/core/root.c @@ -167,7 +167,7 @@ int dm_scan_plat(bool pre_reloc_only) ret = lists_bind_drivers(DM_ROOT_NON_CONST, pre_reloc_only); if (ret == -ENOENT) { - dm_warn("Some drivers were not found\n"); + dm_warn("Some devices were not found\n"); ret = 0; } -- 2.40.1

2 3

[PATCH v2 1/2] pico-pi-imx6ul: Connvert to DM_SERIAL
by Fabio Estevam 04 Nov '23

04 Nov '23

From: Fabio Estevam <festevam(a)denx.de> The conversion to DM_SERIAL is mandatory, so select this option. Signed-off-by: Fabio Estevam <festevam(a)denx.de> --- Changes since v1: - None configs/pico-pi-imx6ul_defconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/configs/pico-pi-imx6ul_defconfig b/configs/pico-pi-imx6ul_defconfig index 1eee1e6c2ff5..3af968d55128 100644 --- a/configs/pico-pi-imx6ul_defconfig +++ b/configs/pico-pi-imx6ul_defconfig @@ -70,6 +70,7 @@ CONFIG_DM_REGULATOR=y CONFIG_DM_REGULATOR_PFUZE100=y CONFIG_DM_REGULATOR_FIXED=y CONFIG_DM_REGULATOR_GPIO=y +CONFIG_DM_SERIAL=y CONFIG_MXC_UART=y CONFIG_USB=y CONFIG_SPL_USB_HOST=y -- 2.34.1

1 1

[PATCH] m68k: remove common.h references
by Angelo Dureghello 04 Nov '23

04 Nov '23

In one case (mcffec.c), had to replace common.h include with config.h, to avoid CFG_SYS_CACHE_ACR0 redefine-order conflict. Signed-off-by: Angelo Dureghello <angelo(a)kernel-space.org> --- drivers/net/mcffec.c | 2 +- drivers/net/mcfmii.c | 1 - drivers/rtc/mcfrtc.c | 2 -- drivers/serial/serial_mcf.c | 1 - drivers/watchdog/mcf_wdt.c | 1 - 5 files changed, 1 insertion(+), 6 deletions(-) diff --git a/drivers/net/mcffec.c b/drivers/net/mcffec.c index ec1fae9688..4e0a9a8b7c 100644 --- a/drivers/net/mcffec.c +++ b/drivers/net/mcffec.c @@ -10,8 +10,8 @@ * (C) 2019 Angelo Dureghello <angelo.dureghello(a)timesys.com> */ -#include <common.h> #include <env.h> +#include <config.h> #include <hang.h> #include <malloc.h> #include <command.h> diff --git a/drivers/net/mcfmii.c b/drivers/net/mcfmii.c index eae2065451..9bf887035d 100644 --- a/drivers/net/mcfmii.c +++ b/drivers/net/mcfmii.c @@ -4,7 +4,6 @@ * TsiChung Liew (Tsi-Chung.Liew(a)freescale.com) */ -#include <common.h> #include <config.h> #include <net.h> #include <netdev.h> diff --git a/drivers/rtc/mcfrtc.c b/drivers/rtc/mcfrtc.c index d2ac889c30..9708971c5c 100644 --- a/drivers/rtc/mcfrtc.c +++ b/drivers/rtc/mcfrtc.c @@ -4,8 +4,6 @@ * TsiChung Liew (Tsi-Chung.Liew(a)freescale.com) */ -#include <common.h> - #include <command.h> #include <rtc.h> #include <asm/immap.h> diff --git a/drivers/serial/serial_mcf.c b/drivers/serial/serial_mcf.c index bb2afd0d8c..76143575fa 100644 --- a/drivers/serial/serial_mcf.c +++ b/drivers/serial/serial_mcf.c @@ -15,7 +15,6 @@ * as serial console interface. */ -#include <common.h> #include <dm.h> #include <asm/global_data.h> #include <dm/platform_data/serial_coldfire.h> diff --git a/drivers/watchdog/mcf_wdt.c b/drivers/watchdog/mcf_wdt.c index b36488bb5b..b555bbeb68 100644 --- a/drivers/watchdog/mcf_wdt.c +++ b/drivers/watchdog/mcf_wdt.c @@ -6,7 +6,6 @@ * */ -#include <common.h> #include <dm.h> #include <hang.h> #include <asm/io.h> -- 2.42.0

1 0

[PATCH] doc: build: fix wrongly written targests instead of targets
by Milan P. Stanić 04 Nov '23

04 Nov '23

Signed-off-by: Milan P. Stanić <mps(a)arvanta.net> --- doc/build/gcc.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/build/gcc.rst b/doc/build/gcc.rst index 23501dea37..3c64657727 100644 --- a/doc/build/gcc.rst +++ b/doc/build/gcc.rst @@ -66,7 +66,7 @@ For building U-Boot on Alpine Linux at least the following packages are needed: Depending on the build target further packages may be needed: * sandbox with lcd: sdl2-dev -* riscv64 S-mode targests: opensbi +* riscv64 S-mode targets: opensbi * some arm64 targets: arm-trusted-firmware Prerequisites -- 2.42.1

2 1

Re: U-boot env in binary format
by Simon Glass 04 Nov '23

04 Nov '23

On Wed, 1 Nov 2023 at 18:58, SIMON BABY <simonkbaby(a)gmail.com> wrote: > > Thanks Simon. > I will try this command. By any chance how do I find the environment partition size in my target? (please do try to avoid top-posting on the ML, and keep the ML copied) I think this depends on your platform, but you might find the information in the fixed-partitions node in the devicetree? - Simon > > Regards > Simon > > On Wed, Nov 1, 2023 at 1:22 PM Simon Glass <sjg(a)chromium.org> wrote: >> >> Hi Simon, >> >> On Tue, 31 Oct 2023 at 17:07, SIMON BABY <simonkbaby(a)gmail.com> wrote: >> > >> > Hello , >> > Can I know if I could generate uboot env file in binary format as part of my build process ? >> > Currently it generate as a text file . >> >> There is the tools/mkenvimage program: >> >> mkenvimage [-h] [-r] [-b] [-p <byte>] -s <environment partition size> >> -o <output> <input file> >> >> This tool takes a key=value input file (same as would a `printenv' >> show) and generates the corresponding environment image, ready to be >> flashed. >> >> The input file is in format: >> key1=value1 >> key2=value2 >> ... >> Empty lines are skipped, and lines with a # in the first >> column are treated as comments (also skipped). >> -r : the environment has multiple copies in flash >> -b : the target is big endian (default is little endian) >> -p <byte> : fill the image with <byte> bytes instead of 0xff bytes >> -V : print version information and exit >> >> If the input file is "-", data is read from standard input >> >> You can build with 'make u-boot-initial-env' to get a tool called >> printinitialenv to run, which emits the environment. Or you can look >> in include/generated/ to see the env files from the build. >> >> If you would like to send a documentation patch, it could go here: >> >> https://u-boot.readthedocs.io/en/latest/usage/environment.html >> >> (in the source tree this is doc/usage/environment.html) >> >> Regards, >> Simon

1 0