Re: Making driver example as a application entry point

2021-09-27 Thread rushi ghatkar
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

Re: Making driver example as a application entry point

2021-09-27 Thread rushi ghatkar
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 Fea

Re: Making driver example as a application entry point

2021-09-25 Thread murat tologlu
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 prob

Re: Making driver example as a application entry point

2021-09-20 Thread Alan Carvalho de Assis
Hi Rushi, Could you please explain exactly what are you trying to do? First of all you are not suppose to call your "driver" directly. Although maybe it will work on FLAT mode, it violates the kernel/userspace isolation and it will not work on PROTECTED and KERNEL modes. You should create an app

Making driver example as a application entry point

2021-09-19 Thread rushi ghatkar
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 sche