If you press enter a few time in the serial terminal do you get the nsh>
prompt? There might been some buffer issue. I use screen, but that should
not be a problem.
If this does not work you will likely need to use a debugger like gdb to
see if you are actually getting to the shell.
You can us
- Enable another UART in blue configuration menu, section called Device
drivers
- It will appear in /dev in NSH as ttySX
- Open it in your code and write to it. For examples search in NuttX apps.
It is not documented because it is POSIX.
On Wed, 11 Aug 2021, 04:59 Sathish Touch energy,
wrote:
>
Hi Rushikesh Ghatkar
I think you missed a "-f". The command line should be
*openocd -f interface/stlink-v3.cfg -f target/nucleo-h743zi2.cfg*
I use a command like the one below to to write the nuttx image
* openocd -f interface/stlink.cfg -f target/stm32g4x.cfg -c init -c "reset
halt" -c "flash
Hi Rushikesh,
Yes, seams like the NuttX was initialized correctly.
There are some possible reason why you are not seem the NSH terminal:
- Are you sure that /dev/ttyACM0 is from you board (case there are
other board or USB modem on your computer, please remove it)
- Maybe the STLink in the boar
Hi Sathish,
Currently on s32k144evb the UART1 is used by the NSH, then you will
not be example to use it directly if you want to stay with the NSH,
but if you write your own application and remove the NSH from the
USER_ENTRYPOINT you could use it.
Why don't use you use UART0 and UART2? This way y
Hi Alan Sir,
Thanks for your help.
Here is answer,
- Are you sure that /dev/ttyACM0 is from you board (case there are
other board or USB modem on your computer, please remove it)
*Answer: *Yes sir. I have checked it.
- Maybe the STLink in the board is not connected to the right pins of
the USART
Dear all,
since yesterday's upstream fetch, my custom board is not working any more.
Basically it is a copy of same70_explained:nsh ...
ADC, CAN, ETHERNET is not any more in /dev/
nsh is prompting fine...
board_app_initialize() is not called any more.
I think it has something to do with the fo
On Wed, Aug 11, 2021 at 8:28 AM Simon Filgis
wrote:
> Dear all,
>
> since yesterday's upstream fetch, my custom board is not working any more.
>
> Basically it is a copy of same70_explained:nsh ...
>
> ADC, CAN, ETHERNET is not any more in /dev/
> nsh is prompting fine...
>
> board_app_initialize
Hi Daniel,
Thanks sir. Sure I will try this openocd command.
Regards,
Rushikesh Ghatkar
On Wed, Aug 11, 2021 at 5:13 PM Daniel Pereira Carvalho
wrote:
> Hi Rushikesh Ghatkar
>
> I think you missed a "-f". The command line should be
>
> *openocd -f interface/stlink-v3.cfg -f target/nucleo-h743
On Wed, Aug 11, 2021 at 8:32 AM Nathan Hartman
wrote:
> On Wed, Aug 11, 2021 at 8:28 AM Simon Filgis <
> si...@ingenieurbuero-filgis.de> wrote:
>
>> Dear all,
>>
>> since yesterday's upstream fetch, my custom board is not working any more.
>>
>> Basically it is a copy of same70_explained:nsh ...
Hi Rushikesh,
Congratulations!!!
What was the issue?
BR,
Alan
On 8/11/21, rushi ghatkar wrote:
> Hi @Brennan @Alan Sir,
>
> I have tried to install and configure NUttx RTOS and completed
> successfully.
> Both* nuttx.bin* and *nuttx.hex* files have been created.
>
> Now Picocom is also workin
Thanks a lot for the quick response..
On Wed, 11 Aug 2021 at 13:43, Maciej Wójcik wrote:
> - Enable another UART in blue configuration menu, section called Device
> drivers
> - It will appear in /dev in NSH as ttySX
> - Open it in your code and write to it. For examples search in NuttX apps.
> I
Thanks a lot for the quick response, Alan..
On Wed, 11 Aug 2021 at 17:28, Alan Carvalho de Assis
wrote:
> Hi Sathish,
>
> Currently on s32k144evb the UART1 is used by the NSH, then you will
> not be example to use it directly if you want to stay with the NSH,
> but if you write your own applicat
Hi Nathan,
You mean this option?
[image: image.png]
Makes no difference.
I checked all the points in the list of cwiki. I did not miss a single line.
I have attached my board's Kconfig and defconfig file, could you please
have a look?
Simon
On Wed, Aug 11, 2021 at 3:03 PM Nathan Hartman
wr
Please check your board/_path_/src/Makefile and check that your
CONFIG_ are all in the new format, i.e.: CONFIG_LIB_BOARDCTL to
CONFIG_BOARDCTL
On Wed, Aug 11, 2021 at 3:56 PM Simon Filgis
wrote:
>
> Hi Nathan,
>
> You mean this option?
>
>
> Makes no difference.
>
> I checked all the points in
That is done:
[image: image.png]
Any other ideas?
By the way: is it OK to double include sam_bringup.c in line 30 and 35?
I will go back to an older state for verification of the assumptions.
Simon
On Wed, Aug 11, 2021 at 3:59 PM Abdelatif Guettouche <
abdelatif.guettou...@gmail.com> wrote:
Hi Simon,
It is not included twice, see now with indentation:
ifeq ($(CONFIG_BOARDCTL),y)
CSRCS += sam_appinit.c sam_bringup.c
ifeq ($(CONFIG_BOARDCTL_RESET),y)
CSRCS += sam_reset.c
endif
else ifeq ($(CONFIG_BOARD_LATE_INITIALIZE),y)
CSRCS += sam_bringup.c
endif
BR,
Alan
On 8/11/2
Dear all,
OK.
nuttx -> master
apps -> something old
after pulling apps the problem is solved. I realized this when looking at
several new warnings, that are also gone now.
Thanks for the awesome support :)
Simon
On Wed, Aug 11, 2021 at 4:51 PM Alan Carvalho de Assis
wrote:
> Hi Simon,
>
>
18 matches
Mail list logo
