Hi Florian,
Does this problem only occur in version 9.0.0?
Or is it happening to the current master as well?
Are you following this tutorial: https://www.youtube.com/watch?v=oL6KAgkTb8M
Also you can increase the debug level (include warn and info).
BR,
Alan
On 5/16/20, Florian Wehmeyer wrote
However, got a new problem now which I've not figured out yet:
The binary loader does not load the elf if the program is a built-in
app... very strange..
It does not even try to load the elf file from file-system, it directly
goes to the built-in app.
That means that it failed to load the app
FYI it was just approved.
https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-182
--Brennan
On Wed, May 13, 2020, 7:26 AM Nathan Hartman
wrote:
> On Wed, May 13, 2020 at 12:54 AM Brennan Ashton >
> wrote:
>
> > I created the ticket
> > https://issues.apache.org/jira/browse/PODLINGNAMESEAR
Hi Greg and Alan,
> > It does not even try to load the elf file from file-system, it
> > directly
> > goes to the built-in app.
> That means that it failed to load the app on the file system. It
> should
> check in this order"
>
> - Load file from file system if possible
>
> - If not, run bu
Mystery solved.
It does not even try to load the elf file from file-system, it
directly
goes to the built-in app.
That means that it failed to load the app on the file system. It
should
check in this order"
- Load file from file system if possible
- If not, run built-in application if possibl
I just created incubator-nuttx-apps PR 255 that should restore the
correct behavior: https://github.com/apache/incubator-nuttx-apps/pull/255
On 5/17/2020 3:33 PM, Gregory Nutt wrote:
Mystery solved.
It does not even try to load the elf file from file-system, it
directly
goes to the built-in ap
On Sun, May 17, 2020 at 2:46 PM Brennan Ashton
wrote:
> FYI it was just approved.
>
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-182
Thanks for taking care of that!
Nathan
I just created incubator-nuttx-apps PR 255 that should restore the
correct behavior: https://github.com/apache/incubator-nuttx-apps/pull/255
This is a major bug and, if we release do a bugfix release sometime,
this should be included.
On Sun, May 17, 2020, 3:50 PM Gregory Nutt wrote:
>
> > I just created incubator-nuttx-apps PR 255 that should restore the
> > correct behavior:
> https://github.com/apache/incubator-nuttx-apps/pull/255
>
> This is a major bug and, if we release do a bugfix release sometime,
> this should be incl
Hi, Brennan,
I just created incubator-nuttx-apps PR 255 that should restore the
correct behavior:
https://github.com/apache/incubator-nuttx-apps/pull/255
This is a major bug and, if we release do a bugfix release sometime,
this should be included.
I was thinking the same. I created a label ba
On Sun, May 17, 2020, 3:59 PM Gregory Nutt wrote:
> Hi, Brennan,
> >>> I just created incubator-nuttx-apps PR 255 that should restore the
> >>> correct behavior:
> >> https://github.com/apache/incubator-nuttx-apps/pull/255
> >>
> >> This is a major bug and, if we release do a bugfix release somet
On Sun, May 17, 2020 at 7:11 PM Brennan Ashton
wrote:
> On Sun, May 17, 2020, 3:59 PM Gregory Nutt wrote:
>
> > Hi, Brennan,
> > >>> I just created incubator-nuttx-apps PR 255 that should restore the
> > >>> correct behavior:
> > >> https://github.com/apache/incubator-nuttx-apps/pull/255
> > >>
I have no preference. At some point, I think we also have to say that
9.0.x "is what it is". Or do you see us continuing to maintain the
release forever? In the dark, pre-Apache past, I had about a two week
period after the release after which it "is what it is". I distrubuted
patches up un
hi,
this is just a curious question.
why do we use the name "intel64" for qemu things?
i thought it was from qemu, but qemu seems to use x86_64 or amd64.
i think "amd64" is more commonly used as it's from amd.
do we want to help intel marketing for some reasons?
On Sun, May 17, 2020, 10:36 PM Takashi Yamamoto
wrote:
> hi,
>
> this is just a curious question.
> why do we use the name "intel64" for qemu things?
> i thought it was from qemu, but qemu seems to use x86_64 or amd64.
> i think "amd64" is more commonly used as it's from amd.
> do we want to help
Hi Greg,
About the break commit:
commit 9a28ccf836c1b9f0eb5e1163964042eddc207697
Author: chao.an
Date: Fri Feb 21 09:54:47 2020 +0800
nsh/parse: try the builtin configuration first
In the case of enable the BUILTIN_APPS/FILE_APPS at the same
time, try t
16 matches
Mail list logo
