Please help restore Beagleboard via OpenOCD JTAG

Hello,

Due to my lack of knowledge, I bricked my BeagleBoard by erasing the
contents of flash. When I boot, I get

...40T.........

After which nothing else happens. I tried to restore using
instructions at BeagleBoardRecovery - eLinux.org however, that
was unsuccessful.

I am trying to restore the stock x-loader and u-boot. To that end, I
ordered a Flyswatter from Tincan Tools with the cable adapter, etc.

I followed the instructions on BeagleBoardOpenOCD - eLinux.org to
get OpenOCD running and I can connect to the board.

I get the following for scan_chain command:

scan_chain

     TapName | Enabled | IdCode Expected IrLen
IrCap IrMask Instr
---|--------------------|---------|------------|------------|------|------|------|---------
0 | omap3.cpu | Y | 0x00000000 | 0x0b6d602f | 0x04 |
0x01 | 0x00 | 0x0e
1 | omap3.jrc | Y | 0x00000000 | 0x0b7ae02f | 0x06 |
0x01 | 0x0f | 0x3f

And the following for drscan command:

irscan omap3.cpu 0xE
drscan omap3.cpu 32 0x0

FFFFFFFF

I have a rev B4 board and I am running Ubuntu 8.10 x86_64 on Core2Duo.
I tried compiling OpenOCD with both, libftd2xx and libFTDI support
with the same results shown above.

Could someone please provide instructions for flashing the stock x-
loader and u-boot using OpenOCD and the Flyswatter.

Thank you very much

Hello,

Due to my lack of knowledge, I bricked my BeagleBoard by erasing the
contents of flash. When I boot, I get

...40T.........

After which nothing else happens. I tried to restore using
instructions at BeagleBoardRecovery - eLinux.org however, that
was unsuccessful.

If you are getting 40T, the board recovery procedure should work. I
would go through it very carefully again.

Philip

mishamanulis@gmail.com wrote:

Hello,

Due to my lack of knowledge, I bricked my BeagleBoard by erasing the
contents of flash. When I boot, I get

...40T.........

After which nothing else happens. I tried to restore using
instructions at BeagleBoardRecovery - eLinux.org however, that
was unsuccessful.

As Philip already mentioned, recovery will work if you get 40T

I am trying to restore the stock x-loader and u-boot. To that end, I
ordered a Flyswatter from Tincan Tools with the cable adapter, etc.

I followed the instructions on BeagleBoardOpenOCD - eLinux.org to
get OpenOCD running and I can connect to the board.

Actually, OpenOCD can't be used for anything useful with Beagle due to missing Cortex-A8 support.

At wiki page you mention above, we tried to make this clear by

"As of April 2009, OpenOCD has basic support for OMAP3 on Beagle Board, but still lacks ARM Cortex A8 support. This is work in progress."

Is this misleading? How can we clarify that from a user point of view OpenOCD doesn't work with Beagle, yet, and that support is still work in progress?

Best regards

Dirk

mishamanulis@gmail.com wrote:

Hello,

Due to my lack of knowledge, I bricked my BeagleBoard by erasing the
contents of flash. When I boot, I get

...40T.........

After which nothing else happens. I tried to restore using
instructions at BeagleBoardRecovery - eLinux.org however, that
was unsuccessful.

I am trying to restore the stock x-loader and u-boot. To that end, I
ordered a Flyswatter from Tincan Tools with the cable adapter, etc.

I followed the instructions on BeagleBoardOpenOCD - eLinux.org to
get OpenOCD running and I can connect to the board.

I get the following for scan_chain command:

scan_chain

     TapName | Enabled | IdCode Expected IrLen
IrCap IrMask Instr
---|--------------------|---------|------------|------------|------|------|------|---------
0 | omap3.cpu | Y | 0x00000000 | 0x0b6d602f | 0x04 |
0x01 | 0x00 | 0x0e
1 | omap3.jrc | Y | 0x00000000 | 0x0b7ae02f | 0x06 |
0x01 | 0x0f | 0x3f

And the following for drscan command:

irscan omap3.cpu 0xE
drscan omap3.cpu 32 0x0

FFFFFFFF

Even if it doesn't help you as mentioned earlier, I just tried recent OpenOCD version (1462) and can confirm that it still works like documented in

http://elinux.org/BeagleBoardOpenOCD#telnet

> irscan omap3.cpu 0xE
> drscan omap3.cpu 32 0x0
0B6D602F

Just for the records.

Dirk

At wiki page you mention above, we tried to make this clear by

"As of April 2009, OpenOCD has basic support for OMAP3 on Beagle
Board, but still lacks ARM Cortex A8 support. This is work in progress."

Is this misleading? How can we clarify that from a user point of view
OpenOCD doesn't work with Beagle, yet, and that support is still work
in progress?

If you could list what is and is not supported, that would be
appreciated. "Basic Support" can mean different things to different
people. While a feature list would be great, simply stating what
cannot be done in general terms (i.e. flashing, GDB support, etc.)
would be great.

I'll try again with the recovery procedure and post any errors I may
find in a thread more specific to that topic.

Thank you for the suggestions

Misha

mishamanulis@gmail.com wrote:

At wiki page you mention above, we tried to make this clear by

"As of April 2009, OpenOCD has basic support for OMAP3 on Beagle
Board, but still lacks ARM Cortex A8 support. This is work in progress."

Is this misleading? How can we clarify that from a user point of view
OpenOCD doesn't work with Beagle, yet, and that support is still work
in progress?

If you could list what is and is not supported, that would be
appreciated. "Basic Support" can mean different things to different
people. While a feature list would be great, simply stating what
cannot be done in general terms (i.e. flashing, GDB support, etc.)
would be great.

From user point of view you can't do anything with OpenOCD with OMAP3, yet. No flashing, no GDB support, nothing. You need ARM Cortex A8 support for all of this.

From OpenOCD developer point of view you are able to "see" "ARM JTAG device" to be able to start with developing ARM Cortex A8 support.

Best regards

Dirk