sam460: takeover control by putty ?

@All

Currently , when i want to control Sam460 via serial from the putty (i mean typing symbols on the terminal instead of on the SAM's keyboard), i should physically detach mouse and keyboard from. But, is there are some variable/environment which i can set, to avoid detaching of keyboard/mouse physically ?

For example, on pegasos2, when i want to have control over terminal and not over peg2's keyboard, i set "setenv output-device ttya", and then use putty without "flow control" to make it works. And to give control back to peg2's keyboard i set it back like "setenv output-device screen". But this is openfirmware, while sam460 is uboot based.

So, question is : is there any environment of this kind like on peg2, which when i set, i have control by terminal of my sam460, without detaching keyboard/mouse from them ?

Setting "stdout=serial" of course only mean to threw output to serial instead of screen, but not about ability to type from serial.

Thanks!

@kas1e

setenv stdin serial

@max
Quote:

Yeah, it works for current session (When i am in uboot shell already) , but , when i reboot, i can't "esc" from putty's keyboard to go to the uboot , neither from usb keyboard. But i definately have "serial" for both stdin and stdout.

Maybe i need some special serial settings to make "esc" works form keyboard on serial to go to uboot ? I currently tried 115200, data bits 8, stop bits 1, parity NONE, and flow control NONE (at least with XON/XOFF it didn't works for me on pegasos2).

@kas1e

if you need to interrupt the boot countdown and go into u-boot shell, you may press 'q' instead of ESC

@m3x
Right ! "q" works then ! Strange why not ESC, but so far there is a way. And issue only when both stdin and stdout set to serial. If i set stdin to serial, but stdout to vga, then ESC from putty still works. But if i want both output/input to/from serial, then i had to use "q" , as ESC didn't works.

And btw, not only "q", but also "space" works too to go to the uboot-graphical menu: and even with "stdout=serial" it will throw on VGA, which can't be controlled very well as i have both stdout and stdin to "serial" : i.e. up/down/left/right didn't work, but instead act like "esc" :) Maybe if play with different terminal settings it can work, but then if "q" work, then all fine. Is there reasons why "esc" stop working after stdin+stdout at the same time set to serial ?

ps. Btw, is uboot for sam only support "ext2" by default and no fat one ? I just see everywhere in the internet uboot should have "fatls", "fatload" commands, etc, while our one only have "ext2ls" and "ext2load"

ps2. check discord plz :)

@kas1e

yes, it supports only ext2fs, fat support was removed to save space on the 512 Kb boot eeprom, maybe we can add it back again with a new u-boot version.

New u-boot supporting RX500 cards would be nice.

wait.. :P

@kas1e
Quote:Setenv only changes variables for the current session, if you want to make it permanent use

@joerg
Of course i use saveenv :) Just there is some bug in uboot which prevent using "ESC" when you have both env set to serial (while "q" works).

@kas1e

maybe can the 'ESC not working' be a putty setting/config issue?

EDIT1: tried here on a WinXP and putty 0.73 and ESC works fine:

@javier
As i point before issue with non working ESC happens when you have and stdout set to serial _and_ stdin too (to be able to type from terminal while usb keyboard still attached to sam). In your case stdin is usbkbd. This combo works. But once you will set it to serial, then only "q" will work, while "esc" didnt

Try set to serial also stdin (and not forget to set flow control to None in putty, at least with my cable i shoukd to do so to be able to type from putty)

@skygecko
Quote:



https://www.amigans.net/modules/newbb/viewtopic.php?topic_id=9544

@kas1e

Ooops I bypassed that "stdin" option X-)