Failed to get this digital clock kit working :(

[Michael GilliganParticipant @michaelgilligan61133]

Thanks for the thought, Martin, but [so far asI’m aware] it’s not a Pic

… and I really don’t want to try to learn a whole system for the sake of two chips.

I’m struggling enough with the easy stuff.

MichaelG.
 

.

Edit: __ for what it’s worth

AT89C2051 Product details

Description The AT89C2051 is a low-voltage, high-performance CMOS 8-bit microcomputer with 2K bytes of Flash programmable and erasable read-only memory (PEROM). The device is manufactured using Atmel’s high-density nonvolatile memory technology and is compatible with the industry-standard MCS-51 instruction set. By combining a versatile 8-bit CPU with Flash on a monolithic chip, the Atmel AT89C2051 is a powerful microcomputer which provides a highly-flexible and cost-effective solution to many embedded control applications.   Features • Compatible with MCS®-51Products

Edited By Michael Gilligan on 25/02/2023 22:51:59

[Martin KyteParticipant @martinkyte99762]

I did get the message you had given up with the clock. PicKit info posted as a response to Duncan and a general bit of info for anyone who might find it useful.

regards Martin

[Michael GilliganParticipant @michaelgilligan61133]

Posted by duncan webster on 25/02/2023 21:54:24:

Michael, I could lend you the programming device k assuming it's a Pic) but I'd not know how to use it. Mine came with a load of other stuff, and is too good to throw away

.

Sorry, Duncan … I missed the fact that it was you making the offer

I was too busy trying to respond to Martin

MichaelG.

[duncan webster 1Participant @duncanwebster1]

I've no doubt that the code in Michael's link of 11/05 works, but it is making heavy weather of it. If you drive all 8 segments from one port you can tell it which character to write by putting portA = 0b01010101 or similar instead of the 8 lines for each character. Faster as well, not that it probably matters

[Michael GilliganParticipant @michaelgilligan61133]

Good morning folks …

I now see that I managed, last night, to mess-up the cosmetics of this thread by copying and pasting text from a web-page.

… The old ‘text running under the adverts’ trick.

… Might have been better to not bother

MichaelG.

[SillyOldDufferModerator @sillyoldduffer]

Posted by Michael Gilligan on 26/02/2023 06:55:51:

Good morning folks …

I now see that I managed, last night, to mess-up the cosmetics of this thread by copying and pasting text from a web-page.

… The old ‘text running under the adverts’ trick.

… Might have been better to not bother

MichaelG.

I found the thread interesting as an example of the need to get everything right!

Someone has designed a circuit, and a pcb, and bought and packaged all the components for a reasonable kit. They wrote a clock program in PIC Assembly language, and tested it on a prototype.

All good until someone made a basic mistake by sending the PIC chip supplier the program's source code rather than the compiled machine instructions. Thus large numbers of PIC chips loaded with duff code and sent out.

A rough rule of thumb in IT Projects, and it's generally true of all new design, it that the cost of fixing a mistake multiplies by 10 at each successive stage. Errors detected on the drawing board are cheap and easy to fix; the same mistake discovered by customers in the final product can cost millions to fix, perhaps more than the product sold for. Product recalls are horrifically expensive, involving substantial organisation, paying transport costs at retail-rates, dealing with items lost or damaged in transit and other complications. Often better to send a replacement, go bankrupt, or hide under the bed.

Dave

[Michael GilliganParticipant @michaelgilligan61133]

Addendum: [might be useful to someone, sometime]

**LINK**

https://github.com/ruthsarian/at89c2051_clock

MichaelG.

[Author]

Posts