Updating hyper terminal
Follwing are the Hyper Terminal windows showing card detection (One window shows baudrate as 38400, that was while testing for higher clock speeds, current code still uses 19200 baud and 8MHz internal clock of Mega32). 'create File' function replaced with write File, which looks for the filename first, if the given file name doesn't exist then it creates new file and writes data, but if the file already exists, then it opens it and appends the entered data.
- A bug removed which was giving error related to use of 'LONG' - : 1 raw data block (512 bytes) takes 4.15ms for reading or writing (123.37 KBytes/s) at current 4 MHz SPI clock rate.
These transfer rates can be further increased by using a 16MHz crystal (8 MHz SPI clock). : - A bug removed which stopped creating new files after 32*8 files in the root directory - The root directory was unnecessarily getting expanded by one cluster whenever a file was created.
For testing these options, format the card with FAT32 file system and store some directories and text files (because text files can be read & checked thru Hyper Terminal). Now the current date of file creation and file update will be entered in the FAT table (can be viewed by checking file 'properties' using a PC) (The RTC will also be useful in data-logging with time-stamp) - Three more options added in the Hyper Terminal menu for displaying or updating RTC date & time. Ver 2.4.1: - Same as 2.4, with a bug fix for RTC: 'twi_init' function added to define I2C clock freq. This was taking default values earlier, which was as high as [email protected], not desirable (Note: Version 2.2, 2.3 & 2.4 are tested on ATmega32, but they can be adopted to any controller having RAM cards added (tested with San Disk & Transcend micro SD and micro SDHC cards).
I suspect a network driver or network hardware issue, but since I'm already running the latest drivers I'm not sure what to do about it. In response to the comment asking for hardware details, the server is an Intel SR1670HV, which is 1U chassis containing two independent S5500HV motherboards.
Communication is via the motherboards' integrated NICs which are Intel 82574L. I have had a simular problem with Cent OS images on a MS hyper V server.
On those hosts I am running two VM's each running Windows Server 2008 R2 Web edition with SP1.
My storage server is Windows Storage Server 2008 connected via i SCSI.