HyperTerminal outside of Windows 7 systems

I will be honored if I can help you, thanks for the following. ：-）)

Recently because of my PC computer XP out of the problem, finally installed Win7 system, before the use of Win 7 Big six months, eventually due to some of the professional-related software and its poor compatibility of the reason to abandon the win 7, yesterday spent a few hours to finish (:-) is mainly part of the drive is not easy to find, or is not installed on the bad).

Installed Win7, began to wait to test jlink&ads& serial communication is normal, test serial port found Win7 no super terminal (XP system with), then the Internet search, finally or in csdn find a Dongdong "good Windows7 Super terminal" , if useful Win7 friends may wish to try, download the URL: http://download.csdn.net/source/2613324, if there is not enough csdn to load the children's shoes, you can leave the mailbox, I send you.

Here are a few pieces of the test-cut diagram:

Hardware environment for testing: GT2440 Development Board

Software Environment: U-boot (for GT2440:-) the previous period of time transplant well, support CS8900 network card and NOR flash---sst89vf1601a ... )

Uimage (for GT2440): Open the Kernel in NFS mode.

U-boot start OK.

PRINTENV View U-boot Environment variables

Use setenv to delete the environment variable "bootcmd" and use saveenv to save it in Flash, where nor flash write OK.

Before testing the network, use the instructions above (setenv sets the ipaddr of the target Development Board to the ServerIP of the host (Ps:linux system) so that it is in a network segment and then Savenv), Then printenv see the Development Board's network card base address ethaddr whether there is a setting; (The network card on my Development Board is CS8900, after viewing datasheet found that it does not have an external EEPROM to store the network card base address information, Therefore, the establishment of its base site can be arbitrarily set the correct format of the base site, if the Development Board is other network card chips, before the set up to check their datasheet related information, environment variables set OK, saveenv, easy to use when not need to reset ( The premise is that your development Board bootloader did not erase, the above set OK, first use ping to test the Development Board network is unobstructed (here I choose the Development Board and the way the router is directly connected): Ping 192.168.0.23 (This is my host IP), if the Super terminal display "Host 192.168.0.23 is Alive", the network is unobstructed. Then use TFTP to download the kernel image file (here's a little experience: if you use the Development Board to connect to the notebook, be sure to turn off the wireless in your notebook, and then assign the IP manually): TFTP 31000000 (the address that the kernel resides in memory) Uimage-nfs ( This file is stored in the/tftpboot directory under the Linux system root file directory, and the download process is shown in the following illustration. When the download is complete, use BOOTM 31000000 to run the kernel, and if the last image shows, use the NFS mode to reboot the kernel OK.

NFS Mode Kai kernel OK. You can use the LS command to view the files in the current directory (the commands you support are the choices you make when you configure BusyBox). In this running Kernel Load module module Please view the previous articles.