lkcl changed the topic of #arm-netbook to: arm-netbook: Don't ask to ask. Just ask! - EOMA68 spec http://bit.ly/ZHqfxA - ML arm-netbook@lists.phcomp.co.uk - Logs http://bit.ly/XELKJq or http://bit.ly/15OCYPD - For Allwinner/sunxi discussions prefer #linux-sunxi - iMX6 Card http://bit.ly/XAUGCD - Flying Squirrel http://bit.ly/WgOYaR - Allwinner A10/A20 Card http://bit.ly/zBLAbY - http://rhombus-tech.net
infobot has quit [Read error: Connection reset by peer]
infobot has joined #arm-netbook
robgriff444 has quit [Remote host closed the connection]
leviathan has joined #arm-netbook
tuliom has quit [Quit: Konversation terminated!]
leviathan has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
oaken-source has joined #arm-netbook
oaken-source has quit [Ping timeout: 248 seconds]
robgriff444 has joined #arm-netbook
diego_r has joined #arm-netbook
stefanro has joined #arm-netbook
oaken-source has joined #arm-netbook
stefanro has left #arm-netbook [#arm-netbook]
Necrosporus has joined #arm-netbook
<Necrosporus> hello. I have an ARM device. I have identified pins which could be UART but I cannot determina data rate
<Necrosporus> 115200 doesn't work, 9600 does not work
robgriff444 has quit [Quit: Konversation terminated!]
<jn__> Necrosporus: try some more speeds. i've seen 57600 baud once. (more speeds are listed in termios(3), at least in the linux manpage)
<jn__> a digital oscilloscope or a logic analyzer may also be useful
<Necrosporus> jn__, thanks. However it turns out that the connector was not UART
<Necrosporus> What it was I do not know but it sends some garbage out when device is turned on just like uart would
<Necrosporus> Other connector is UART however and it sort of works
<jn__> ah!
<jn__> how does it sort of work?
<Necrosporus> jn__, works fine but does not output login: stuff
<Necrosporus> or maybe I'm not waiting long enough
<Necrosporus> the device has android
<Necrosporus> It is a TVbox
<jn__> maybe it scrolled by already
<jn__> pressing enter doesn't help?
<jn__> or maybe it just doesn't spawn a shell or getty on the serial port
leviathan has joined #arm-netbook
leviathan has quit [Client Quit]
leviathan has joined #arm-netbook
<Necrosporus> It's more likely
<Necrosporus> It has two consoles however
<Necrosporus> Firmware start at: 0x00023c59
<Necrosporus> OK:Read c1107d54=000003bd
<Necrosporus> >
<Necrosporus> r c1107d54
<Necrosporus> Enter Debugrom mode at /hdd2/home/luoj/android/work/uboot/uboot_mc_ddr_480/board/amlogic/stv_mbx_mc/firmware/lowlevel_init.c:0x000000cd
<Necrosporus> jn__, do you have any ideas what sort of console it is and what commands it accepts after > ?
<Necrosporus> Another console is available by hitting anykey a little later
<Necrosporus> init suspend firmware done. (ret:0)
<Necrosporus> Hit any key to stop autoboot: 0
<Necrosporus> MCBOX #
<Necrosporus> this one seems to be regular uboot console
<jn__> which comes first?
<Necrosporus> > comes on very early boot if you hit key immediately after plugging power
<Necrosporus> # comes if you let it boot for a couple of seconds and hit any key then
<jn__> "Debugrom mode" and the path after it make it sound like this is some version of uboot that's in a ROM in the SoC
<Necrosporus> Probably
<jn__> Necrosporus: ok, that makes sense
<jn__> do you see any output from linux or userspace?
<Necrosporus> So you think there are three on-board ROMs, one in SoC, one in NOR flash and one in NAND?
<Necrosporus> Yes
<jn__> i haven't seen the board, so i don't know about SPI/NOR flash and NAND flash, but that sounds like a common setup
diego_r has quit [Ping timeout: 260 seconds]
leviathan has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
oaken-source has quit [Ping timeout: 265 seconds]
diego_r has joined #arm-netbook
diego_r has quit [Ping timeout: 248 seconds]
tuliom has joined #arm-netbook
tuliom has quit [Quit: Konversation terminated!]