VoyForums
[ Show ]
Support VoyForums
[ Shrink ]
VoyForums Announcement: Programming and providing support for this service has been a labor of love since 1997. We are one of the few services online who values our users' privacy, and have never sold your information. We have even fought hard to defend your privacy in legal cases; however, we've done it with almost no financial support -- paying out of pocket to continue providing the service. Due to the issues imposed on us by advertisers, we also stopped hosting most ads on the forums many years ago. We hope you appreciate our efforts.

Show your support by donating any amount. (Note: We are still technically a for-profit company, so your contribution is not tax-deductible.) PayPal Acct: Feedback:

Donate to VoyForums (PayPal):

[ Login ] [ Contact Forum Admin ] [ Main index ] [ Post a new message ] [ Search | Check update time | Archives: 1, 2, 3, 4, 5, 6, [7], 8, 9 ]

[ Next Thread | Previous Thread | Next Message | Previous Message ]

Date Posted: 09:56:13 03/03/02 Sun
Author: Gaz
Subject: Re: PAL B/G decoder PT - Starting
In reply to: A coupla words.. 's message, "Re: PAL B/G decoder PT - Starting" on 09:34:24 03/03/02 Sun

Some how i was suspicious about that, but ok, i will give it a try to C, it's just because i think it's very hard to most of the people understand assembler, and i don't know if it's possible to make good programming for a PIC like 16F84 using a more accessible language then assembler.
Thanks a lot for your words, i think they come to meet the kind of spirit i was expecting here, that we help each other with our knowledge and experience.

And this is for all the people in general ... send your ideas, critics, sugestions ... let's talk about this openly, don't be shy, and don't be afraid, remenber that learning is not a crime!

Greatings
Gaz

>The SX's have a difficult programming algorithm
>compared to the standard microchip pics and I had some
>setbacks until I built the 'fluffy' programmer - no
>problems since but it's more complex than the 'JDM'
>type interface.
>Writing the software in C may cause timing problems
>and you'll have to pick over every line of the
>assembly output to ensure extra cycles have not been
>added or subtracted in critical routines (most of
>them) - if you're using the 3chip approach that is. As
>you'll find, being 1 cycle out (20MHz) can be enough
>to make the difference between good picture and no
>picture.
>I've got nothing against C but the executable it
>produces is ultimately assembly language and the
>lowest level is where you'll be working with this type
>of application especially when troubleshooting the
>code.

[ Next Thread | Previous Thread | Next Message | Previous Message ]

Replies:

[ Contact Forum Admin ]

Forum timezone: GMT-8
VF Version: 3.00b, ConfDB:
Before posting please read our privacy policy.
VoyForums(tm) is a Free Service from Voyager Info-Systems.
Copyright © 1998-2019 Voyager Info-Systems. All Rights Reserved.