![]() |
Re: Ortonview PCB
Quote:
I have made progress, in that I have determined that there are a couple of registers needing clearing before the Ortonview will do anything, but now it seems very unstable. It seems to run sometimes then not at others. If you tap the board, especially in the vicinity of the crystal, it works for a short while except the vertical sync seems to be all over the place. This is with the Ortonview not connected to the MK14. I think there might be more work required to get the configuration fuses working properly, perhaps the oscillator is not starting properly. Its been a long while since I've played seriously with PICs and its taking time to get up to speed with all the intricacies of them. I do recall that at one point Karen decided to move functions from one port to another, I don't recall why but that also might be an issue. I have had a week or so off from the project due to other things but I'll get down to testing it again this weekend, I think I need to check the config settings bit by bit. If anyone wants to look at where I am at the moment its at https://bitbucket.org/IanKRolfe/orto...src/PIC16F887/ (Note: The HEX file in the repository is not the HEX file generated from the latest source, MPLAB squirrels that away somewhere else. I believe the HEX file in the repository is the "vanilla" pic 877 #692 version, so ignore that. |
Re: Ortonview PCB
I’ve been thinking about the issue with the 877A in graphics mode and re-reading the original thread. If I understand correctly the first working code did not have the issue, but then after Karen improved the time available to the 8060 the graphics mode showed the issue. I don’t have any 877A or 887 yet, they are still on my shopping list, but if I read the thread correctly the issue is the shifting of the display by one character pixel left and right in alternate frames. I’m thinking this might have been introduced by an optimisation of the timing of sync signals that Karen might have made, considering she was always quite particular to achieving perfection. Anyway I’m wondering if the graphics mode issue is caused by an odd number of cycles between frames causing an issue with sync of the tx clock in graphics mode with the 877A. I’m assuming here that the 877 resets the prescaler on init of the clocked serial and the 877A does not. I would suggest either adding or removing a single instruction cycle from the vertical synch to see what effect that has, it should still be acceptable synch timing for a tv.
|
Re: Ortonview PCB
Quote:
|
Re: Ortonview PCB
Yes, I think there was a particular 877 port she wanted to use for the databus hence a very late change to the assignment of ports. It coincided with her decision to use the 877 instead of the 887, so, worst case scenario, there may be reason to change it back to the original wiring but still take into account that one of the page select pins also has to operate in a dual mode.
Another possibility is to (reluctantly) change to the PLCC packaged version of the 877 / 877A because that gets you a couple of extra port pins - but they can only realistically be used on a PCB, trying to hand-build without a PCB or at least a pin breakout board would be tedious in the extreme. I do have some '44 pin PIC Demo' PCBs of the type which originally came with the Pickit 3 - we bought a number of those at work but we only really needed the programmers so the boards were up for grabs so I grabbed them. They typically came with PIC16F877 (QFP) versions fitted although they will accept QFP versions of the PIC16F877A, PIC16F887, PIC18F452 etc - but they are fine pitch devices which have to be soldered, of course. |
Re: Ortonview PCB
Regarding the apparent sensitivity around the crystal area when using the 887, I'm sure the crystal 'type' in the configuration setup needs to be 'HS' rather than 'XT' and I recall when first messing about with the 887 that I had to disable the Low Voltage Programming option (LVPDIS in the 'C' source I posted earlier) because otherwise signals and states applied to the programming pins may try to put the chip into program mode. Of course disabling Low Voltage Programming is not helpful if you only have a low-voltage programmer rather than a PicKit2/3, ICD2 or ICD3 etc.
|
Re: Ortonview PCB
Quote:
. I did set the crystal type to HS (or at least, I set them intending that to happen, its always possible I got it wrong, I used the configuration editor on MPLAB and set the config values in the source to match. I should probably use the defined symbols to build up the config values "properly". |
Re: Ortonview PCB
1 Attachment(s)
Quote:
|
Re: Ortonview PCB
Quote:
Code:
CFG1 EQU _DEBUG_OFF & _LVP_OFF & _FCMEN_OFF & _IESO_OFF & _BOREN_OFF & _CPD_OFF & _CP_OFF & _MCLRE_ON & _PWRTE_OFF & _WDTE_OFF & _FOSC_HS Code:
ORG 0 When I've checked this out and the signals seem plausible I will try connecting it up to the MK14 again. |
Re: Ortonview PCB
Running parallel to Slothie's (possibly) continuing efforts on the software side, I am finally getting my lardy **** into gear and making up Mark's little 74HCT74 patch for the 'occasional RAM corruption' problem. Should be 'installed' by the end of the week with any luck.
|
Re: Ortonview PCB
I've kind of dropped the ball on this one as well for the last few weeks, I've lost track of where I put my logic analyser module (its somewhere "safe") and I need to find the time to do a search......
|
Re: Ortonview PCB
A question for Mark or for Slothie who has already added this patch - can you confirm that the insertion point for the patch is between the 877 pin 7 and D4 anode, or to be precise
- Cut the connection between [877 pin 7] and [D4 anode / redundant U1D buffer enable gate] - Connect from 877 pin 7 to 74HCT74 pin 12 - Connect from 74HCT74 pin 9 to D4 anode / redundant buffer enable gate. The following connections obviously also have to be picked up +5V power and 0V CLK OUT (actually clock in, from the MK14) NADS |
Re: Ortonview PCB
1 Attachment(s)
I found this in my notebook, if its any help, it shows the 74HCT74 from underneath.
|
Re: Ortonview PCB
3 Attachment(s)
Hi Sirius
Attached pictures of my mod, hope I didn't reduce the resolution too far, pin 7 cut before it reaches the via, I used this location so I was clear of other traces in case I slipped, also seemed like a good place to repair the cut if I needed to later. Pin numbers on the 74HCT74 might be different. Try not to be confused by the additional circuit, this was to remove the white bar down the let edge, but the wire lengths introduce noise in the video output. Are you trying the first or second version of the mod? I think the second one is better as it should also work with the standard crystal. Mark |
Re: Ortonview PCB
1 Attachment(s)
Just realised I cropped the view of the back of the mod to miss the 74hct74 for delay in NADS.
|
Re: Ortonview PCB
Quote:
I had considered cutting / drilling the tracks going to one of the noise generator IC pad positions and placing the IC there but I suspected Slothie might be inconsolable if I did that, so I've built mine on the shiny side of a small square piece of stripboard which I can stick down on any conveniently bare part of the PCB. I've used the circuit and IC pin numbers as drawn in your drawing of #488. |
Re: Ortonview PCB
I'm not aiming to include the white line blanking mod at the moment - one baby step at a time.
|
Re: Ortonview PCB
You are trying the circuit from #488 and not the earlier #466?
Just want to make sure we are talking about the same circuit. |
Re: Ortonview PCB
If I want to try the PIC16F877A instead of PIC16F877, do I need a different build of firmware or can I use the same firmware as the PIC16F877?
I have a couple of 877A and 887 now, so interested in duplicating the graphics mode issue with the 877A. I’ll wait for Slothie before I try the 887. |
Re: Ortonview PCB
Quote:
There is no specific 'fork' of the firmware for 877A, we made a decision along with Karen just to declare that the project only worked with the 877 and not the 877A. Trying to fix that problem was taking up far too much of the little time and energy she had left. If you put the same firmware in an 877A it will work almost normally but in graphics mode the whole image appears to jump from side to side by about a pixel width on every successive frame. One reason for trying to get the code to run in an 887 is to see whether this problem is also present when that chip is used. |
Re: Ortonview PCB
Quote:
When the time comes of course it will be on the PCB, as there will be plenty of room without the buffers which have proved unnecessary. I'd like to see if there are any changes required to get the 887 working first even though that is unlikely. I really must get my mojo going on this one! |
All times are GMT +1. The time now is 7:20 pm. |
Powered by vBulletin®
Copyright ©2000 - 2023, vBulletin Solutions, Inc.
Copyright ©2002 - 2023, Paul Stenning.