Hello
So in the midst of procrastinating, I decided that my Dockstar's u-boot desperately needed upgrading. Of course.
I downloaded the latest one from this forum and attempted to flash it from uboot itself (tftp then write to flash)
After doing this, I had a brick.
I managed to recover it using openocd and a buspirate, but the u-boot I flashed was a bit weird and didn't have support for booting from USB etc. I think it was the stock u-boot.
From this u-boot, I attempted what I thought was a slightly different method of flashing the latest one. I was feeling brave since now I knew I had JTAG to fall back on. And of course it bricked, and now JTAG won't work.
I'm using the config file and the instructions (mostly) from here: http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirate
I can halt the CPU in Thumb mode, but not in ARM mode. If I get it into Thumb, I get the following:
> halt
target was in unknown state when halt was requested
target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x400000f3 pc: 0xffff0a42
MMU: enabled, D-Cache: enabled, I-Cache: enabled
If I halt the CPU in ARM mode, I get this. It used to work:
> halt
invalid mode value encountered 3
cpsr contains invalid mode value - communication failure
in procedure 'halt'
invalid mode value encountered 3
cpsr contains invalid mode value - communication failure
Polling target feroceon.cpu failed, GDB will be halted. Polling again in 100ms
invalid mode value encountered 3
cpsr contains invalid mode value - communication failure
Polling target feroceon.cpu failed, GDB will be halted. Polling again in 300ms
...
Does anyone know what I can try to make this work? Why can't I get this device to halt in ARM mode? I can't access the flash otherwise :/
I've checked wiring multiple times, it seems to be fine.
And for bonus points, which u-boot image should I be using and how do I flash clean environment variables to the device?
Thanks in advance. Please say if I need to add more information.
So in the midst of procrastinating, I decided that my Dockstar's u-boot desperately needed upgrading. Of course.
I downloaded the latest one from this forum and attempted to flash it from uboot itself (tftp then write to flash)
After doing this, I had a brick.
I managed to recover it using openocd and a buspirate, but the u-boot I flashed was a bit weird and didn't have support for booting from USB etc. I think it was the stock u-boot.
From this u-boot, I attempted what I thought was a slightly different method of flashing the latest one. I was feeling brave since now I knew I had JTAG to fall back on. And of course it bricked, and now JTAG won't work.
I'm using the config file and the instructions (mostly) from here: http://plume.redox.ws/article13/dockstar-debricking-jtag-with-buspirate
I can halt the CPU in Thumb mode, but not in ARM mode. If I get it into Thumb, I get the following:
> halt
target was in unknown state when halt was requested
target state: halted
target halted in Thumb state due to debug-request, current mode: Supervisor
cpsr: 0x400000f3 pc: 0xffff0a42
MMU: enabled, D-Cache: enabled, I-Cache: enabled
If I halt the CPU in ARM mode, I get this. It used to work:
> halt
invalid mode value encountered 3
cpsr contains invalid mode value - communication failure
in procedure 'halt'
invalid mode value encountered 3
cpsr contains invalid mode value - communication failure
Polling target feroceon.cpu failed, GDB will be halted. Polling again in 100ms
invalid mode value encountered 3
cpsr contains invalid mode value - communication failure
Polling target feroceon.cpu failed, GDB will be halted. Polling again in 300ms
...
Does anyone know what I can try to make this work? Why can't I get this device to halt in ARM mode? I can't access the flash otherwise :/
I've checked wiring multiple times, it seems to be fine.
And for bonus points, which u-boot image should I be using and how do I flash clean environment variables to the device?
Thanks in advance. Please say if I need to add more information.