Podling Nuttx Report Reminder - October 2020
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 21 October 2020. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, October 07). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/October2020 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Podling Nuttx Report Reminder - October 2021
Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 October 2021. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, October 06). Please submit your report with sufficient time to allow the Incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Candidate names should not be made public before people are actually elected, so please do not include the names of potential committers or PPMC members in your report. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. * How does the podling rate their own maturity. This should be appended to the Incubator Wiki page at: https://cwiki.apache.org/confluence/display/INCUBATOR/October2021 Note: This is manually populated. You may need to wait a little before this page is created from a template. Note: The format of the report has changed to use markdown. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC
Re: Making driver example as a application entry point
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 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 >
