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 application (see apps/examples/hello) and call your application_main in the entry point. But reading it again it seams like you are just calling your application as driver, because you refers to depath failing :-) Probably your driver is not initialized because when your call the Application entry point the NSH will not run and then the driver will not be initialized by the NSH ARCH Init. Try to enable the CONFIG_BOARD_LATE_INITIALIZE in the RTOS Features -> RTOS hooks. BR, Alan On 9/20/21, rushi ghatkar <rushighatka...@gmail.com> 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 >
