Hi,
Could someone help me with that question pls ? Can I use an ulink2 for that or do I need an ATOCD51 and if, where to purchase that device ?
Thx, Tom.
I do not know of the latest versions of the Rx2, but If there is not a major change, you will need an ICE to debug that chip.
The only '51s I know of that have "built in" debug are the SILabs offerings.
Erik
Hey guys,
Thx btw for the replies - but please read the question, understand it and post a reply only if you really got it. The AT89C51RE2 has two dedicated OCD lines (RxD, TxD). This has NOTHING to do with an ICE or serial monitor debugging, sorry guys. There is a dedicated device called ATOCD51 debug adapter to connect via USB to that lines and afaik the ulink/ulink2 hat a plug for 51-2 pins OCDS internally as well. So, my question is: Does the ulink2 support this derivate as well or do I need the dedicated ATOCD51 adapter. It comes in the same housing, just different labeling on it...
thx and sorry if I could not make my question totally clear in the first run...
tom ;o).
Have you asked Keil sales/support?
Have you asked Atmel?
Atmel do seem strangely reticent about the on-chip debug on their 8051 products. probably something they added to the hardware and a) found out it does not work (as a non-invasive debugger should) b) decided not to invest in the software required to use it
So, I've got the ATODC51 debug adapter up and running with the AT89C51RE2 but encountered an always crashing debug session when the TWI of my uC gets activated by writing the Enable bit in SSCON register :-(. Atmel support is not responding on that issue, even I sent them a uVision project to reproduce that behaviour.
May be anyone else run into the same problem and already solved it ???
The other strange thing is that you have to load the application using the batchisp utility first and then connect the debugger afterwards. Performance is poor when loading the application, it takes approx. 1,5 minutes to load 90k code (binary size). Oh, I miss my Cortex micros and the quick build-debug cycles so much...
Any help/ideas appreciated, thx.
Tomas.
I don't use the ATOCD51, but there is currently a serious bug in S8051.dll, causing debugger crashes. I already got a fixed version from the support staff, but it is not yet included in the latest release (at the time of writing: 9.51a).
So either wait for the next release or ask the KEIL support for S8051.dll with version >= 3.86.0.0 and see if that helps.
Hi Rene,
could you send me an email pls to keep in touch ? tom@tktronic.de
cy, tom.
I have a question for you...
I'm have c8051f330 and c8051f392 from silabs and I want to debug them with the Ulink2 (I'm using uVision3 and I just ordered the uLink2).
Do I only have to connect the C2D(C8051 serial data) to the TMS(JTAG 10 pin connector) and the C2CK(C8051 serial data clock) to the TCLK(JTAG 10 pin connector)? I cant find any instructions on how to set them up together in order to debug using uVision... Is the 51-2PIN connector would be what I want to hook my uC after?
Thanks in advance for the answer :)
Phil
Tom, Rene
Did you manage to solve the crashes? Need to make a decision between the AT89C51RE2 and Cortex processors, would prefer the AT89C51RE2 with my 8051 background, but an in-circuit debugger is a must!
Deon