I have a HW product I designed that has a USB 2.0 interface. I need a Windows based application that uses the USB interface to talk to my HW product. I am writing the code for the USB interface within the HW product. In essence, the Windows application needs to be able to "peek and "poke" any arbitrary memory location within the HW product. I have 64K of 8 bit FLASH in the HW product. The commands to peek and poke are to be defined between me and the Windows developer. WIll keept the extremely simple
Using the peak and poke capabilities of the Windows application, we will then be able to load new program memory in the Flash of the HW application (there will always be a kernal USB code in the first 256 bytes of FLASH).
The Windows application must install very simply for a user, e.g. download a file and load it, no complicated .net files or anything like that.
The Windows application needs some buttons to allow a user to :
1) Select a program file from some location on the PC and load it into the HW application (start location of memory is known and the Windows application just keeps poking date to the HW application until it is at end of the file or an 8K limit is reached.
2) Select a user configuration file from some location on the PC and load it into the HW application (Exact memory locations of the 256 byte file for storage within the HW application are known)
3) Interrogate the HW application and retrieve the existing program and save it into some PC file location (by "peeking" each memory location)
4) Interrogate the HW appication and retrieve the existing user configuration file and save it into some PC file location (by peeking each memory location)
5) Misc buttons to retrieve some exact memory locations from the HW application and display them on the PC (llike SW version, some other parameters,etc).
The Windows application doesn't have to be exotic display with multi colors or graphics, etc. It is a barebones way to load and view data in the HW device.
It needs to run on VISTA or XP platforms.