I have a hardware named wiggle..It can be used in iar,ads,realview....but how to use it with keil arm? thanks a lot!
Sorry, but we do not support WIGGLER since the software interface does not work on modern PC's (XP, Laptop, ect). Instead, we provide a low-cost, but high-speed USB based ULINK USB-JTAG Adapter that works for ARM and several other devices. For more information see: http://www.keil.com/ulink
I don't know what is "does not use in modern pc(xp etc)? wiggle is $1 but ulink is $199.....
It is possible to write AGDI DLL with support of Wiggler for Keil ARM. And then to debug programs over OcdLibRemote. There was an application note(apnt173?) for ARM devtools. But it is necessary to spend some time (or lot of $$$) to write such DLL :)
I don't know what is "does not use in modern pc... Well. Back in the old days, the PC's parallel printer port interface was constructed using discreet hardware components. I don't recall the part number but it was a PIO or a PIA or something like that. The PC could read and write to this thing and the signls went out and came in the parallel port in exact response to CPU instructions. Current computers do not implement parallel ports the same way anymore. In many cases, the parallel port interface (the old PIO) is simulated in the motherboard ChipSet. The problem is that there is a timing delay between the instructions that talk to the interface and the data actually going in or out the parallel port. Now, this is not a problem for most talking to a slow printer. But, when you use the parallel port to interface a high-speed communications devices, errors can and do occur. And, these kind of problems are extremely difficult to diagnose. Aparently, HP has had a lot of trouble with chipsets and have documented their discoveries at http://www.computer-and-printer-reviews.com/hp-printer-drivers.html. The real problem is that convincing a customer that this is REALLY the problem sounds like you don't know the answer and are trying to blame the customer's computer or operating system or something like that. And, when the customer has a lab full of the same PC with the same problem it's even more difficult. I've been lucky. Of my last 8 PCs/Laptops, all of the PCs worked fine but 2 of the laptops parallel ports never worked with wigglers/device programmers. Jon
The problem is that there is a timing delay between the instructions that talk to the interface and the data actually going in or out the parallel port I believe that some of that, in addition to hardware changes, is courtesy of Mr. Gates. When Windows abandoned the DOS base, the I/O became "real enough time" (which for many things in not "real enough") instead of real time. The same apply to the RTOSs that really should be name URTOS, since the "real enough" "philosophy" apply there as well. It is sad when some developer somewhere decide what is real enough for you. Erik
my best thanks to Alexey Selishev ,Ward Jon and erik malund ! thanks you give more good advise.I think many beginer's need is a sample wiggle link with pc's parallel port. so a sample and chip wiggle and a dll can used in keil ........I think Keil's AGDI is a good solution.but i'll find it until it appear in the internet!:))
now I use IAR EARM 4.11 and a sample wiggle to debug my program.but i think keil and a dll can use wiggle is the best choice
anybody can help me ????God to sale ulink to get more money !!!
"God to sale ulink to get more money !!!" Do you mean you need to sell your uLink? If so, How about eBay?