• Home
  • Help
  • Search
  • Login
  • Register
Pages: 1 2 3 [4]
Author Topic: end_request: I/O error, dev mtdblock0, sector 0  (Read 31633 times)
Raśl Porcel
Global Moderator
Jr. Member
*****

Karma: 0
Posts: 68


View Profile
« Reply #45 on: May 15, 2009, 04:52:13 AM »

And why are you doing a reset?
After you do the resume, connect to the serial console.
http://www.openplug.org/plugwiki/index.php/Setting_up_Serial_Console_Under_Linux
Logged

sevi4310
Jr. Member
**

Karma: 0
Posts: 63


View Profile
« Reply #46 on: May 15, 2009, 08:49:35 AM »

I did "resume", look at the log below but after rebooting and connecting the windows mashine by Tera Term I have no message on it. I used it before and it worked alright.
Also I tried it on Ubuntu but:
root@stockalerts:~# modprobe usbserial
FATAL: Module usbserial not found.
root@stockalerts:~# modprobe ftdi_sio vendor=0x9e88 product=0x9e8f
root@stockalerts:~#


Code:
root@stockalerts:~# telnet localhost 4444
Trying ::1...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Open On-Chip Debugger
> sheevaplug_init
target state: halted
target halted in ARM state due to debug-request, current mode: Supervisor
cpsr: 0x000000d3 pc: 0xffff0000
MMU: disabled, D-Cache: disabled, I-Cache: disabled
0 0 1 0: 00052078

> load_image uboot
378216 byte written at address 0x00600000
11540 byte written at address 0x00670000
downloaded 389756 byte in 2.930218s

> resume 0x00600000

>
Logged

Raśl Porcel
Global Moderator
Jr. Member
*****

Karma: 0
Posts: 68


View Profile
« Reply #47 on: May 15, 2009, 09:21:57 AM »

Do this:
apt-get install picocom
picocom -b 115200 /dev/ttyUSB1

And then do the openocd command, then the nc command...and watch the terminal where you're running picocom
Logged

sevi4310
Jr. Member
**

Karma: 0
Posts: 63


View Profile
« Reply #48 on: May 15, 2009, 09:46:29 AM »

root@stockalerts:~# modprobe usbserial
FATAL: Module usbserial not found.
root@stockalerts:~# picocom -b 115200 /dev/ttyUSB1
picocom v1.4

port is        : /dev/ttyUSB1
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : ascii_xfr -s -v -l10
receive_cmd is : rz -vv


FATAL: cannot open /dev/ttyUSB1: No such file or directory
root@stockalerts:~#
Logged

sevi4310
Jr. Member
**

Karma: 0
Posts: 63


View Profile
« Reply #49 on: May 15, 2009, 10:03:17 AM »

it works with /ttyUSB0 but when I try
sudo openocd -f /usr/local/lib/openocd/board/sheevaplug.cfg
it close the terminal

Look at the output below


root@stockalerts:/dev# picocom -b 115200 /dev/ttyUSB0
picocom v1.4

port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
escape is      : C-a
noinit is      : no
noreset is     : no
nolock is      : no
send_cmd is    : ascii_xfr -s -v -l10
receive_cmd is : rz -vv

Terminal ready

FATAL: term closed
root@stockalerts:/dev#
Logged

Raśl Porcel
Global Moderator
Jr. Member
*****

Karma: 0
Posts: 68


View Profile
« Reply #50 on: May 15, 2009, 10:12:38 AM »

Its normal.

Load both usbserial and the other one, then paste the dmesg log.
Logged

sevi4310
Jr. Member
**

Karma: 0
Posts: 63


View Profile
« Reply #51 on: May 15, 2009, 10:21:10 AM »

root@stockalerts:/dev# modprobe usbserial
FATAL: Module usbserial not found.
root@stockalerts:/dev# modprobe ftdi_sio vendor=0x9e88 product=0x9e8f
root@stockalerts:/dev#
root@stockalerts:/dev# ls ttyU*
ttyUSB0  ttyUSB1
root@stockalerts:/dev#
Logged

Raśl Porcel
Global Moderator
Jr. Member
*****

Karma: 0
Posts: 68


View Profile
« Reply #52 on: May 16, 2009, 03:15:14 AM »

Let's see...
-Open 3 terminals and make sure you are root on all three.
-load the modules and make sure you have /dev/ttyUSB0 and 1.
-On one terminal, run picocom -b 115200 /dev/ttyUSB1 (don't close the terminal, keep it running with the command)
-On another terminal, change the directory where the uboot file is, and run the openocd command. (don't close the terminal, keep it running with the command)
-On another terminal, execute the telnet thing, and run the sheevaplug_init, load_image, and resume commands
-Check what shows up on the picocom terminal.
Logged

yotam
Global Moderator
Newbie
*****

Karma: 1
Posts: 10


View Profile
« Reply #53 on: May 20, 2009, 01:30:52 PM »

Please use resume 0x670000
Logged

Pages: 1 2 3 [4]
Print
Jump to: