Hi, And when I tried built-in example app "leds" , to make as an entry point, it gives error,* led_daemon: ERROR: Failed to open /dev/userleds: 2*
So for a built -in app example, could you please tell me what is wrong? Regards, Rushikesh Ghatkar On Tue, Sep 28, 2021 at 10:38 AM rushi ghatkar <rushighatka...@gmail.com> wrote: > Hi, > > Actually I have created my own gpio driver and created an app too. > When I run the app using picocom, it works fine. > > But when I create an application as an entry point using *RTOS features > ---> Task and scheduling ---> Application entry point *and > *CONFIG_BOARD_LATE_INITIALIZE > in the RTOS Features -->RTOS hooks, *it does* not work*. > > Could you please tell me what is wrong? > > > > Regards, > Rushikesh Ghatkar > > On Sat, Sep 25, 2021 at 7:33 PM murat tologlu <mtolo...@hotmail.com> > wrote: > >> Hi Rushi, >> Which “driver example” are you talking abaut? >> >> On 2021/09/20 06:51:42 rushi ghatkar wrote: >> > Hi, >> > >> > I have created drivers and when I'm trying to make them as an entry >> point. >> > I am facing the issue while making them as an entry point as soon as my >> > board gets powered up. >> > >> > The problems I'm facing mentioned below, >> > 1. When I am configuring *built-in example * in *RTOS features ---> >> Task >> > and scheduling ---> Application entry point, *when I do this, it fails >> to >> > open the devpath. >> > >> > 2. When I am using my own driver example to configure as an entry >> > point in *RTOS >> > features ---> Task and scheduling ---> Application entry point, *it does >> > not run as expected. >> > But when *using picocom it works fine* and as I have programmed it* >> without >> > configuring it to the application entry point*. >> > >> > >> > Is there any other better way to make it work? >> > >> > >> > >> > Regards, >> > Rushikesh Ghatkar >> > >> >
