On Mon, Sep 18, 2023 at 7:01 AM Lee, Lup Yuen wrote:
> Here's what Ken and I have tried for the riscv64 libm linking problem:
>
> (1) The recommended toolchain for NuttX on riscv64 is SiFive Freedom Tools.
> But it doesn't support Raspberry Pi OS (64-bit Debian).
>
> (2) So we used Debian gcc-ris
On Mon, Sep 18, 2023 at 4:16 AM wrote:
> On 2023-09-17 12:47, Petro Karashchenko wrote:
> > Hi,
> >
> > What kind of RISC-V toolchain are you using?
>
> Raspian:RasPi4:~/RISCV/NuttX/apps >>> apt search riscv64-unknown
> Sorting... Done
> Full Text Search... Done
> binutils-riscv64-unknown-elf/old
Here's what Ken and I have tried for the riscv64 libm linking problem:
(1) The recommended toolchain for NuttX on riscv64 is SiFive Freedom Tools.
But it doesn't support Raspberry Pi OS (64-bit Debian).
(2) So we used Debian gcc-riscv64-unknown-elf instead. Which shows the
missing libm error that
On 2023-09-17 12:47, Petro Karashchenko wrote:
Hi,
What kind of RISC-V toolchain are you using?
Raspian:RasPi4:~/RISCV/NuttX/apps >>> apt search riscv64-unknown
Sorting... Done
Full Text Search... Done
binutils-riscv64-unknown-elf/oldstable,now 2.32.2020.04+dfsg-2 arm64
[installed]
GNU ass
Since C++ most likely will never be used in the kernel I see that
compatibility border should stay in the "include" folder in nuttx repo. The
nuttx-apps headers should be C++ compatible as we can mix things at
application level.
Hi,
What kind of RISC-V toolchain are you using? I recall that the RISC-V
toolchain provided by Ubuntu is built without libm support. Also I noticed
that you have "CFLAGS += -lm " in Make.defs and with CONFIG_LIBM=y that
should be removed I think as you try to rebuild math from NuttX sources.
Ple
Please forgive the noob question.
I am porting a Scheme interpreter to riscv64 NuttX as
apps/interpreters/umb-scheme/ but the binary fails to link in libm
functions.
I could use some help in this.
Specifically, building on Raspberry Pi 4 Raspian 64 bit:
Raspian:RasPi4:~/RISCV/NuttX/apps/bin
Hi,
That part of the documentation looks like it is specific to esp32 only
(not esp32s or esp32c). This info applies to all the esp32 variants (s,
c, h, etc). That's why I was wondering where this should end up...
There doesn't seem to be a place for esp32 non-variant-specific
documentatio
On Sun, Sep 17, 2023 at 2:18 PM Mike Moretti wrote:
> (..)
> I would like to contribute documentation for this. Where, where would
> this documentation belong? This is definitely not specific to esp32s3
> (but applies to all esp32 variants) and I don't even know if it's
> specific to esp32? Is t
Hi,
I found some info in the NuttX bootloader readme in the github repo.
Apparently the default non-mcuboot partition table is setup as one 1M
partition. This is why my build was failing to boot (as it was 1.5M).
I was able to modify the partition size through sheer luck, as nothing
is doc
10 matches
Mail list logo
