during_the_course_of_developing_a_program_it_seemed_like_my_dsk_board_was_not_behaving_correctly

During the course of developing a program it seemed like my DSK board was not behaving correctly.

I pressed the reset button and things got worse. Code Composer quit communicating with my board. Since that time I have noticed that this happens every time that I push reset. How do I 'bring my board back to life' after my program under development 'kills it'?

If you have to reset the board [it is even possible for 'runaway programs' to get the 6211 into a state that requires power to be removed from the board] you should terminate Code Composer first. The board may then be reset and Code Composer restarted. Part of this problem is that the 6211 DSK is configured for 'ROM Boot Mode'. When you press reset and program [POST] is loaded and executed. This obviously changes the state of the board and the contents of memory on the board. At the same time, Code Composer has information stored about the state and configuration of the board and is not aware that the reset has taken place. Consequently the board and Code Composer become 'out of sync' with each other. Because of this reset should only be used as a 'last resort'.