Announcement

Collapse

Forum etiquette

Our mission ...

This forum is part of our mission to promote the preservation of vintage computers through education and outreach. (In real life we also run events and have a museum.) We encourage you to join us, participate, share your knowledge, and enjoy.

This forum has been around in this format for over 15 years. These rules and guidelines help us maintain a healthy and active community, and we moderate the forum to keep things on track. Please familiarize yourself with these rules and guidelines.


Remain civil and respectful

There are several hundred people who actively participate here. People come from all different backgrounds and will have different ways of seeing things. You will not agree with everything you read here. Back-and-forth discussions are fine but do not cross the line into rude or disrespectful behavior.

Conduct yourself as you would at any other place where people come together in person to discuss their hobby. If you wouldn't say something to somebody in person, then you probably should not be writing it here.

This should be obvious but, just in case: profanity, threats, slurs against any group (sexual, racial, gender, etc.) will not be tolerated.


Stay close to the original topic being discussed
  • If you are starting a new thread choose a reasonable sub-forum to start your thread. (If you choose incorrectly don't worry, we can fix that.)
  • If you are responding to a thread, stay on topic - the original poster was trying to achieve something. You can always start a new thread instead of potentially "hijacking" an existing thread.



Contribute something meaningful

To put things in engineering terms, we value a high signal to noise ratio. Coming here should not be a waste of time.
  • This is not a chat room. If you are taking less than 30 seconds to make a post then you are probably doing something wrong. A post should be on topic, clear, and contribute something meaningful to the discussion. If people read your posts and feel that their time as been wasted, they will stop reading your posts. Worse yet, they will stop visiting and we'll lose their experience and contributions.
  • Do not bump threads.
  • Do not "necro-post" unless you are following up to a specific person on a specific thread. And even then, that person may have moved on. Just start a new thread for your related topic.
  • Use the Private Message system for posts that are targeted at a specific person.


"PM Sent!" messages (or, how to use the Private Message system)

This forum has a private message feature that we want people to use for messages that are not of general interest to other members.

In short, if you are going to reply to a thread and that reply is targeted to a specific individual and not of interest to anybody else (either now or in the future) then send a private message instead.

Here are some obvious examples of when you should not reply to a thread and use the PM system instead:
  • "PM Sent!": Do not tell the rest of us that you sent a PM ... the forum software will tell the other person that they have a PM waiting.
  • "How much is shipping to ....": This is a very specific and directed question that is not of interest to anybody else.


Why do we have this policy? Sending a "PM Sent!" type message basically wastes everybody else's time by making them having to scroll past a post in a thread that looks to be updated, when the update is not meaningful. And the person you are sending the PM to will be notified by the forum software that they have a message waiting for them. Look up at the top near the right edge where it says 'Notifications' ... if you have a PM waiting, it will tell you there.

Copyright and other legal issues

We are here to discuss vintage computing, so discussing software, books, and other intellectual property that is on-topic is fine. We don't want people using these forums to discuss or enable copyright violations or other things that are against the law; whether you agree with the law or not is irrelevant. Do not use our resources for something that is legally or morally questionable.

Our discussions here generally fall under "fair use." Telling people how to pirate a software title is an example of something that is not allowable here.


Reporting problematic posts

If you see spam, a wildly off-topic post, or something abusive or illegal please report the thread by clicking on the "Report Post" icon. (It looks like an exclamation point in a triangle and it is available under every post.) This send a notification to all of the moderators, so somebody will see it and deal with it.

If you are unsure you may consider sending a private message to a moderator instead.


New user moderation

New users are directly moderated so that we can weed spammers out early. This means that for your first 10 posts you will have some delay before they are seen. We understand this can be disruptive to the flow of conversation and we try to keep up with our new user moderation duties to avoid undue inconvenience. Please do not make duplicate posts, extra posts to bump your post count, or ask the moderators to expedite this process; 10 moderated posts will go by quickly.

New users also have a smaller personal message inbox limit and are rate limited when sending PMs to other users.


Other suggestions
  • Use Google, books, or other definitive sources. There is a lot of information out there.
  • Don't make people guess at what you are trying to say; we are not mind readers. Be clear and concise.
  • Spelling and grammar are not rated, but they do make a post easier to read.
See more
See less

Commodore pet 3032 screen full of lines

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #46
    Ui2:
    Pin2: pulse
    pin3: pulse
    pin4: pulse
    pin5: pulse
    pin6: pulse
    pin7: pulse
    pin10: pulse
    pin11: pulse
    pin12: pulse
    pin13: pulse
    pin14: pulse
    pin15: pulse

    ui2 to ui9 pin2: pulse

    ui2:
    Pin8:13,3v
    pin9:5,4v
    pin1:-5,7v
    pin16:0v

    Comment


      #47
      Excellent.

      There doesn't seem to be any stuck signals (so that is good).

      I need to go and check something in the source code - but I am in the middle of something at the moment so I will get back to you shortly.

      The +12 V rail is a little high, but not enough to cause concern.

      Dave

      Comment


        #48
        Quick question. Which version of my PETTESTER are you using? Are you using version 4 (as I pointed you to back in post #27?).

        Dave

        Comment


          #49
          Originally posted by daver2 View Post
          Quick question. Which version of my PETTESTER are you using? Are you using version 4 (as I pointed you to back in post #27?).

          Dave
          Yes,i ve downloaded it from your link

          Comment


            #50
            Pettester 4 in Ud8 with all roms inserted....

            Comment


              #51
              Thanks.

              OK, so you shouldn't get just that screen on startup.

              Can you rig up a manual reset button to your PET please? Either connect a normally-open pushbutton (or switch) across C67 (1uF tantalum capacitor used in the reset circuit) or between pins 7 and 1 of UA2 (8-pin 555 timer IC).

              With the PET turned on, and my test firmware running, can you record a video of the screen after depressing and releasing the reset button/switch. Set the video recording BEFORE operating the manual reset switch.

              The firmware should first display all the characters from the character generator on the screen then verify that they can be read by the CPU.

              The screen is then cleared.

              The next test performs a byte test on the page 0 and 1 RAM.

              The next test performs a 55/AA test on the page 0 and 1 RAM.

              I would like to see how far it gets during its testing.

              Between each test is a delay.

              EDIT: I am just going out for a walk, so I will catch up with your posts when I get back. Also, to keep dave_m happy , I am working on the documentation for the diagnostic firmware...

              Dave
              Last edited by daver2; September 14, 2019, 10:33 AM.

              Comment


                #52
                Originally posted by daver2 View Post
                Also, to keep dave_m happy , I am working on the documentation for the diagnostic firmware...
                Dave,
                Pettest V4 released and to be soon documented. Good boy!
                -dave_m

                Comment


                  #53
                  He he...

                  Documentation week I think.

                  Dave

                  Comment


                    #54
                    Originally posted by daver2 View Post
                    Thanks.

                    OK, so you shouldn't get just that screen on startup.

                    Can you rig up a manual reset button to your PET please? Either connect a normally-open pushbutton (or switch) across C67 (1uF tantalum capacitor used in the reset circuit) or between pins 7 and 1 of UA2 (8-pin 555 timer IC).

                    With the PET turned on, and my test firmware running, can you record a video of the screen after depressing and releasing the reset button/switch. Set the video recording BEFORE operating the manual reset switch.

                    The firmware should first display all the characters from the character generator on the screen then verify that they can be read by the CPU.

                    The screen is then cleared.

                    The next test performs a byte test on the page 0 and 1 RAM.

                    The next test performs a 55/AA test on the page 0 and 1 RAM.

                    I would like to see how far it gets during its testing.

                    Between each test is a delay.

                    EDIT: I am just going out for a walk, so I will catch up with your posts when I get back. Also, to keep dave_m happy , I am working on the documentation for the diagnostic firmware...

                    Dave

                    Good morning,
                    ok i ve added button accross to 555 's pin 1 and 2.
                    This is little video test:

                    https://youtu.be/tSRnz_Z8lHA

                    Thanks

                    Comment


                      #55
                      Pin 1 and 2 for reset. Thanks for the correction.

                      I have a problem with the video in that it is not showing what my PETTEST V4 firmware actually does according to the source code...

                      The first thing that it should do (after a reset) is to fill the screen with copies of the full character set. This is not happening?

                      This could happen for one of three reasons:

                      1. My PETTEST firmware is not compatible with the version of kernal ROM you are using. What part number is on the kernal ROM you are using please? I should be able to duplicate your specific machine setup in VICE and check that it works.

                      2. You have a faulty kernal ROM (the first few instructions that execute following a reset are corrupt).

                      3. You haven't got the kernal ROM installed at all, but another variant of the PETTEST that runs in the kernal socket (as opposed to mine that runs in the EDIT ROM socket).

                      We need to find out which of the above three scenarios we have.

                      Dave

                      Comment


                        #56
                        Originally posted by daver2 View Post
                        Pin 1 and 2 for reset. Thanks for the correction.

                        I have a problem with the video in that it is not showing what my PETTEST V4 firmware actually does according to the source code...

                        The first thing that it should do (after a reset) is to fill the screen with copies of the full character set. This is not happening?

                        This could happen for one of three reasons:

                        1. My PETTEST firmware is not compatible with the version of kernal ROM you are using. What part number is on the kernal ROM you are using please? I should be able to duplicate your specific machine setup in VICE and check that it works.

                        2. You have a faulty kernal ROM (the first few instructions that execute following a reset are corrupt).

                        3. You haven't got the kernal ROM installed at all, but another variant of the PETTEST that runs in the kernal socket (as opposed to mine that runs in the EDIT ROM socket).

                        We need to find out which of the above three scenarios we have.

                        Dave

                        Hi dave,
                        no i can't see full char set in the screen after reset..
                        i have installated 901465-03 kernal ROM in Ud9...i ve tested and verified with eprom programmer and seems to be ok...

                        Comment


                          #57
                          I have configured VICE as follows:

                          -model 4016
                          -kernal ../kroms/kernal-2.901465-03.bin
                          -editor ../V04/PETTESTE2KV04.bin

                          On start-up, VICE tells me that the Kernel is for BASIC 2 based upon the ROM checksum.

                          My PETTEST code correctly starts up and displays the full character set.

                          The checksum I get for the kernel ROM is 7C98.

                          It seems to work.

                          Can you put the PETTEST EPROM into your EPROM programmer and post the first 8 bytes you find at offset $000 within the EPROM and (because you have made two copies of my code in a 2732) the 8 bytes at offset $800 within the EPROM please.

                          Something 'funny' is going on here...

                          Dave

                          Comment


                            #58
                            Originally posted by daver2 View Post
                            I have configured VICE as follows:

                            -model 4016
                            -kernal ../kroms/kernal-2.901465-03.bin
                            -editor ../V04/PETTESTE2KV04.bin

                            On start-up, VICE tells me that the Kernel is for BASIC 2 based upon the ROM checksum.

                            My PETTEST code correctly starts up and displays the full character set.

                            The checksum I get for the kernel ROM is 7C98.

                            It seems to work.

                            Can you put the PETTEST EPROM into your EPROM programmer and post the first 8 bytes you find at offset $000 within the EPROM and (because you have made two copies of my code in a 2732) the 8 bytes at offset $800 within the EPROM please.

                            Something 'funny' is going on here...

                            Dave

                            Ok now i try

                            Comment


                              #59
                              Ok these are the results:
                              a.jpg
                              b.jpg

                              Comment


                                #60
                                I can't see anything wrong with that. As Alice would say "curiouser and curiouser"...

                                Next issue could be that your kernel ROM is (in some way) different to what I am expecting...

                                Each of the different variants of the kernel ROM (and the EDIT ROM) had a different entry point. I have configured my diagnostics to be compatible with all of the known variants of the Kernel ROM I know about. This included 901465-03 for BASIC 2.

                                My diagnostics were originally written for an 8032 with BASIC 4 and (if I remember correctly) a similar thing happened when people used the diagnostics with BASIC 1 and 2 (hence the reason I added the three different entry points into my diagnostic ROM).

                                Can you dump the kernel ROM out you are running please (in HEX) and post it so I can see where it enters the EDIT ROM please. The other option is to get your EPROM programmer to perform a 16-bit checksum on the contents of the ROM. It should match with $7C98.

                                Thanks.

                                I suppose the other problem is that we could have an address, data or ROM selection fault which is causing the diagnostic ROM not to execute correctly?

                                Dave

                                Comment

                                Working...
                                X