The address 0x80008000 was used in pre-K3 devices. ARM64 requires the
kernel loaded to a 2MB aligned address when not using KASLR. For FIT
set the address to 0x8100 which gives the kernel 32MB before running
into the FDT at 0x8300.
If you get this error someday then your kernel is too
New features added require another increase to max_leb_cnt.
Signed-off-by: Ryan Eatmon
---
meta-ti-bsp/conf/machine/am335x-evm.conf | 2 +-
meta-ti-bsp/conf/machine/am437x-evm.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-ti-bsp/conf/machine/am335x-evm.conf
Are there any plans to convert this to a prebuilt firmware binary hosted at
ti-linux-firmware, like was done to many other firmwares in meta-ti?
On Wed, Jul 05, 2023 at 09:09:06PM +, Nick Saulnier via
lists.yoctoproject.org wrote:
> No top-level build errors observed with the updated PSSP
No top-level build errors observed with the updated PSSP commits. Thanks
Praneeth!
-Nick
-Original Message-
From: Bajjuri, Praneeth
Sent: Wednesday, July 05, 2023 4:07 PM
To: Bajjuri, Praneeth ; Eatmon, Ryan ;
Saulnier, Nick ; Nagalla, Hari
Cc: meta-ti@lists.yoctoproject.org
Subject:
From: Praneeth Bajjuri
Upgrade to v6.2.0 version.
This release supports Linux kernel 6.1.
The RPMsg library in previous versions of the PSSP will not work with
the PRU RPMsg drivers in Linux kernel 6.1.
Other changes in this version:
* Bug fixes:
- Getting Started Labs, fix "zero" command
The address 0x80008000 was used in pre-K3 devices. ARM64 requires the
kernel loaded to a 2MB aligned address when not using KASLR. For non-FIT
we use 0x8200, let's use the same when loading from FIT.
Signed-off-by: Andrew Davis
---
meta-ti-bsp/conf/machine/include/k3.inc | 4 ++--
1 file
This patch fails to build:
Building file: pru_adc_firmware.c
Invoking: PRU Compiler
/scratch/jenkins_builds/arago-kirkstone-next/build/build/arago-tmp-default-glibc/work/am57xx_evm-oe-linux-gnueabi/pru-icss/6.2.0-r1/recipe-sysroot-native/usr/share/ti/cgt-pru/bin/clpru
Today the SDK for AM335x/AM437x loads kernel/dtb from the boot partition, but
all K3 devices load kernel/dtb from the root partition. This inconsistency
confuses customers.
Is it possible to locate 'extlinux.conf' on boot partition with kernel/dtb on
root partition ?
This old link explains
Just for your information there are more complaints about that issue [1] of
some bad side effects of sharing the TMP folder in multi configs.
[1] https://lists.openembedded.org/g/bitbake-devel/message/14860
Jose
Ricardo Salveti escreveu no dia segunda, 30/01/2023
à(s) 18:27:
> On Mon, Jan 30,
