hi, How can I want to use console line on serial line. When I debugging, it is not convenient without command line on serial line.
thanks
-------- Forwarding messages -------- From: longjks <longjks@...176...> Date: 2013-04-17 19:06:21 To: "Genode OS Framework Mailing List" genode-main@lists.sourceforge.net Subject: How to get l4android log on android_term?
hi, last mail, Stefan said
By removing the log_term in l4android, I can see the log appear on serial line. How can I make the log on android_term appear on serial line? When I debugging, it is not convenient to use android_term. thanks. longjks
Hi,
On 05/02/2013 03:38 PM, longjks wrote:
if you want to use the serial line as terminal interface, and not for logging purposes, or to interact with the kernel debugger only, there exist two possibilities.
The first most convenient one is to enable a second UART interface of the Pandaboard (via its expansion connectors), and use the Genode's UART driver for the Pandaboard, which provides a UART session. A UART session in Genode is derived from the terminal session type, therefore you can directly connect e.g. the l4android process to use that UART driver as its terminal.
If you don't want or aren't able to use a second UART interface, another approach would be to use the Fiasco.OC specific UART driver that simply connects to the Fiasco.OC kernel debugger. It can be found under: 'os/src/drivers/uart/kdb'.
The drawback of the latter approach is, that your terminal sessions might get polluted by logging messages of Genode's core process, and the Fiasco.OC kernel.
Another component that might be of interest for you is the terminal multiplexer. In combination with the terminal multiplexer service ('gems/src/server/terminal_mux') you can use one and the same terminal session (e.g.: a UART line) in combination with several terminal clients. An run script example that combines the terminal multiplexer, and the UART kdb driver can be found in 'gems/run/terminal_mux.run'.
Regards Stefan
Hi,At 2013-05-06 16:18:59,"Stefan Kalkowski" <stefan.kalkowski@...1...> wrote:
like Stefan said, I have used the seconde method using the Fiasco.OC specific UART driver under 'os/src/drivers/uart/kdb'. I added this to my run script: <start name="uart_drv"> <binary name="kdb_uart_drv"/> <resource name="RAM" quantum="1M"/> <provides> <service name="Uart"/> <service name="Terminal"/> </provides> <config> <policy label="terminal_mux" uart="1" detect_size="yes"/> <policy label="noux" uart="1" detect_size="yes"/> </config> <route> <any-service> <parent/> </any-service> </route> </start> then, I can use console line on seria line. However, there are some problem in my console line. You can see the problem pictures in attachment. One is that When I enter one character, it will write this character twice. For example, if I enter one 'a' in the console line, it will appear 'aa' in the screen. but the fiasco kernel get the right one 'a'. The other problem is that when i enter another path using the command 'cd ', the path can not appear int the front of console line. You can not know what path you are. thanks.
Hi,
On 05/14/2013 04:21 PM, longjks wrote:
Without having your complete run-script, it's just guessing: One problem to me seems your configuration of the KDB uart driver. Why do you define two different clients, and why do they use uart device #1? Would you please change the configuration to something like this:
<start name="uart_drv"> <binary name="kdb_uart_drv"/> <resource name="RAM" quantum="1M"/> <provides> <service name="Uart"/> <service name="Terminal"/> </provides> <config> <policy label="terminal_mux" uart="0" detect_size="yes"/> </config> <route> <any-service> <parent/> </any-service> </route> </start>
If the double quoting of letters remain, please post your complete run-script, so that one can reproduce your problem.
The other problem is that when i enter another path using the command 'cd ', the path can not appear int the front of console line. You can not know what path you are.
Well, this is something related to the shell you're using (I assume the Android debug shell) only. Would you please be appreciative of us not discussing such items on the mailing list, first and foremost related to Genode issues?
Regards Stefan
hi At 2013-05-15 17:48:26,"Stefan Kalkowski" <stefan.kalkowski@...1...> wrote:
Sorry for the run script error. I have put the right complete run-script in the attachment. With this run-script in the attachment, the double quoting of letters remain.
Sorry for that, I will check the shell and only discuss issues related to Genode.... Have a nice day
Hi,
On 05/16/2013 02:27 PM, longjks wrote:
ok, thank you for providing the script. I fear there are some general problems with running L4Linux on the Pandaboard with Genode's current master branch. When trying to use your script it hangs after reading the first blocks from sd-card. I'll investigate that problem. Nevertheless, I assume the double quoting problem might be related to a slightly outdated version of the Fiasco.OC kernel. For the KDB uart driver to work properly, the kernel was tweaked a bit to omit echoing characters given to serial line:
https://github.com/ssumpf/foc/commit/1d8bc40fd966f794c4ff3017265f80cb0032b43...
To have the right Fiasco.OC version in place, please do a 'make prepare' in the 'base-foc' directory. After that, better do a 'make cleanall' in your build directory
No problem.
Have a nice day
Have a nice day too
Hi,
it's me again.
I've found the problem related to the current master branch. It was just a missing config entry for the usb driver. One has to define in the configuration of the driver, which USB host controller will be used, and enabled. After tweaking the configuration like that, I could use your script draft, and boot L4android. The double quoting is no issue for me.
Possibly, you can update to Genode's current master branch, do a 'make prepare' at least in base-foc, and ports-foc, and try the attached run script in a fresh build directory?
Regards Stefan
On 05/22/2013 11:02 AM, Stefan Kalkowski wrote:
-
longjks -
Stefan Kalkowski