public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: from https://gitlab.denx.de/u-boot/custodians/u-boot-mips:f3d8c7f8d3c02ff1de172aff7e6392a9ddd1f5b2 to master:
Date: Tue, 1 Sep 2020 15:21:07 +0200	[thread overview]
Message-ID: <a8e2069c-cde0-671e-e172-3e6aec8bb2ae@denx.de> (raw)
In-Reply-To: <e63923fd-6b8a-73ce-1f54-bc9eef88578d@mclink.it>

Hi Mauro,

On 01.09.20 15:09, Mauro Condarelli wrote:

<snip>

> Now problem is "Unable to allocate 209398 bytes for LZMA"
> Full trace below.
> 
> I assume I should enlarge
> #define CONFIG_SYS_MALLOC_LEN?????????? (1024 * 1024)
> since GARDENA has:
> #define CONFIG_SYS_MALLOC_LEN?????????? (16 * 1024 * 1024)
> but I would like a confirmation, if possible.

Its the SPL malloc area, so you need to change a different value:

Please try to increase this value via Kconfig:

CONFIG_SPL_SYS_MALLOC_F_LEN

On GARNEDA its currently this:
CONFIG_SPL_SYS_MALLOC_F_LEN=0x40000

HTH,
Stefan

> TiA!
> 
> full trace: =============================
> U-Boot SPL 2020.04-rc1 (Mar 29 2020 - 17:07:13 +0200)
> Trying to boot from NOR
> 
> 
> U-Boot 2020.04-rc1 (Mar 29 2020 - 17:07:13 +0200)
> 
> CPU:?? MediaTek MT7628A ver:1 eco:2
> Boot:? DDR2, SPI-NOR 3-Byte Addr, CPU clock from XTAL
> Clock: CPU: 580MHz, Bus: 193MHz, XTAL: 40MHz
> DRAM:? 128 MiB
> WDT:?? Started with servicing (60s timeout)
> MMC:?? mmc at 10130000: 0
> Loading Environment from SPI Flash... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
> OK
> In:??? uart2 at e00
> Out:?? uart2 at e00
> Err:?? uart2 at e00
> Model: VoCore2
> Net:
> Warning: eth at 10110000 (eth0) using random MAC address - 8a:c1:c1:2a:28:91
> eth0: eth at 10110000
> Hit any key to stop autoboot:? 0??????????????????????????????????????? <--- booting ok with "mtmips"
> => ls mmc 0:1
>  ?? 179840?? uboot-ram_20170210.bin
>  ?? 179840?? uboot-ram.bin
>  ?? 183272?? uboot-rom_20170213.bin
>  ?? 183272?? uboot-rom_20170423.bin
>  ? 1819846?? uImage.initram
>  ? 1473392?? initram.cpio.xz
>  ? 1819846?? uImage
>  ?? 534530?? u-boot.bin
>  ?12713984?? recov.squashfs
>  ?52983808?? okcash.swu
>  ?? 698880?? persist_data.tar
>  ?????? 97?? net.cfg
>  ? 2360074?? recov.uImage-old
>  ?? 247721?? u-boot-with-spl.bin
>  ?? 244580?? u-boot-mtmips.bin
> 
> 15 file(s), 0 dir(s)
> 
> => load mmc 0:1 80200000 u-boot.bin
> 534530 bytes read in 35 ms (14.6 MiB/s)
> => go ${fileaddr}????????????????????????????????????????????????????? <--- test of raw image (OK)
> ## Starting application at 0x80200000 ...
> 
> 
> U-Boot 2020.10-rc3-00012-g9f04a634ef-dirty (Sep 01 2020 - 09:40:13 +0200)
> 
> CPU:?? MediaTek MT7628A ver:1 eco:2
> Boot:? DDR2, SPI-NOR 3-Byte Addr, CPU clock from XTAL
> Clock: CPU: 580MHz, Bus: 193MHz, XTAL: 40MHz
> DRAM:? 128 MiB
> WDT:?? Started with servicing (60s timeout)
> MMC:?? mmc at 10130000: 0
> Loading Environment from SPIFlash... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
> OK
> In:??? uart2 at e00
> Out:?? uart2 at e00
> Err:?? uart2 at e00
> Model: VoCore2
> Net:
> Warning: eth at 10110000 (eth0) using random MAC address - 7e:fc:d1:78:a2:4e
> eth0: eth at 10110000
> Hit any key to stop autoboot:? 0
> => sf probe
> => load mmc 0:1 85000000 u-boot-with-spl.bin?? <--- use raw image to reflash
> 247721 bytes read in 18 ms (13.1 MiB/s)
> => sf update ${fileaddr} 0 ${filesize}
> device 0 offset 0x0, size 0x3c7a9
> 247721 bytes written, 0 bytes skipped in 2.269s, speed 111648 B/s??? <--- apparently OK
> => reset
> resetting ...
> 
> U-Boot SPL 2020.10-rc3-00012-g9f04a634ef-dirty (Sep 01 2020 - 09:40:13 +0200)
> Trying to boot from NOR
> alloc space exhausted
> Unable to allocate 209398 bytes for LZMA
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
> 
> *** DTR: up ***
>  ??????????????????????????????????????????????????????????????????????????? <--- this is effectively a power-cycle
> *** DTR: down ***
> 
> U-Boot SPL 2020.10-rc3-00012-g9f04a634ef-dirty (Sep 01 2020 - 09:40:13 +0200)
> Trying to boot from NOR
> alloc space exhausted
> Unable to allocate 209398 bytes for LZMA??????? <--- same error
> SPL: failed to boot from all boot devices
> ### ERROR ### Please RESET the board ###
> 
> *** DTR: up ***
> 
> 
> 


Viele Gr??e,
Stefan

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-51 Fax: (+49)-8142-66989-80 Email: sr at denx.de

  reply	other threads:[~2020-09-01 13:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 19:57 from https://gitlab.denx.de/u-boot/custodians/u-boot-mips:f3d8c7f8d3c02ff1de172aff7e6392a9ddd1f5b2 to master: Mauro Condarelli
2020-08-31 20:36 ` Daniel Schwierzeck
2020-08-31 21:53   ` Mauro Condarelli
2020-08-31 23:41     ` Daniel Schwierzeck
2020-09-01 13:09       ` Mauro Condarelli
2020-09-01 13:21         ` Stefan Roese [this message]
2020-09-01 14:01         ` Daniel Schwierzeck
2020-09-01  4:53   ` Stefan Roese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a8e2069c-cde0-671e-e172-3e6aec8bb2ae@denx.de \
    --to=sr@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox