We are working on porting QNX to a custom ARM Cortex A7 board. We are facing trouble while launching the serial driver through the build script.In the build script we launch the driver with the following commanddevc-pl011Uart -e -S -F -b115200 -c51200000 -u3 0x50020000,59waitfor /dev/ser3reopen /dev/ser3display_msg Reopen doneThe reopen command succeeds and we get the display print on console.There after the shell hangs indefinitely and does not execute any shell commands correctly.We observe from JTAG debugger that we consistently get Receive interrupts whenever we input something from the host and the input is processed by ttyto be echoed back on console. However the given input is not processed by the shell.
qnx 6.6 include ssh-keygen in to build script
Thanks for your help the change from ksh to esh helped us progress.If we change the shell to esh i get the shell prompt.I made the following change to my build script.[+session] PATH=/proc/boot esh &
I was able to resolve the issue of slow command response to shell commands.The issue was in my tto function where the exit condition for transmission of characters was incorrect.With this fix we are able to launch the shell and execute commands by launching esh from the build script.Some small issues still exist like for instance the TAB command does not work.
For developing software, you don't always have to use the command line;the QNX Momentics Professional Edition includes an Integrated DevelopmentEnvironment (IDE) that provides a graphical way to write, build, and test code.The IDE frequently uses Neutrino utilities,but "hides" the command line from you.For more information, see the IDEUser's Guide.
When the system starts devc-con, it canspecify how many virtual consoles to enableby specifying the -n.In a desktop system, the buildfile specifies four consoles when it startsdiskboot.For more information, see the description ofdiskbootin the Controlling How Neutrino Starts chapter.The maximum number of virtual consoles is nine.The tiny console driver,devc-tcon,supports only one console.
Theres some #ifdef logic which allows overriding this definition, but only as a parameter to the configure script at build time. No run time configuration of where to look for login is possible. When I then checked, sure enough, for this project the QNX filesystem had been populated with login under /bin/ not /usr/bin/. 2ff7e9595c
Comments