A few weeks ago I moved my custom board out of the NuttX
"nuttx/nuttx/boards" tree to a folder "nuttx/CustomBoards".
Make menuconfig allows you to specify that folder
(CONFIG_ARCH_BOARD_CUSTOM_DIR=)
To try and rule out .config errors for some issues I have at the moment I
did a make distcl
A recent change (e8f4d74ad0c33389c1094c3ca6c10a6336d8fbe7) moved the
individual rp2040_spi.c into the common directory.
How can a board with different chip select GPIO usage have a board
specific setup?
I don't see a way to disable the common implementation.
--
B.Walter https://www.bwct.de
Modbu
There is an option for relative links. The you can pass the path to
configure.sh
Like configure.sh ../boards/custom-board/config/nsh
On Thu, Sep 15, 2022 at 12:25 PM TimH wrote:
> A few weeks ago I moved my custom board out of the NuttX
> "nuttx/nuttx/boards" tree to a folder "nuttx/CustomBoards
Thank you! I was trying to run it like this:
./tools/configure.sh -l ../CustomBoards/board-name:config-name
Perhaps this needs to be added to the configure.sh help text?
>-Original Message-
>From: Abdelatif Guettouche
>Sent: 15 September 2022 11:59
>To: dev@nuttx.apache.org
>Subject: Re
Thanks Greg - knowing that -1 is not error means I'm not wasting time
investigating that, at least!
The problem is unrelated to the touchscreen and more an RTOS/NuttX
configuration error I think - the ADC example app will run once quite happily,
with either 1 sample or 0 (i.e. run forever) - bu
This is not about nuttx, but about this list.
Just a few minutes ago I had send a mail to this list.
The returned mail from the list was tagged as spam.
It wasn't enough to reject the mail, but tag it, so that it was filed
into the spam folder.
The major reason (rspamd default config) was 7 points
Hi Bernd,
Yes, I think the current implementation is fixed to allow only 1 CS
per RP2040 SPI.
That is not ideal (read: "incorrect").
It is possible to have the rp2040_spi.c as a common boards file, but
the CS should be extended, i.e.:
#if defined(LCDxyz) || defined(LCDwku) ...
rp2040_gpio_put
Actually you can include support for multiple devices of same type in
the same SPI bus:
#if defined(LCDxyz) || defined(LCDwku) ...
switch (devid)
{
case SPIDEV_DISPLAY(0):
/* Set the GPIO low to select and high to de-select */
rp2040_gpio_put(BOARD_RP2040_SPI0_DISPLAY_CS0, !
I have sorted the touchscreen on the SAMA5D2 - minor errors in the init code
"as supplied" meaning a couple of registers were not set up right.
I have also found that priority inheritance is needed, at least for the ADC
example app: I've not sat back or read my books to see why, but it works fo
On Thu, Sep 15, 2022 at 09:48:42AM -0300, Alan Carvalho de Assis wrote:
> Actually you can include support for multiple devices of same type in
> the same SPI bus:
>
> #if defined(LCDxyz) || defined(LCDwku) ...
> switch (devid)
> {
> case SPIDEV_DISPLAY(0):
> /* Set the GPIO low to
Hi,
> The easy option is to comment out the two calls, but I don't know if that'
s
> deemed acceptable, especially as other adc drivers do the same?
I do not think this is correct since it is better to disable and detach the
interrupt
when we close the device.
Instead I think the the e
Makes sense! I searched other drivers for where they called the detach but
didn't think to see where those other drivers called the attach!
Thanks :)
>-Original Message-
>From: Michal Lenc
>Subject: Re: ADC device close and IRQ
>
>Hi,
>
>> The easy option is to comment out the two calls
On Thu, Sep 15, 2022 at 7:06 AM TimH wrote:
> Perhaps this needs to be added to the configure.sh help text?
I agree!
See PR-7103:
https://github.com/apache/incubator-nuttx/pull/7103
Help with reviewing that will be appreciated!
Nathan
Hi Prelude,
The W5500 initialization code is already merged into mainline:
https://github.com/apache/incubator-nuttx/blob/master/boards/arm/stm32/stm32f4discovery/src/stm32_w5500.c
Did you have the chance to test it?
BR,
Alan
On 9/14/22, Alan Carvalho de Assis wrote:
> Hi Prelude and Michael
14 matches
Mail list logo
