Show Posts
|
|
Pages: 1 [2] 3 4 5
|
|
17
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
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:~# 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
>
|
|
|
|
|
18
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
on: May 14, 2009, 03:42:52 PM
|
It looks like it worked this time but I still cant get any info at my terminal window. Here is a log: 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.929965s
> resume 0x00600000
target state: halted target halted in ARM state due to debug-request, current mode: Undefined cpsr: 0x0000009b pc: 0xffff0004 MMU: disabled, D-Cache: disabled, I-Cache: disabled > reset JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2) JTAG Tap/device matched
> Connection closed by foreign host. root@stockalerts:~#
|
|
|
|
|
20
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
on: May 13, 2009, 11:23:19 AM
|
Both nc and telnet work now in a different window but there is another problem: 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 SheevaPlug_U-Boot/Compiled_Images/u-boot-rd88f6281Sheevaplug couldn't open SheevaPlug_U-Boot/Compiled_Images/u-boot-rd88f6281Sheevaplug
> Example 3 doesn't work ether. root@stockalerts:~# telnet localhost 4444 Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. Open On-Chip Debugger > setenv ipaddr 192.168.1.235 invalid command name "setenv_ipaddr" called at file "command.c", line 456 called at file "embedded:startup.tcl", line 89 called at file "embedded:startup.tcl", line 93 > setenv serverip 192.168.1.53 invalid command name "setenv_serverip" called at file "command.c", line 456 called at file "embedded:startup.tcl", line 89 called at file "embedded:startup.tcl", line 93 > bubt uboot.bin invalid command name "bubt_uboot.bin" called at file "command.c", line 456 called at file "embedded:startup.tcl", line 89 called at file "embedded:startup.tcl", line 93 >
|
|
|
|
|
23
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
on: May 13, 2009, 09:08:29 AM
|
I don't think it a a hardware problem. Maybe I did something wrong. Howe do I have to connect the plug to the computer? 1. ./configure --enable-ft2232_libftdi gave me some errors. Could you check it. There is output above (Posted on: May 11, 2009, 02:11:31 PM). 2. Is it correct? I have a command line after nc command. root@stockalerts:/home/serge/sheeva# nc localhost 4444 root@stockalerts:/home/serge/sheeva# 3. Here is output for openocd but there was no anything after that. Do I have just do <CTR>+C? root@stockalerts:/home/serge/sheeva# sudo openocd -f /usr/local/lib/openocd/board/sheevaplug.cfg Open On-Chip Debugger 1.0 (2009-05-11-14:15) svn:1589
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ 3000 kHz dcc downloads are enabled Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2) Info : JTAG Tap/device matched Error: unknown EmbeddedICE version (comms ctrl: 0x00000018) Warn : no telnet port specified, using default port 4444 Warn : no gdb port specified, using default port 3333 Warn : no tcl port specified, using default port 6666 Warn : DBGACK set while target was in unknown state. Reset or initialize target. target state: halted target halted in ARM state due to debug-request, current mode: Undefined cpsr: 0x200000db pc: 0xffff0130 MMU: disabled, D-Cache: disabled, I-Cache: disabled
|
|
|
|
|
25
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
on: May 11, 2009, 02:53:37 PM
|
Which uboot.bin I have to use. I've got flowing output. root@stockalerts:/home/serge/sheeva# openocd -f /usr/local/lib/openocd/board/sheevaplug.cfg -c init -c sheevaplug_reflash_uboot Open On-Chip Debugger 1.0 (2009-05-11-14:15) svn:1589
BUGS? Read http://svn.berlios.de/svnroot/repos/openocd/trunk/BUGS
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $ 3000 kHz dcc downloads are enabled Info : JTAG tap: feroceon.cpu tap/device found: 0x20a023d3 (Manufacturer: 0x1e9, Part: 0x0a02, Version: 0x2) Info : JTAG Tap/device matched Error: unknown EmbeddedICE version (comms ctrl: 0x00000018) Warn : no telnet port specified, using default port 4444 Warn : no gdb port specified, using default port 3333 Warn : no tcl port specified, using default port 6666 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 NAND flash device 'NAND 512MiB 3,3V 8-bit' found Warn : invalid block: 2 Error: erase operation didn't pass, status: 0xe1 erase failed Warn : target reentered debug state, but not at the desired exit point: 0x10000014 Error: error executing hosted NAND write Error: timed out while waiting for target halted Error: error executing hosted NAND write Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target Error: NAND flash access requires halted target failed writing file uboot.bin to NAND flash 0 at offset 0x0000e000 Warn : target not halted Runtime error, file "/usr/local/lib/openocd/board/sheevaplug.cfg", line 103:
|
|
|
|
|
27
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
on: May 11, 2009, 02:11:31 PM
|
./configure --enable-ft2232_ftd2xx works now but ./configure --enable-ft2232_libftdi dives an error. root@stockalerts:/trunk# ./bootstrap Bootstrap complete; you can './configure --enable-maintainer-mode ....' root@stockalerts:/trunk# ./configure --enable-ft2232_libftdi checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for library containing ioperm... none required checking for library containing dlopen... -ldl checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking jtag_minidriver.h usability... no checking jtag_minidriver.h presence... no checking for jtag_minidriver.h... no checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking elf.h usability... yes checking elf.h presence... yes checking for elf.h... yes checking for strings.h... (cached) yes checking stdbool.h usability... yes checking stdbool.h presence... yes checking for stdbool.h... yes checking whether time.h and sys/time.h may both be included... yes checking whether byte ordering is bigendian... no checking for strndup... yes checking for strnlen... yes checking for gettimeofday... yes checking for usleep... yes checking for vasprintf... yes checking for "./guess-rev.sh"... yes checking whether to enable verbose JTAG I/O messages... no checking whether to enable verbose USB I/O messages... no checking whether to enable verbose USB communication messages... no checking Build & Link with libftdi...... configure: error: Cannot build & run test program using libftdi
|
|
|
|
|
29
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
on: May 07, 2009, 11:07:12 AM
|
|
Here is output for both configure does it look good?
root@stockalerts:/trunk# ./configure --enable-ft2232_libftdi checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for library containing ioperm... none required checking for library containing dlopen... -ldl checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking jtag_minidriver.h usability... no checking jtag_minidriver.h presence... no checking for jtag_minidriver.h... no checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking elf.h usability... yes checking elf.h presence... yes checking for elf.h... yes checking for strings.h... (cached) yes checking stdbool.h usability... yes checking stdbool.h presence... yes checking for stdbool.h... yes checking whether time.h and sys/time.h may both be included... yes checking whether byte ordering is bigendian... no checking for strndup... yes checking for strnlen... yes checking for gettimeofday... yes checking for usleep... yes checking for vasprintf... yes checking for "./guess-rev.sh"... yes checking whether to enable verbose JTAG I/O messages... no checking whether to enable verbose USB I/O messages... no checking whether to enable verbose USB communication messages... no checking Build & Link with libftdi...... configure: error: Cannot build & run test program using libftdi root@stockalerts:/trunk# root@stockalerts:/trunk# root@stockalerts:/trunk# ./configure --enable-ft2232_ftd2xx checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for library containing ioperm... none required checking for library containing dlopen... -ldl checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking jtag_minidriver.h usability... no checking jtag_minidriver.h presence... no checking for jtag_minidriver.h... no checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking elf.h usability... yes checking elf.h presence... yes checking for elf.h... yes checking for strings.h... (cached) yes checking stdbool.h usability... yes checking stdbool.h presence... yes checking for stdbool.h... yes checking whether time.h and sys/time.h may both be included... yes checking whether byte ordering is bigendian... no checking for strndup... yes checking for strnlen... yes checking for gettimeofday... yes checking for usleep... yes checking for vasprintf... yes checking for "./guess-rev.sh"... yes checking whether to enable verbose JTAG I/O messages... no checking whether to enable verbose USB I/O messages... no checking whether to enable verbose USB communication messages... no checking ftd2xx.h usability... no checking ftd2xx.h presence... no checking for ftd2xx.h... no configure: error: You seem to be missing the FTD2xx driver header file. root@stockalerts:/trunk#
|
|
|
|
|
30
|
Hardware and U-Boot firmware / U-Boot stuff / Re: end_request: I/O error, dev mtdblock0, sector 0
|
on: May 07, 2009, 09:22:01 AM
|
|
here are some ls outputs:
root@stockalerts:/trunk# ls /usr/lib/libftd2xx.so. ls: cannot access /usr/lib/libftd2xx.so.: No such file or directory root@stockalerts:/trunk# ls /usr/lib/libftd2xx.so Config.txt ftd2xx.cfg libftd2xx0.4.16 libftd2xx.so.0.4.16 libusb-0.1.12 readme.dat static_lib faq.txt ftd2xx.h libftd2xx.so.0.4.12 lib_table object sample WinTypes.h root@stockalerts:/trunk# ls /usr/lib/libftd2xx.so.* /usr/lib/libftd2xx.so.0 /usr/lib/libftd2xx.so.0.4.16
|
|
|
|
|