search

135u5 / tinyos-main

Automatically exported from code.google.com/p/tinyos-main
1 stars 0 forks source link

GDB gets stuck after first soft_reset_halt #21

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Connect ERASE and reset the board.
2. Connect JTAG and lauch openocd. Make sure the output shows how many 
watchpoints and breakpoints the board supports.
3. Run GDB and execute the following script:

target remote :3333
mon halt
load
mon at91sam3 gpnvm set 1
mon soft_reset_halt
b main
continue

4. At the breakpoint, step (next) through until the Platform.init call. This 
call will block and never return. For some reason, the main clock never gets 
ready after the last switch to the PLLA clock.
5. execute "mon soft_reset_halt"
6. Continue the execution, and step again through the code. This time, 
Platform.init will return and not get stuck at the mainclock switch.

I have no idea why we get stuck the first time, but not the second time. Might 
be related to issue 20 
(http://code.google.com/p/tinyos-main/issues/detail?id=20)?

Original issue reported on code.google.com by thomas.s...@gmail.com on 22 Feb 2011 at 2:55

GoogleCodeExporter commented 8 years ago

Original comment by thomas.s...@gmail.com on 26 May 2011 at 10:38