Hi Rushikesh,
You need to look the source code example to understand how to control
a single LED.
The userled works as a set of LEDs, so you need to use an IOCTL
command to set a single bit to turn on/off single LED. It is not like
the GPIO that you have a unique device file for each GPIO.
BR,
Hi,
Thank you Alan sir. Now it's working.
Did you enable NSH_ARCHINIT ?
Application Configuration --->
NSH Library --->
[*] Have architecture-specific initialization
Could you please tell me how this nsh library works here?
This built-in leds driver works but it shows binary v
>> present/included? Surprised it's just a warning though.
>>
>> >-Original Message-
>> >From: Alan Carvalho de Assis
>> >Sent: 18 August 2021 12:38
>> >To: dev@nuttx.apache.org
>> >Subject: Re: Creating our own driver in NUCLEO-H743ZI2 wi
Did you enable the LED DEBUG?
Note that "Initializing LEDs" is not printed!
Did you enable NSH_ARCHINIT ?
Application Configuration --->
NSH Library --->
[*] Have architecture-specific initialization
BR,
Alan
On 8/18/21, rushi ghatkar wrote:
> Hi,
>
> I have modified as u ask
ing
> implicitly declared - so no lower driver function is actually
> present/included? Surprised it's just a warning though.
>
> >-Original Message-
> >From: Alan Carvalho de Assis
> >Sent: 18 August 2021 12:38
> >To: dev@nuttx.apache.org
> >Subject
12:38
>To: dev@nuttx.apache.org
>Subject: Re: Creating our own driver in NUCLEO-H743ZI2 with Nuttx rtos
>
>Hi Rushikesh,
>
>Since it is there the /dev/userleds0 should be registered.
>
>Please open your drivers/leds/userled_lower.c and modify it to print some info:
>
>int user
Hi Rushikesh,
Since it is there the /dev/userleds0 should be registered.
Please open your drivers/leds/userled_lower.c and modify it to print some info:
int userled_lower_initialize(FAR const char *devname)
{
int ret;
ledinfo("Initializing LEDs\n");
g_lednum = board_userled_initialize();
"Open your System.map and search for userled_lower_initialize"
On 8/18/21, rushi ghatkar wrote:
> Hi,
>
> @Alan sir, I have enabled the debug option and checked, it still gives the
> same error message in nsh> prompt whenever I run the built-in driver or my
> own driver.
> Please find the attache
The /dev/userleds is created this way:
ret = userled_lower_initialize("/dev/userleds");
Open your System.map and search for userled_lower_initialize, if you
find it, this mean your firmware has it and the issue is probably some
error during the initialization.
*Please* enable the DEBUG LEDS:
Bu
Hi,
How to create * /dev/userleds* ?
I have searched for it but can't find it.
Need Help.
Regards,
Rushikesh Ghatkar
On Mon, Aug 16, 2021 at 6:32 PM Alan Carvalho de Assis
wrote:
> Did you look at /dev? I think the /dev/userleds is not created.
>
> Try to enable the DEBUG LED to see that is
Did you look at /dev? I think the /dev/userleds is not created.
Try to enable the DEBUG LED to see that is going on.
BR,
Alan
On 8/16/21, rushi ghatkar wrote:
> Hi,
>
> I have changed the declaration but it still gives some warning. Please find
> the attached image.
>
> and when I flash code a
You need to declare all LEDs, including GPIO_LED_BLUE
This is the pin on your board used for each LED.
Please look at stm32h747i-disco/src/stm32h747i-disco.h for reference.
BR,
Alan
On 8/16/21, rushi ghatkar wrote:
> Hi Alan sir,
>
> I have disabled the status/diagnostic LEDs compete for the
HI Rushikesh,
It seams your board already has the userleds support:
boards/arm/stm32h7/nucleo-h743zi2/src/stm32_userleds.c
Did you disable the CONFIG_ARCH_LEDS? The status/diagnostic LEDs
compete for the use of LEDs.
So disable it:
Board Selection --->
[ ] Board LED Status support
BR,
A
Hi,
I have tried the built-in LED driver in menuconfig, Application
Configuration -> Examples -> LED driver example.
But when I run that driver using picocom,it shows error,
Builtin Apps:
leds sh hello nsh
nsh> leds
leds_main: Starting the led_daemon
leds_main: led_daemon started
led_d
Hi Alan sir,
Thank you for the clarification.
Regards,
Rushikesh
On Fri, Aug 13, 2021 at 5:34 PM Alan Carvalho de Assis
wrote:
> What do you mean by "try to make driver into app" ?
>
> Drivers need to be created on nuttx/drivers, not at apps/. Also you
> cannot call a driver function direct
What do you mean by "try to make driver into app" ?
Drivers need to be created on nuttx/drivers, not at apps/. Also you
cannot call a driver function directly from apps/, it is a violation
of the OS abstraction.
Your application needs to open the /dev/yourdriver to read/write
from/to your driver.
Hi @Alan & @Frank sir,
I was also thinking the same, first check for the drivers I need and then
copy it and the change as per my needs.
Then change Makefiles, Make.defs, and Kconfigs files to make the driver
include.
Then make them an app to run on picocom.
Will try to change driver as per nee
Am 13.08.2021 um 10:43 schrieb rushi ghatkar:
Hi,
I have configured and installed Nuttx rtos on the Nucleo-H743zi2 board.
Now I want to create my own driver. How to create our own driver?
Has anyone created their own driver using Nuttx rtos on the STM32 board?
Could anybody please tell me how
Hi Rushikesh,
First of all you need to say what driver you want to create.
There are many drivers already available, so I suggest you to start
searching for a driver of a device similar to yours.
If it is a sensor, look at drivers/sensors, if it is a LCD look at
drivers/lcd/, and so on.
Normall
Hi,
Getting confused with where to create a driver, what is Makefile, Kconfig
and Make.defs ?
After creating a driver how to create an app to run that driver?
Regards,
Rushikesh Ghatkar
On Fri, Aug 13, 2021 at 2:13 PM rushi ghatkar
wrote:
> Hi,
>
> I have configured and installed Nuttx rto
Hi,
I have configured and installed Nuttx rtos on the Nucleo-H743zi2 board.
Now I want to create my own driver. How to create our own driver?
Has anyone created their own driver using Nuttx rtos on the STM32 board?
Could anybody please tell me how to start?
Thanks & Regards,
Rushikesh Ghatka
21 matches
Mail list logo
