Running WASP on Win7 or win XP with ADuC842 SAR eval Rev A4.
The hex file loads, I select TEMP sensor and hit RUN.
WASP just hangs.
The WASP performs two separate functions
1) Download of the routine that it will communicate with later to perform the WASP-ish tasks.
2) Communicate with the downloaded routine via the UART.
The USB-EA dongle is only suitable for download (and debug), and is not a USB->Serial bridge as you might first consider it.
Therefore it only accepts the download commands and doesn’t pass the WASP commands through to the board.
You can use this USB-EA dongle to download using WASP, however that is all. It is not suitable for the WASP function and you will need to use the cable that I am using in the video.
I will need to set up a system and see if I can reproduce this.
Can you confirm the version of the WASP software you are using?
Tried both Wasp 6.02 and 6.04 (with FTDI drivers v2.08.12) with same result.
There appears to be a newer version - 6.1 - on the ftp site.
I will try this version first and see if I see the same as you.
Just loaded and tried 6.1 - same thing.
I tried this this morning, and it worked for me on a Windows 7 PC with Administrator privileges.
I found however that if the communications parameters were incorrect, or the routine that communicates to the PC program was not downloaded that it would not respond.
I recorded my session; maybe you are not following one of these steps. See attached video clip for details but you need the following steps at a minimum
I've downloaded the bin multiple times, from multiple PCs, clean PC and dev PC.
Selected the correct MCU
It says the bin is downloaded.
It just hangs.
Are you using the same board (ADuC842 SAR eval Rev A4.\) ??
Looking at the video, you are using a different board (mine does not have a white 4 pin connector next to the USB dongle).
In addition, the dongle shipped with the board is not the same as the one you are using. Mine has an additional 2 pin EA lead.
WASP 6.1 does not even let you download the bin with the dongle unless this EA connector is connected.
Hmmm, so basically the dev kit as shipped (with dongle) doesn't work out of the box ??
It also doesn't work very well with the IAR compiler. I wrote a program that included printf output and sure, I do get the output, but it is really slow - even at 115200 the chars come out about 1 per second.
In addition, the run/break cycle time is incredibly slow. I'm used to debugging 8051 systems on TI CC radios and get infinitely better debug latency.
Perhaps the ADuC chips have no hardware breakpoints??
The ADUC8xx do not have any hardware breakpoints, and are implemented using the opcode substitution (software breakpoints).
The serial cable that comes with the kit should be used for serial communications. The USB dongle is for debugging only, I don’t know what performance to expect when using it as a COM port for serial communications and not sure if I expect it to even work that way.
Is that what you are using and getting such slow communications with?
Retrieving data ...