Why don't you add printing of the return value from cognew() so you know which cog actually started? Doesn't PST require a cog? That might explain why 7 didn't start.
I think you are right about cog 7 not starting but cog 4 does not start for sure. I have tested this same code on my Prop breadboard and all cogs start up. Maybe I have a bad Prop? It was brand new when I popped it in an started programming...
Ok, I redid the cog tester and it is a little more informative now. All cogs start on my breadboard. Cog #5 according to the tester does not work. Guess I am going to have to buy more Props
Ok, I redid the cog tester and it is a little more informative now. All cogs start on my breadboard. Cog #5 according to the tester does not work. Guess I am going to have to buy more Props
To have one cog that has "failed" is the least likely of almost any scenario, just don't be so quick to point the finger unless it is at yourself. It will be your software, and you know it. As for testing "cogs" it is easy enough to load some other software onto the Prop which can check this out rather than relying on the very code you are debugging, but once again, it is NOT going to be a faulty cog.
Hmm. I am confused I pulled out the Prop from the socket of my circuit board and installed it in my breadboard where the other Prop was and cog #5 failed as it did in the other circuit. The Prop that was replaced with the "Bad" Prop was in the same circuit and all cogs started. If it is software, how?
EDIT * : I just installed the Prop that "Passed" into my circuit board and all cogs started using the cog tester I made. I then loaded the full suntracker code into it and all works...well, except for the socket data part which I started a new thread on
Hmm. I am confused I pulled out the Prop from the socket of my circuit board and installed it in my breadboard where the other Prop was and cog #5 failed as it did in the other circuit. The Prop that was replaced with the "Bad" Prop was in the same circuit and all cogs started. If it is software, how?
EDIT * : I just installed the Prop that "Passed" into my circuit board and all cogs started using the cog tester I made. I then loaded the full suntracker code into it and all works...well, except for the socket data part which I started a new thread on
Okay, I'm sticking by what I said about it's not a failed cog, despite this "indication" that it could be. I still think you have power problems that aren't showing up and one Prop may just work and another may just fail. As I said before the failed cog scenario is a very unlikely, they just don't fail and if any part of the Prop was stressed by over-voltage etc then we normally find that the weakest link breaks first, that is, the PLL. If you loaded my "Hardware Explorer" onto your board you could very easily test out cog 5 etc. For instance:
Comments
Also, BYTE cog[7] should be BYTE cog[8].
Sapphire is correct, Cog 7 does not start because there are no more free cogs.
To have one cog that has "failed" is the least likely of almost any scenario, just don't be so quick to point the finger unless it is at yourself. It will be your software, and you know it. As for testing "cogs" it is easy enough to load some other software onto the Prop which can check this out rather than relying on the very code you are debugging, but once again, it is NOT going to be a faulty cog.
EDIT * : I just installed the Prop that "Passed" into my circuit board and all cogs started using the cog tester I made. I then loaded the full suntracker code into it and all works...well, except for the socket data part which I started a new thread on
Okay, I'm sticking by what I said about it's not a failed cog, despite this "indication" that it could be. I still think you have power problems that aren't showing up and one Prop may just work and another may just fail. As I said before the failed cog scenario is a very unlikely, they just don't fail and if any part of the Prop was stressed by over-voltage etc then we normally find that the weakest link breaks first, that is, the PLL. If you loaded my "Hardware Explorer" onto your board you could very easily test out cog 5 etc. For instance: As you can see I launch some very simple counting code into cog 5 and it checks out fine. This check took me a whole 30 seconds to run.