Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Jan Waclawek

#106
> Try this:
>
> DEVICE(89C51RD2Hxx, -1.000)

Now THIS is something I call a HACK !!!  :)

JW



Post Edited (06-09-06 01:57)
#107
Alex, you are right, sorry. I haven't really tried, just had a look at it... But Andy recently published a "hack" here: http://www.esacademy.com/software/flashmagic/forum/read.php?f=1&i=2815&t=2815

Other - maybe stupid, too - thing came into my mind, couldn't you simply cut the DTR line in the cable?

Jan Waclawek
#108
This sounds similar than my question here a few days ago. Fortunately, the status quo suited my purpose well; but I investigated this a little bit then, and now I am uncertain: couldn't this be solved somehow by using the commandline version of FM (using the HARDWARE option)?

Jan Waclawek
#109
P89V51Rx2/P89LV51Rx2 / Re: Problem with P89V51RD2FA
June 06, 2006, 11:50:25 PM
Can you try to make a very simple program, such as flashing a LED, to detect if the proper file gets "burned" and is running?


Jan Waclawek
#110
P89V51Rx2/P89LV51Rx2 / Re: Problem with P89V51RD2FA
June 06, 2006, 03:09:41 PM
Is there any indication that your "keypad" program is actually running?
E.g. some LEDs flashing etc.

Jan Waclawek
#111
P89V51Rx2/P89LV51Rx2 / Re: Problem with P89V51RD2FA
June 06, 2006, 06:53:53 AM
> This problem is coming in the the terminal program only. When I insert
> the first chip, it.s working
>
> No communication is taking place, the chip does not responds.

I don't understand. Are you trying to get into the bootloader mode using a terminal emulator?

Please elaborate.

Jan Waclawek
#112
P89V51Rx2/P89LV51Rx2 / Re: Problem with P89V51RD2FA
June 06, 2006, 04:32:07 AM
#113
P89V51Rx2/P89LV51Rx2 / Re: P89V51RD2 and RTS/DTR
June 05, 2006, 08:02:25 AM
Thanks.

Jan Waclawek
#114
P89V51Rx2/P89LV51Rx2 / P89V51RD2 and RTS/DTR
June 05, 2006, 04:22:46 AM
Hello all,

Is the behaviour of handshake signals (RTS, DTR) defined in FlashMagic when device is set to P89V51RD2 (i.e. the Advanced options->Hardware config is blank)?
I observed that after clicking on "Start" (and the "Reset device etc." windows comes up), RTS gets asserted, but can I rely on this (e.g. for "parasitic" supply from RS232)?

Thanks,

Jan Waclawek
#115
What is your crystal/oscillator value and which baudrates did you try? What is the serial cable length? Can you also please describe the programming procedure you use?

Jan Waclawek
#116
I'd guess some weird reset circuit, rather.
However, if you are able to get the chip into ISP mode "manually" (getting it to echo the 'U's), you might leave Hyperterminal in that moment andrun FlashMagic to do the rest (or program it in Hyperterminal if you dare to do so).

Jan Waclawek
#118
Feature Requests / Re: ISP software in linux
May 06, 2006, 03:19:48 PM
A blind guess: do you set the oscillator frequency value in your software?

Jan Waclawek
#119
Andy,

Can't this be made public? Philips published the _sources_ of the bootloader (as a part of one of the appnotes), so I doubt they would object...

Jan Waclawek
#120
What I do with P89V51RD2 (when 'integrity of serial line is fine' :-) ) is:
- run my favorite terminal program (for this purpose it is terminal by Bray)
- set to 9600Baud*, 8N1, no handshake
- click in "transmit" window
- hold down shift-U
- reset P89V51RD2
It should start echoing U. If not, "integrity of serial line" is "not fine", or mcu is not working (incorrect power (including ground!), reset, crystal/oscillator, /EA - all measured directly on pin; less likely chip set to SoftIce mode**, erased bootloader flash or irreversibly damaged).

---
* for exotic and low crystal values, less is required. Search for my "autobaud error" document.
** if this is the case (you already run FlashMagic successfully and set SoftIce mode accidentally, or programmed the chip accidentally as a different type) remedy available, search for my older contributions here