Hi Brennan,
I think that we should backport them and I will cut RC1
Thanks
Alin
On Thu, Apr 22, 2021, 08:30 Brennan Ashton
wrote:
> Alin,
> I think we should consider if we want to backport these into the
> 10.1.0 release. I am still running more tests myself on all the
> hardware I have, but
Alin,
I think we should consider if we want to backport these into the
10.1.0 release. I am still running more tests myself on all the
hardware I have, but these seemed important to at least consider.
https://github.com/apache/incubator-nuttx/pull/3586
https://github.com/apache/incubator-nuttx/pul
On Wed, Apr 21, 2021 at 5:59 PM Masayuki Ishikawa
wrote:
>
> Hi, Brennan
>
> Sorry to reply to the old email but I noticed that the following tags are
> missing in the github repositories.
>
> https://github.com/apache/incubator-nuttx/
> nuttx-9.1.1
>
> https://github.com/apache/incubator-nuttx-a
Hi, Brennan
Sorry to reply to the old email but I noticed that the following tags are
missing in the github repositories.
https://github.com/apache/incubator-nuttx/
nuttx-9.1.1
https://github.com/apache/incubator-nuttx-apps/
nuttx-9.1.1
nuttx-10.0.1
Could you please add the above tags to the re
It worked.
Just changing the linker script was enough.
Thank you very much.
Best regards,
Flavio
Em qua., 21 de abr. de 2021 às 16:00, Gregory Nutt
escreveu:
>
>
> > But I don't know if there is anything to be done directly in NuttX source
> > code.
>
> Nothing other than setting the VBAR re
But I don't know if there is anything to be done directly in NuttX source code.
Nothing other than setting the VBAR register (called NVIC_VECTAB in
NuttX). This is already done so I guess the real answer is No.
Hello,
To have usbnsh working I used, as a workaround, the implementation
done in this pull request:
https://github.com/apache/incubator-nuttx-apps/pull/521
In my application I don't use nsh. And USB-CDC works fine accessing
directly the device.
Hope it helps,
Best regards,
Flavio
Em ter., 20
Hello,
I intend to use a NuttX firmware with a custom bootloader on a
STM32F4DISCOVERY board.
The bootloader will be executed on the first available memory block in
flash, and the firmware will start from the second block - position
0x0802.
I believe I know what to do regarding linker script
Thank you very much for your explanation. I didn't check irq_attach() in
depth and didn't discover what you mention
I've found
https://cwiki.apache.org/confluence/display/NUTTX/High+Performance%2C+Zero+Latency+Interrupts.
It seems a good start for that subject
El mié, 21 abr 2021 a las 9:30, Nat
On Wed, Apr 21, 2021 at 9:03 AM Grr wrote:
>
> Hello to all.
>
> I was studying EXTI handling in STM32 and noticed irq handlers (as defined
> in stm32_exti_gpio.c) have three parameters: irq, context and arg.
>
> And they are never used
>
> If handlers are looked up in the vector table, which only
On Wed, Apr 21, 2021 at 9:04 AM Tim wrote:
> I am in need of a driver for an FUSB301 USB C Controller/PD device. I see
> there are drivers for the FUSB301 and FUSB303 but not the FUSB302.
>
>
>
> Before I have a stab at porting the outline code I already have for this
> device, and finishing it o
I am in need of a driver for an FUSB301 USB C Controller/PD device. I see
there are drivers for the FUSB301 and FUSB303 but not the FUSB302.
Before I have a stab at porting the outline code I already have for this
device, and finishing it off to become a "proper" NuttX driver (and
potentially m
Hello to all.
I was studying EXTI handling in STM32 and noticed irq handlers (as defined
in stm32_exti_gpio.c) have three parameters: irq, context and arg.
And they are never used
If handlers are looked up in the vector table, which only have handler's
address, where do these parameters (special
Wow! I am very glad to see that you are so involved in this subject. I have to
be worthy of your attention.
Firstly, let me explain what I am thinking about Hasseb USB-Dali Master
device. You can consider it in place of the USB-RS485 Converter in Nuttx Modbus
tutorial ( http://ta1db.5g.com.tr/
14 matches
Mail list logo
