Hyper Terminal communications test for 218x EZ-ICE: NOTE: Connection to a DSP Target is not required for this test. 1. Open Hyper Terminal (Start, Programs, Accessories, Communications(W9x only), Hyper Terminal, hypertrm.exe or Hyper Terminal. 2. Enter New Connection name in the Connection Description dialog box. Click OK. 3. Select COM port in the Connect using: field of the Connect To dialog box. 4. In the COMn Properties screen, Port Settings: Bits per second: 9600 Data bits: 8 Parity: None Stop bits: 1 Flow control: hardware Click OK 5. Click on Receive Button in the main Hyper Terminal window. Browse for destination folder to "Place received file..." Select 1K Xmodem in "Use receiving protocol:" field Click Receive. Enter name of file in Receive Filename dialog box, e.g., 218xtest, Click OK. 6. Click Cancel in the 1K Xmodem File Receive for... box. 7. Power up ICE, something similar to below should appear in the Hyper Terminal main window. ///////////////////////////////////////////////// Boot code v1.0a May 7, 1997 Flash code v1.0N July 14, 2000 for menu (1 sec) $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ ENTERING EMULATOR jumping to FLASH ROM ///////////////////////////////////////////////// 8. You get the above splash screen when you press reset and HyperTerminal is connected, to run additional tests see procedure below. For the additional tests the EZ-ICE must be connected to a target. NOTE: The contents of FLASH Memory may be changed when proceeding with additional tests. See the "BE AWARE..." note below for more information. 10 ///////////////////////////////////////////////// 20 Boot code v1.0a May 7, 1997 30 Flash code v1.0N July 14, 2000 40 50 for menu (1 sec) 60 $$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$ 70 ENTERING EMULATOR 80 90 jumping to FLASH ROM 100 ///////////////////////////////////////////////// Look at line 50 , immediately after you press the reset on the EZ-ICE, press 'enter' on your keyboard while the $ line is writing. This will let you go into another menu that looks like this: 10 Boot code v1.0a May 7, 1997 20 30 j - jump to emulator in Flash memory 40 c - Compute CRC of Boot code and Flash code 50 i - DSP interface test 60 t - SRAM test 70 f - Flash memory test 80 update - update FLASH ROM 90 erase - erase all FLASH ROM 100 ? - menu 110 $ When this menu appears, you can run the tests in the menu items by pressing that letter then 'enter'. For example I could run the I test, and my screen might look like: 110 $i 120 Testing DSP emulation port 130 Expect 0x0F5A got 0x0000 - ERROR 140 Expect 0xA5F0 got 0x0000 - ERROR 150 160 Boot code v1.0a May 7, 1997 170 180 j - jump to emulator in Flash memory 190 c - Compute CRC of Boot code and Flash code 200 i - DSP interface test 210 t - SRAM test 220 f - Flash memory test 230 update - update FLASH ROM 240 erase - erase all FLASH ROM 250 ? - menu 260 $ Notice line 110, I pressed 'i' then enter, and ran the interface test. Lines 130 & 140 show that an error occurred. This test writes to a register inside the DSP and then reads it back. If the target board is not connected, or is malfunctioning, this test will fail just like above. It is designed to test the interface between the "target board" and the EZ-ICE, however, by virtue of being able to see the results in HyperTerminal, you are testing between the PC and the target board. I could also run the SRAM test which tests the EZ-ICE's system RAM, this test does not test the DSP's SRAM it doesn't even need to be connected to a "target board" to run the test. By pressing 't' then 'enter' the test can be run. 260 $t 270 Testing SRAM 0xC000..0xEFFF 280 0 error(s) with 0000, 0000, 0000 290 0 error(s) with 5555, 5555, 5555 300 0 error(s) with AAAA, AAAA, AAAA 310 0 error(s) with FFFF, FFFF, FFFF 320 0 error(s) with increment 330 340 Boot code v1.0a May 7, 1997 350 360 j - jump to emulator in Flash memory 370 c - Compute CRC of Boot code and Flash code 380 i - DSP interface test 390 t - SRAM test 400 f - Flash memory test 410 update - update FLASH ROM 420 erase - erase all FLASH ROM 430 ? - menu 440 $ Lines 270 through 320 show me the result of this test. In this case, the test passed without any errors. By typing 'f' then 'enter' the FLASH test is selected. Typically, FLASH tests are destructive to the contents of the flash and this is no exception. To get into this test, the user must type 'f', 'enter' then 'yes' then 'enter' The yes must be typed in within 1 second of the 'enter' or the test will not be performed. If you do not do it fast enough it looks like this: 440 $f 441 The emulator code in Flash will be erased and must be reprogrammed 442 Enter 'yes' to continue test 443 $abort A passed test looks like this: 440 $f 450 The emulator code in Flash will be erased and must be reprogrammed 460 Enter 'yes' to continue test 470 $yes 480 Testing... 490 passed erase test 500 passed increment pattern test 510 passed all zero test 520 530 Boot code v1.0a May 7, 1997 540 550 j - jump to emulator in Flash memory 560 c - Compute CRC of Boot code and Flash code 570 i - DSP interface test 580 t - SRAM test 590 f - Flash memory test 600 update - update FLASH ROM 610 erase - erase all FLASH ROM 620 ? - menu 630 $ Notice lines 450 - 510. 450 is warning you that the flash will be erased and need to be reprogrammed, and lines 490 - 510 say the flash passed the various different tests. This is where and why you would need to edit the registry to tell VisualDSP that the flash has been destroyed. (See below) BE AWARE - the HyperTerminal utility erases the flash in the emulator. To restore the flash in the emulator you must do the following or you will not be able to use the emulator with the debugger. 1) Close out of the debugger and Hyper Terminal. 2) Go to START > Run and type in regedit. 3) Go to H_KEY_Current User > Software > Analog Devices > VisualDSP > 218x folder and delete the 218x folder 4) Close out of the Registry. 5) Now restart the VisualDSP debugger and select the proper ICE session that represents your target. This assumes you corrected the problem discovered during the Hyper Terminal dsp Interface test