ࡱ> 241%` gbjbj"x"x .@@g@@@@ L mdddddddd$#hddddddd'dddd dX p;:9D@z=0m 1"1 1 ddddddd dddmddddDD The good news is that the Serial Debug Monitor interfaces with CodeWarrior in such a way that there is very little difference between using it and using the P & E BDM. Here is what you must do differently: You must specify the HC(S)12 Serial Monitor when you create the project. You must have the serial cable connected between the modules serial port and the PCs serial connector when you bring up Code Warrior and start debugging the program. You must have the power cube that came with the module kit plugged in to power the CSM12C32 module. Set your computers serial communication (COM) port to 9600 baud, 8 data bits, no parity, one stop bit, no flow control, if it is not already set this way. Do this by right clicking on the My Computer icon, then select Properties Hardware Device Manager Ports Communications Port (COM1) Port Settings. This brings up the Communication Port Properties window shown below. Set each parameter as shown below, as needed. While pressing down pushbutton SW1 that is located on the CSM12C32 module, momentarily depress the RESET button on the CSM12C32 module to start the serial debug monitor program running on the CSM12C32 module. (Nothing visible will show up on the CodeWarrior window at this time.) You may now use CodeWarrior to download programs to the module as you did with the P&E BDM. The same CodeWarrior debug commands may be used as with the BDM! When writing programs that are to be debugged with the Serial Monitor, you must only use ONLY the RAM block that starts at 0x4000, not the one that starts at 0xC000, since the one at 0xC000 holds the Serial Monitor Program. You can no longer debug a program that uses the serial port, since it is being used by the debugger. However, the serial port may still be used in an application as long as the serial port driver routine is not single-stepped through.   ' )  A F xzefghF;hu56\]huB* phhu#huB* CJOJQJ^JaJph ) zfg & Fgdu & Fgdugdu g,1h/ =!"#$% @@@ NormalCJ_HaJmH sH tH DAD Default Paragraph FontRiR  Table Normal4 l4a (k(No Listg)zfi0 0 0 0 0 0 0 0 0y00)zfi0 0 0 0 0 0 0 0 0 0fgg g mqii3ii"L0M^`.^`.pp^p`.@ @ ^@ `.^`.^`.^`.^`.PP^P`."LgDKEFEE /EOr9| A5SK| afX &B a c% -X ;w z  $2 =   } G&)23w_bd |g6F KuR%1 x^$l\a#P4@%5AZ#^Z4ag]Dx>j'.62 z.!i0!`!m+"Tz"y#a$=,')8)y)*0*wS*W+,~D,\t,-X.^.j.p/P/R0B1B1J102)J2bj2Ol2!3Aa3 44dM4\456I6]7R76[78u08NW8w_8-+9yY9%:):&-:]:rk:<<o)<2<U</e<fQ=U>U?~?J@+@i8A8A3;A=A/B/BZJBbCvCyC1D5DKDgrD{D0E6ECEG4GzZGZGH*H-HmH3I-%INI:JitJyJg!Ks]KLR^d^!_(_8_V;_.>_nU_v_*aAaHatac=cTc%bcO-d1d2d!Fd`SdpdG{d9eEeqe$fd[ftfuf{fogCh}`hxhPiGQi]ciTgigk\l m:#m7mAnEnqn|nooohonpTpCNp:Zp5 qIqerS|restAtytfuNu^u'vuwuvAEwmwDbx.y2yVvyl*zA-z0zHzf[zecz){f{@|E|5 }$}~:}$~~L~6z/B</?PK%6tTJ!O+j/8nTV-R"Cl%*\Nz!ODMs/N 4?`p. P%smDe%8[P|B=^^Va>ZN04v &R.aT1u8aBnGx$8Se-|.]8A"BB^j=7U7y@PQ;$B#]( 0GPIPdB0@G !C|XOe=ko{ 4?B$fl I\Iz:HO-S=kmWXJ]dlqW&*RLTAVK^yi1 XimCw03't!a&]ddz F;? p&M! ci o=",UH U"YaptO1dsh&"@B67m.AA&ERT\fg>^$d!-6muCIx# 7%4eL7m I~1DO0Rl RuWm 5SMRVp2(3YHwX\_S`|$@'9<WZeB"AbF]foIoEu"83(#h#O$'R@[Vu=5s@ffp&8ffgP@UnknownGz Times New Roman5Symbol3& z Arial"qh[F[FM M !24dd 2QKX)?u2The good news is that the Serial Debug Monitor interfaces with CodeWarrior in such a way that there is very little difference between using it and using the P & E BDM Keith Hoover Keith Hoover Oh+'0 HTlx    The good news is that the Serial Debug Monitor interfaces with CodeWarrior in such a way that there is very little difference between using it and using the P & E BDMKeith Hoover Normal.dotKeith Hoover1Microsoft Office Word@Ik@88D@ E9DM՜.+,0 hp  $Rose-Hulman Institute of Technology d' The good news is that the Serial Debug Monitor interfaces with CodeWarrior in such a way that there is very little difference between using it and using the P & E BDM Title  "#$%&'(*+,-./03Root Entry FU@9D5Data  1TableAWordDocument.SummaryInformation(!DocumentSummaryInformation8)CompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q