When I get back home tonight I'll try your latest program and see if I can replicate your results. There are a bunch of messages here, so I'm just want to clarify a couple of details:
1 - What board are you working on?
2 - What Sx chip? SX28, 48, or 52?
3 - What is your clock soource when the key is not attached?
3 - What is your clock soource when the key is not attached?
No external resonator. It doesn't matter what the clock source is other than it starting in Sleeping or Running mode and never even once Idle mode (as it is suposed to be).
Sorry about my error in 5.1; I should have said ctrl-I instead of ctrl-L.
When triggering the DEBUG command, your configuration appears instead to be effecting the PROGRAM/RUN command instead of the DEBUG command. It blows away (or never generates) the the extra instructions required for debug at locations $777 through $FFF. Very strange indeed.
And does your sytem show the greyed-out areas immediately after·opening the "DEVICE VIEW" window, or only after making some modification in that window such as moving the memory slider.
I was able to get something similar to happen (but not identical), and I wanted you to perform exactly the same steps I was for a comparison. In my case I CAN get the debug code to be generated, but then only to have the IDE blow it away.
I'm trying to get enough info together to cause the problem under the most simple circumstances possible so that PJMonty can have the easiest go at figuring out this problem. I have'nt got to that state yet.
I don't think your SX-Key is damaged; in that case I would expect very different results.
For curiosity, do you have the identical problem if you use the IDE Version 2.3 or the Version 28L ?
The grey out does not happen on the DEVICE window (ctrl-I) until I move the scroll bar down 1 click.
I'm glad to hear that you do not beleive that the SX Key is damaged.
I don't know how to get an older IDE such as 2.3 or what is 28L (another version of the SX-28?).
The first DEVICE line in the code says:
DEVICE············· sx28l, oschs3
Is this where the 28L that you are refering to comes from? I can change it to sx28 (from sx28l) and it still is "Running" when the DEBUG button is pushed.
Are you saying that I should load an older version of the SX-KEY v2.3 from my current version 3.10 ?
Another option would be to arrange with someone here in Tech Support to send us your code, then call in and actually try this step-by-step.· We could compare results on our end to see what's going on.· I have to admit, at this point I am kind of lost too.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Chris Savage Parallax Tech Support csavage@parallax.com
I have the day off of work today so I was hoping to call Parallax tech support today too and see if they could find out the problem too. I will keep everyone posted.
This thing is quite obscure so don't be surprised if it is difficult for them to re-create it. I hope to be able to figure the sequence causing it today. After that might be a better time to contact them.
I spoke with Chris Savage (Tech Support) and he refered me to Sales to get a replacement SX-Key. A long story goes along with this so I will try to keep it short.
I bought a new BS2p24 and plugged it into a new Professional Development Board (PDB). It was not recognized on the board. I plugged it into the BOE board and the same problem happened via the RS-232 cable. I spoke with Parallax and they sent me a BS2px (my request - same price) as a replacement.
Sometime later I noticed that·on my·new Professional Development Board that it had a problem that the LED for the power went out. Everything else worked fine other than no power light. I called Parallax and they replaced the board as it was only a week or two old.
Later, I got a call back from Parallax and they said the new but bad BS2p was in a run-away state. I told them that I had a new PDB sent back for the blue power LED going out. They said they would see if that was the problem for the bad BS2p. They stated today that my credit card would be refunded for the same priced BS2px that was sent in replacement of the BS2p24. This tells me that the PDB was bad which probably caused the BS2p24 to also go bad.
This leads me into the final stage in this story.·Since the PDB was bad, then it most likely damaged the SX-Key which now needs to be replaced. I am currently awaiting a call back from Parallax sales to arrange sending me a new SX-KEY (that possibly has it's oscillator circuits damaged). I will have to pay for a new SX-KEY but assume this will be refunded once the information is presented that the PDB was the cause for this extended damage.
Thanks again to Chris and Parallax for their great support!
I will keep everyone posted as to the conclusion to this odd occurance.
Now I am starting to wonder if my problem is with the SX-Key, mine is about a year old, so maybe somewhere along the line, I did a quick fry on the thing, and now it is starting to show subtle problems. Any of you engineers have a quick home test to see if the Key is functioning properly. I guess I will probably have to wait for the new SX-Blitz, since that will be cheaper, and use SXSim as a debugger.
Now I am starting to wonder if my problem is with the SX-Key, mine is about a year old, so maybe somewhere along the line, I did a quick fry on the thing, and now it is starting to show subtle problems. Any of you engineers have a quick home test to see if the Key is functioning properly. I guess I will probably have to wait for the new SX-Blitz, since that will be cheaper, and use SXSim as a debugger.
I tried the new SX-KEY and it still showed "RUNNING" in the Debug window.
Then I noticed the 4 MHz external resonator was plugged in and I shut the power off and removed it. I turned the PDB back on and hit the Debug button and it worked showing "IDLE".
The SX-KEY was aparently damaged possibly due to a bad PDB which may have blown a·BS2p and SX-KEY. Everything has been replaced and all working.
Thanks again to Parallax for supporting their waranty·replacement items.
Comments
When I get back home tonight I'll try your latest program and see if I can replicate your results. There are a bunch of messages here, so I'm just want to clarify a couple of details:
1 - What board are you working on?
2 - What Sx chip? SX28, 48, or 52?
3 - What is your clock soource when the key is not attached?
Thanks, PeterM
1 - What board are you working on?
New - Professional Development Board - Rev B
2 - What Sx chip? SX28, 48, or 52?
SX28
3 - What is your clock soource when the key is not attached?
No external resonator. It doesn't matter what the clock source is other than it starting in Sleeping or Running mode and never even once Idle mode (as it is suposed to be).
Lets try this again...
1. Load your SX source program.
OK
2. Re-program the SX by means of the "DEBUG" (left) icon.
OK
3. Confirm that the unit has entered the "RUNNING" or "SLEEPING" states, please note which one.
RUNNING. See screenshot "Step3.jpg"
4. "QUIT" the debugger.
OK
5. At the topleft of the IDE screen press the "RUN" button which then will open a pop-up.
OK. See screenshot "Step5.jpg"
5.1 From the bottom section of the pop-up press the "DEVICE" (ctrl-L) button, this launches the DEVICE screen.
OK. See screenshots "Step5_1b.jpg" - {Ctrl-L brings up View list not DEVICE !!!}
6. On the pop-up "DEVICE" screen, note all active selections as well as any "grayed-out" selections.
Opened up the DEVICE window using the DEVICE button.
7. Use the meory area slider to zoom down to the bottom end of memory and note if there is code located from $777 onward through $FFF.
7.1 Note if any areas in the window are now grayed out after moving the memory slider.
No grey out differences. See screenshot "Step 7_1.jpg"
8. Press the "READ" button to read the current contents of the SX memory.
OK
9. Re-note all active selections and grey-outs as per 6. above.
Crystal Drive, Reset Timer, Sleep_Clock are Grey-outs.
10. Reconfirm the presence of code from locations $777 through $FFF as per 7. above.
OK
10.1 Re-note if any areas in the window are now grayed out after moving the memory slider.
OK. No changes. See Screenshot "Step10_1.jpg"
11. Please report your findings for 3., 6., 7., 7.1, 9., 10. and 10.1
I hope you can figure this out.
I can't believe I am the first person to see this and no one from Parallax or the forum has seen this??? Amazing.
Sorry about my error in 5.1; I should have said ctrl-I instead of ctrl-L.
When triggering the DEBUG command, your configuration appears instead to be effecting the PROGRAM/RUN command instead of the DEBUG command. It blows away (or never generates) the the extra instructions required for debug at locations $777 through $FFF. Very strange indeed.
And does your sytem show the greyed-out areas immediately after·opening the "DEVICE VIEW" window, or only after making some modification in that window such as moving the memory slider.
I was able to get something similar to happen (but not identical), and I wanted you to perform exactly the same steps I was for a comparison. In my case I CAN get the debug code to be generated, but then only to have the IDE blow it away.
I'm trying to get enough info together to cause the problem under the most simple circumstances possible so that PJMonty can have the easiest go at figuring out this problem. I have'nt got to that state yet.
I don't think your SX-Key is damaged; in that case I would expect very different results.
For curiosity, do you have the identical problem if you use the IDE Version 2.3 or the Version 28L ?
Thanks for your help,
Cheers,
Peter (pjv)
Post Edited (pjv) : 12/19/2005 9:35:22 PM GMT
The grey out does not happen on the DEVICE window (ctrl-I) until I move the scroll bar down 1 click.
I'm glad to hear that you do not beleive that the SX Key is damaged.
I don't know how to get an older IDE such as 2.3 or what is 28L (another version of the SX-28?).
The first DEVICE line in the code says:
DEVICE············· sx28l, oschs3
Is this where the 28L that you are refering to comes from? I can change it to sx28 (from sx28l) and it still is "Running" when the DEBUG button is pushed.
Are you saying that I should load an older version of the SX-KEY v2.3 from my current version 3.10 ?
Thanks for the good work!
Timothy Gilmore
Well, at this point we're still grasping at straws, so trying almost anything different and observing the results is potentially useful.
I still have old versions of SX IDE's on my computer; V1.07 (V28L) and V2.02. I'll attach them, and you can try them and post the results.
Probably you should change the downloaded names to prevent any interference with your normal SX-Key software.
Cheers,
Peter (pjv)
Post Edited (pjv) : 12/19/2005 10:28:06 PM GMT
Using the SX28L program and choosing a READ from the DEVICE window, got code at the lower half of EEPROM space. See screenshot.
I then had to modify the DEVICE info on the program to get the Debug button to program it correctly. See screenshot.
However you can still see that the DEBUG function says "RUNNING".
When I ran the other SXKEY program, here are my results:
·I first got an error (see screenshot) saying it was missing a file.
It would not allow me to continue to DEBUG.
Cheers,
Peter (pjv)
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Chris Savage
Parallax Tech Support
csavage@parallax.com
Still working on it......time has not been much available lately. Hopefully tomorrow we will know the sequence of events that's causing this.
Don't lose faith!
Cheers,
Peter (pjv)
Thanks for the good work - especially you Peter!
This thing is quite obscure so don't be surprised if it is difficult for them to re-create it. I hope to be able to figure the sequence causing it today. After that might be a better time to contact them.
Cheers, and Merry Christmas,
Peter (pjv)
I bought a new BS2p24 and plugged it into a new Professional Development Board (PDB). It was not recognized on the board. I plugged it into the BOE board and the same problem happened via the RS-232 cable. I spoke with Parallax and they sent me a BS2px (my request - same price) as a replacement.
Sometime later I noticed that·on my·new Professional Development Board that it had a problem that the LED for the power went out. Everything else worked fine other than no power light. I called Parallax and they replaced the board as it was only a week or two old.
Later, I got a call back from Parallax and they said the new but bad BS2p was in a run-away state. I told them that I had a new PDB sent back for the blue power LED going out. They said they would see if that was the problem for the bad BS2p. They stated today that my credit card would be refunded for the same priced BS2px that was sent in replacement of the BS2p24. This tells me that the PDB was bad which probably caused the BS2p24 to also go bad.
This leads me into the final stage in this story.·Since the PDB was bad, then it most likely damaged the SX-Key which now needs to be replaced. I am currently awaiting a call back from Parallax sales to arrange sending me a new SX-KEY (that possibly has it's oscillator circuits damaged). I will have to pay for a new SX-KEY but assume this will be refunded once the information is presented that the PDB was the cause for this extended damage.
Thanks again to Chris and Parallax for their great support!
I will keep everyone posted as to the conclusion to this odd occurance.
Thanks,
Timothy Gilmore
Thanks,
Timothy Gilmore
Now I am starting to wonder if my problem is with the SX-Key, mine is about a year old, so maybe somewhere along the line, I did a quick fry on the thing, and now it is starting to show subtle problems. Any of you engineers have a quick home test to see if the Key is functioning properly. I guess I will probably have to wait for the new SX-Blitz, since that will be cheaper, and use SXSim as a debugger.
Ray
Thanks so much to Chris Savage for his work in expediting the new SX-KEY.
Timothy Gilmore
Ray, have a look at this: http://forums.parallax.com/showthread.php?p=564136
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Greetings from Germany,
G
I tried the new SX-KEY and it still showed "RUNNING" in the Debug window.
Then I noticed the 4 MHz external resonator was plugged in and I shut the power off and removed it. I turned the PDB back on and hit the Debug button and it worked showing "IDLE".
The SX-KEY was aparently damaged possibly due to a bad PDB which may have blown a·BS2p and SX-KEY. Everything has been replaced and all working.
Thanks again to Parallax for supporting their waranty·replacement items.
Timothy Gilmore