Brute force testing is not a solution unless the testing is very complete and
extensive. Testing is not required for the case of m9dified default
configuration settings. A simple inspection of the Kconf files will detect the
problem in all cases,Sent from my Galaxy
Original message --
Please note that this issue has been fixed:
https://github.com/apache/incubator-nuttx-apps/pull/624
On Sun, Mar 21, 2021 at 6:03 PM Alan Carvalho de Assis
wrote:
>
> Hi Greg and Anthony,
>
> On 3/21/21, Gregory Nutt wrote:
> >
> >> ... what we can
> >> do to prevent these types of "side-effects"
Hi Greg and Anthony,
On 3/21/21, Gregory Nutt wrote:
>
>> ... what we can
>> do to prevent these types of "side-effects" when people are touching the
>> config system.
>
> The use of defconfig files implies that we never change default values
> of configuration. If someone does change the defaul
... what we can
do to prevent these types of "side-effects" when people are touching the
config system.
The use of defconfig files implies that we never change default values
of configuration. If someone does change the default value of a
configuration setting, then it effects ALL configur
Hey Alan,
Can you point to the change? I'm curious how it happened, and what we can
do to prevent these types of "side-effects" when people are touching the
config system.
Best,
Anthony
On Sun, Mar 21, 2021 at 11:22 AM Alan Carvalho de Assis
wrote:
> Hi Flavio,
>
> You need to enable also the
Hi Flavio,
You need to enable also the CONFIG_BCH, some recent modification in
the BCH created this side-effect.
BR,
Alan
On 3/21/21, Flavio Castro Alves Filho wrote:
> Hello,
>
> I am trying to use my stm32f4discovery board with MX25L800 dataflash
> memory, through SPI and SmartFS file system
Hello,
I am trying to use my stm32f4discovery board with MX25L800 dataflash
memory, through SPI and SmartFS file system.
I installed a NuttX driver for this memory type and I am having
problems making this memory work. I cannot format the memory.
Here is the output on the console, with FS Debug
Hello Xiang,
I create the documentation in my fork:
https://github.com/Phi-Innovations/incubator-nuttx/blob/master/Documentation/guides/cpp_cmake.rst
I don't know now to to submit for the main project for revision.
Best regards,
Flavio
Em sex., 19 de mar. de 2021 às 08:38, Flavio Castro Alves
Hello Alan,
In addition to the ID pin, there is another pin, VBUS, which is optional.
In the case of the VBUS pin, it is set on the board.
Similar procedures must be done.
Best regards,
Flavio
Em dom., 21 de mar. de 2021 às 09:35, Alan Carvalho de Assis
escreveu:
>
> Hi Flávio,
>
> I agree,
Hi Flávio,
I agree, this pin is optional and only will be active when OTG is really used.
Maybe a solution should be verifying if the USB Host support is
enabled, since the pin is not required when using as USB Device:
#ifdef CONFIG_USBHOST
stm32_configgpio(GPIO_OTGFS_ID);/* Only needed fo
Hello Allan,
I found the solution.
The PA10 pin has been initialized as a GPIO in USB OTG driver. More
specifically, in file stm32_otgfsdev.c file, line 5602.
I commented this line and everything worked.
This is a solution for me, but it is a problem for the project,
because it is better that t
11 matches
Mail list logo
