The Proto Board with my GPS Data Logger that I had errors trying to run ViewPort...it's got a 6.25Mhz crystal!!! No good for native Viewport, but hardware platform was changed and every thing is A-OK.
Hi,
Hover1- I'm so happy your problem was due to the 6.25MHz crystal- let's just say I didn't sleep much last night.
So, we're back to Thomas who has had success with ViewPort with the DemoBoard but not his own creation.
I'll do some experiments with DIP's and see if there's anything critical.
Hanno
ps- Since getting the clock constants right is the most common ViewPort problem, I'll work on getting that fixed.
Option 1: more intelligence in the conduit conduit, so it doesn't require the clock constants.
Option 2: When ViewPort is used to load the Propeller, it parses the Spin file and displays the crystal speed somewhere. If the communication doesn't work, it gives a much better error message that says: "your program specifies a 5Mhz crystal does that match your hardware"? Of course if I do this, ViewPort could also modify these constants...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Co-author of the official Propeller Guide- available at Amazon
Developer of ViewPort, the premier visual debugger for the Propeller (read the review here, thread here), 12Blocks, the block-based programming environment (thread here)
and PropScope, the multi-function USB oscilloscope/function generator/logic analyzer
Option 3: Operator being a little more observant of his own creation!
(I like your Option 2)
I would think the best place for Thomas to start is moving the programing header onto the board containing the Prop, as Graham has suggested. It's hard to see his wiring in his picture.
Since an overview of ViewPort is included with the PEKit documentation, and seems to work without decoupling caps at the Prop, I think that can be ruled out. (But I think the documentation should include the caps for building more critical circuits later on).
Comments
The Proto Board with my GPS Data Logger that I had errors trying to run ViewPort...it's got a 6.25Mhz crystal!!! No good for native Viewport, but hardware platform was changed and every thing is A-OK.
(I was wondering which board that crystal was in)
Jim
Hover1- I'm so happy your problem was due to the 6.25MHz crystal- let's just say I didn't sleep much last night.
So, we're back to Thomas who has had success with ViewPort with the DemoBoard but not his own creation.
I'll do some experiments with DIP's and see if there's anything critical.
Hanno
ps- Since getting the clock constants right is the most common ViewPort problem, I'll work on getting that fixed.
Option 1: more intelligence in the conduit conduit, so it doesn't require the clock constants.
Option 2: When ViewPort is used to load the Propeller, it parses the Spin file and displays the crystal speed somewhere. If the communication doesn't work, it gives a much better error message that says: "your program specifies a 5Mhz crystal does that match your hardware"? Of course if I do this, ViewPort could also modify these constants...
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Co-author of the official Propeller Guide- available at Amazon
Developer of ViewPort, the premier visual debugger for the Propeller (read the review here, thread here),
12Blocks, the block-based programming environment (thread here)
and PropScope, the multi-function USB oscilloscope/function generator/logic analyzer
Option 3: Operator being a little more observant of his own creation!
(I like your Option 2)
I would think the best place for Thomas to start is moving the programing header onto the board containing the Prop, as Graham has suggested. It's hard to see his wiring in his picture.
Since an overview of ViewPort is included with the PEKit documentation, and seems to work without decoupling caps at the Prop, I think that can be ruled out. (But I think the documentation should include the caps for building more critical circuits later on).
Jim