From: Chirag Shilwant <c-shilwant@ti.com>
To: Ryan Eatmon <reatmon@ti.com>
Cc: Sai Sree Kartheek Adivi <s-adivi@ti.com>,
Paresh Bhagat <p-bhagat@ti.com>, Gyan Gupta <g-gupta@ti.com>,
Denys Dmytriyenko <denis@denix.org>,
<meta-ti@lists.yoctoproject.org>
Subject: Re: [EXTERNAL] [meta-ti][master/scarthgap][PATCH] conf: am437x-evm: Bump up max_leb_cnt
Date: Mon, 13 May 2024 12:49:25 +0530 [thread overview]
Message-ID: <388e7b5a-3b1a-4485-a0df-8a601f591bfb@ti.com> (raw)
In-Reply-To: <17CCCB990A8CA32A.20378@lists.yoctoproject.org>
Hi Ryan,
Looks like this patch got missed out as I can't see it applied on
meta-ti master/scarthgap.
With latest scarthgap based processor-sdk builds, we need this bump up
for am437x-evm.
Errors we observe,
| DEBUG: Python function extend_recipe_sysroot finished
| DEBUG: Executing python function set_image_size
| DEBUG: 6281641.600000 = 4832032 * 1.300000
| DEBUG: 6281641.600000 = max(6281641.600000, 65536)[6281641.600000] + 0
| DEBUG: 6281642.000000 = int(6281641.600000)
| DEBUG: 6281642 = aligned(6281642)
| DEBUG: returning 6281642
| DEBUG: Python function set_image_size finished
| DEBUG: Executing shell function do_image_ubifs
| Error: max_leb_cnt too low (6018 needed)
On 06/05/24 09:53, Chirag Shilwant via lists.yoctoproject.org wrote:
> New features added require another increase to max_leb_cnt.
> Signed-off-by: Chirag Shilwant <c-shilwant@ ti. com> ---
> meta-ti-bsp/conf/machine/am437x-evm. conf | 2 +- 1 file changed, 1
> insertion(+), 1 deletion(-) diff --git
> a/meta-ti-bsp/conf/machine/am437x-evm. conf
> ZjQcmQRYFpfptBannerStart
> This message was sent from outside of Texas Instruments.
> Do not click links or open attachments unless you recognize the source
> of this email and know the content is safe. If you wish to report this
> message to IT Security, please forward the message as an attachment to
> phishing@list.ti.com
> ZjQcmQRYFpfptBannerEnd
> New features added require another increase to max_leb_cnt.
>
> Signed-off-by: Chirag Shilwant <c-shilwant@ti.com>
> ---
> meta-ti-bsp/conf/machine/am437x-evm.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta-ti-bsp/conf/machine/am437x-evm.conf b/meta-ti-bsp/conf/machine/am437x-evm.conf
> index 58b7996f..248add70 100644
> --- a/meta-ti-bsp/conf/machine/am437x-evm.conf
> +++ b/meta-ti-bsp/conf/machine/am437x-evm.conf
> @@ -21,7 +21,7 @@ SERIAL_CONSOLES = "115200;ttyS0"
> # UBI: logical eraseblock size: 253952 bytes
> # from ubiattach stdout:
> # UBI device number 0, total 994 LEBs
> -MKUBIFS_ARGS = "-F -m 4096 -e 253952 -c 6000"
> +MKUBIFS_ARGS = "-F -m 4096 -e 253952 -c 8000"
>
> # do ubiattach /dev/ubi_ctrl -m 11 -O 4096
> # from dmesg:
> --
> 2.34.1
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#17642): https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-ti/message/17642__;!!G3vK!QyV6c3884c4ajGLpKPNQPDSvXJeDU0P8_-TI1nuulPjWsafppz6T8JyZyRDfGvgrzGALzaFFFvH48vf5WtOBfbUA8ByEWxsrBxKi$
> Mute This Topic: https://urldefense.com/v3/__https://lists.yoctoproject.org/mt/105934386/7030289__;!!G3vK!QyV6c3884c4ajGLpKPNQPDSvXJeDU0P8_-TI1nuulPjWsafppz6T8JyZyRDfGvgrzGALzaFFFvH48vf5WtOBfbUA8ByEW3V5XAzx$
> Group Owner: meta-ti+owner@lists.yoctoproject.org
> Unsubscribe: https://urldefense.com/v3/__https://lists.yoctoproject.org/g/meta-ti/unsub__;!!G3vK!QyV6c3884c4ajGLpKPNQPDSvXJeDU0P8_-TI1nuulPjWsafppz6T8JyZyRDfGvgrzGALzaFFFvH48vf5WtOBfbUA8ByEW_5UTeUl$ [c-shilwant@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
parent reply other threads:[~2024-05-13 7:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <17CCCB990A8CA32A.20378@lists.yoctoproject.org>]
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=388e7b5a-3b1a-4485-a0df-8a601f591bfb@ti.com \
--to=c-shilwant@ti.com \
--cc=denis@denix.org \
--cc=g-gupta@ti.com \
--cc=meta-ti@lists.yoctoproject.org \
--cc=p-bhagat@ti.com \
--cc=reatmon@ti.com \
--cc=s-adivi@ti.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).