Yes, every time ... fast or slow download. I wrote a loader before using the Win32 API and had a similar problem ... seems to have been a timing issue.
Brad & jazzed: I do not see this problem. I am using Vista and the bst IDE.
However, I do see that often the prop is not recognised, even after a previous download. I am not using your latest version which may correct this. I am just about download the latest version on my XP machine, so I will let you know how it goes.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Links to other interesting threads:
The latest bst ide version 0.18.4 on XP will not recognise the usb port although PropTool does. The USB is on COM18. So, I downloaded the latest test version 0.18.5-Pre3 and it finds the usb on com18 without problems. As I have not yet done enough testing, I am unsure if it will have intermittent download errors as 0.18.5-Pre1 does on Vista.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔ Links to other interesting threads:
The latest bst ide version 0.18.4 on XP will not recognise the usb port although PropTool does. The USB is on COM18.
Builds up to and including 0.18.4 had a bug in my Win32 serial routines that prevented it seeing ports > 8. I incorporated the fix in 0.18.5-pre2.
There are a number of load/program fixes in there, but none specific to detecting the propeller on Windows that I can think of.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
I'm trying out bst.exe for the first time.· (0.18.5-Pre3)
The first time I try to find the Prop chip (F7), it is located just fine.· Thereafter it cannot find the Propeller until I unplug and replug the USB cable (I'm using a PropStick).· Am I missing a setting somewhere?
I'm trying out bst.exe for the first time. (0.18.5-Pre3)
The first time I try to find the Prop chip (F7), it is located just fine. Thereafter it cannot find the Propeller until I unplug and replug the USB cable (I'm using a PropStick). Am I missing a setting somewhere?
G'day Bob,
What operating system are you using?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
I'm trying out bst.exe for the first time. (0.18.5-Pre3)
The first time I try to find the Prop chip (F7), it is located just fine. Thereafter it cannot find the Propeller until I unplug and replug the USB cable (I'm using a PropStick). Am I missing a setting somewhere?
G'day Bob,
What operating system are you using?
Duh.· Win XP Professional· Version 2002 Service pack 3
Bob Anderson said...
[noparse][[/noparse] Win XP Professional Version 2002 Service pack 3
Ok, I can get my hands on one of those.
Can you go to Tools->IDE Preferences->IDE Preferences->Configure Ports
and see if :
A) your propellers com port is there the box down the bottom has that com port listed
C) Port Select : Says "Manual"
D) when you click "find prop" it actually does?
Try clicking "Find Prop" a couple of times in a row. Does it detect the propeller every time?
If you add/remove a port you need to close/open the port configuration box (or click "Rescan"), it only looks at the available ports when it is opened up.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
jazzed said...
Yes, every time ... fast or slow download. I wrote a loader before using the Win32 API and had a similar problem ... seems to have been a timing issue.
Nevermind, I can reproduce this locally. It was a logic error in the error reporting code. That message should never have been printed.
Unless you need it fixed urgently, I'll let it slip out with the next update.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Bob Anderson said...
[noparse][[/noparse] Win XP Professional Version 2002 Service pack 3
Ok, I can get my hands on one of those.
Can you go to Tools->IDE Preferences->IDE Preferences->Configure Ports
and see if :
A) your propellers com port is there the box down the bottom has that com port listed
C) Port Select : Says "Manual"
D) when you click "find prop" it actually does?
Try clicking "Find Prop" a couple of times in a row. Does it detect the propeller every time?
If you add/remove a port you need to close/open the port configuration box (or click "Rescan"), it only looks at the available ports when it is opened up.
A) through D) work fine after an unplug/replug.· Find Prop works repeatedly.· See BST-test1.png
Then I try F7, it may work once (or twice) then I get BST-test2.png.· After that, Prop can never be found until I go throught the unplug/replug sequence.
Does the "Serial Receive" led on the propstick blink when trying to detect it? Yes.
Right, that is pretty odd. If both leds are blinking that means
A) the reset sequence is ok. The prop is recognising the LFSR
C) the prop is returning the LFSR.
This means bst is not catching the inbound data properly, or it's not making its way back properly.
Does it help if rather than unplug/replug the propstick you restart bst?
The other thing you could try is firing up the serial terminal, connecting to the propeller and then closing it. I'm a bit stumped right now.
Don't suppose you have any other propeller based kit around?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Oh, the other thing you *could* try is a version of bst prior to 0.17. I made some pretty big changes to the reset timing in 0.17 and 0.16 and before hits the reset cap with longer pulses.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Just restarting bst does not clear the "cannot find prop"
There is a sequence that has been perfect.·
Connect (serial terminal)
Type something
Disconnect
F7 always works after that.· Note: step 2 is required!· 1) and 3) alone are not sufficient.
Another minor observation: I use a dual monitor setup.· When I slide bst over to the secondary monitor (on the left in my setup)·and close and then reopen, it reopens nearly off-screen (to the right) of my primary monitor.· If I do the same sequence with bst in the primary monitor, it restores to the expected position.· Size is correct in both cases.
F7 always works after that. Note: step 2 is required! 1) and 3) alone are not sufficient.
Ok, good find. I can't see why simply transmitting a character would solve the problem, but at least it's a known workaround.
I'm assuming this all works perfectly with the Propeller Tool?
Bob Anderson said...
Another minor observation: I use a dual monitor setup. When I slide bst over to the secondary monitor (on the left in my setup) and close and then reopen, it reopens nearly off-screen (to the right) of my primary monitor. If I do the same sequence with bst in the primary monitor, it restores to the expected position. Size is correct in both cases.
I'd guess that there is a problem with the way I'm saving the geometry, but it might take me a little while to figure out how to fix it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
As to the positioning on dual monitors: I write in C# mostly.· I am not aware of anything extra to do when more than one monitor is in use.· I had to change none of my code when I shifted to 2 monitors.· But Hanno had a similar problem with ViewPort, and he did something that fixed it.· Maybe he could shed some light on it.
Another not so nice clue is this: Usually after a unplug/replug or a 1-2-3 sequence on the Serial Terminal, F7 works once.· But sometimes it works twice.· I should add that I am NOT running the connection in high speed mode and I have a high quality short USB cable.
Hi Brad,
On multiple displays the window's horizontal position is negative if it's placed on the left monitor. If you restrict this number you may see what Bob's experiencing.
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
I wonder if what I'm experiencing has something to do with what is running on the Prop.· I have the chip loaded with a program that is using ViewPort as a debugger.· ViewPort loads a cog with a high speed (1Mbps in this case) serial comm program that is continuously sending bits until interrupted by bits coming in.
Ken: found the page.· I don't know what I was doing wrong.
Brad: I updated my FTDI driver from 2.4.16 to 2.6.0· No change.· I have tried loading innocuous programs to the Propeller chip.· Again, no change in the "F7 only works once" problem.
Bob Anderson said...
Ken: found the page. I don't know what I was doing wrong.
Brad: I updated my FTDI driver from 2.4.16 to 2.6.0 No change. I have tried loading innocuous programs to the Propeller chip. Again, no change in the "F7 only works once" problem.
Thanks Bob. Puzzling, but I'll keep looking. Is there anything that might be special about your hardware configuration? I got hold of a Windows XP SP3 machine, but of course it works perfectly here. Sods law.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Hanno said...
Hi Brad,
On multiple displays the window's horizontal position is negative if it's placed on the left monitor. If you restrict this number you may see what Bob's experiencing.
Hanno
Thanks Hanno, that narrowed my search considerably. You are spot on, my routine that parses the geometry saved in the registry was ignoring the '-' sign.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
I fixed a similar bug in ViewPort the other day- I was limiting the value to positive numbers, didn't know a desktop location could be negative. I'm now enjoying my dual monitors. Congrats on getting bst on the Parallax site!
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
So you get a web page at Parallax ?, that is one nice good move !, thanks Parallax and Bard of course
On another line of thought I was playing with "constants", I mean double-quoted ones.
This compiles:
mov 0, "A"
but this does not...
mov 0, "AB"
I was wondering if "AB" is a valid constant... it is smaller than 511... I looked into this because I needed pPropellerSim to compile some code with these kind of constants (just one char). They were not recognized by the compiler thus I added them to it and then I thought what does BST with them ?... (I implemented the second case as valid).
Ale said...
So you get a web page at Parallax ?, that is one nice good move !, thanks Parallax and Bard of course
On another line of thought I was playing with "constants", I mean double-quoted ones.
This compiles:
mov 0, "A"
but this does not...
mov 0, "AB"
I was wondering if "AB" is a valid constant... it is smaller than 511... I looked into this because I needed pPropellerSim to compile some code with these kind of constants (just one char). They were not recognized by the compiler thus I added them to it and then I thought what does BST with them ?... (I implemented the second case as valid).
Any thoughts on this ?
I'm not really sure to be honest. By my maths "AB" is represented as $4142. How are you encoding it?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Comments
However, I do see that often the prop is not recognised, even after a previous download. I am not using your latest version which may correct this. I am just about download the latest version on my XP machine, so I will let you know how it goes.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBlade,·RamBlade,·SixBlade, website
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
· Prop Tools under Development or Completed (Index)
· Emulators: CPUs Z80 etc; Micros Altair etc;· Terminals·VT100 etc; (Index) ZiCog (Z80) , MoCog (6809)
· Search the Propeller forums·(uses advanced Google search)
My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm
The latest bst ide version 0.18.4 on XP will not recognise the usb port although PropTool does. The USB is on COM18. So, I downloaded the latest test version 0.18.5-Pre3 and it finds the usb on com18 without problems. As I have not yet done enough testing, I am unsure if it will have intermittent download errors as 0.18.5-Pre1 does on Vista.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Links to other interesting threads:
· Home of the MultiBladeProps: TriBlade,·RamBlade,·SixBlade, website
· Single Board Computer:·3 Propeller ICs·and a·TriBladeProp board (ZiCog Z80 Emulator)
· Prop Tools under Development or Completed (Index)
· Emulators: CPUs Z80 etc; Micros Altair etc;· Terminals·VT100 etc; (Index) ZiCog (Z80) , MoCog (6809)
· Search the Propeller forums·(uses advanced Google search)
My cruising website is: ·www.bluemagic.biz·· MultiBladeProp is: www.bluemagic.biz/cluso.htm
Builds up to and including 0.18.4 had a bug in my Win32 serial routines that prevented it seeing ports > 8. I incorporated the fix in 0.18.5-pre2.
There are a number of load/program fixes in there, but none specific to detecting the propeller on Windows that I can think of.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
I'm trying out bst.exe for the first time.· (0.18.5-Pre3)
The first time I try to find the Prop chip (F7), it is located just fine.· Thereafter it cannot find the Propeller until I unplug and replug the USB cable (I'm using a PropStick).· Am I missing a setting somewhere?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
G'day Bob,
What operating system are you using?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Ok, I can get my hands on one of those.
Can you go to Tools->IDE Preferences->IDE Preferences->Configure Ports
and see if :
A) your propellers com port is there
C) Port Select : Says "Manual"
D) when you click "find prop" it actually does?
Try clicking "Find Prop" a couple of times in a row. Does it detect the propeller every time?
If you add/remove a port you need to close/open the port configuration box (or click "Rescan"), it only looks at the available ports when it is opened up.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Nevermind, I can reproduce this locally. It was a logic error in the error reporting code. That message should never have been printed.
Unless you need it fixed urgently, I'll let it slip out with the next update.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Then I try F7, it may work once (or twice) then I get BST-test2.png.· After that, Prop can never be found until I go throught the unplug/replug sequence.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
I see that it is possible to fold blocks of code, like DAT or PUB blocks.
Is there a way to designate an arbitrary set of lines to be folded?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Not at the moment. I toyed with the idea of a {$REGION}{$ENDREGION} directive, but thought it was just messy and non-standard.
The serial problem has me a little perplexed.
Is your propstick the one with the built in USB ?
After you get the error, when you click on the "Yes" button and it takes you to the port search box, is COM6 still listed?
Does the "Serial Receive" led on the propstick blink when trying to detect it? Does the "Serial transmit" led blink at all?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Right, that is pretty odd. If both leds are blinking that means
A) the reset sequence is ok.
C) the prop is returning the LFSR.
This means bst is not catching the inbound data properly, or it's not making its way back properly.
Does it help if rather than unplug/replug the propstick you restart bst?
The other thing you could try is firing up the serial terminal, connecting to the propeller and then closing it. I'm a bit stumped right now.
Don't suppose you have any other propeller based kit around?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
There is a sequence that has been perfect.·
F7 always works after that.· Note: step 2 is required!· 1) and 3) alone are not sufficient.
Another minor observation: I use a dual monitor setup.· When I slide bst over to the secondary monitor (on the left in my setup)·and close and then reopen, it reopens nearly off-screen (to the right) of my primary monitor.· If I do the same sequence with bst in the primary monitor, it restores to the expected position.· Size is correct in both cases.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Ok, good find. I can't see why simply transmitting a character would solve the problem, but at least it's a known workaround.
I'm assuming this all works perfectly with the Propeller Tool?
I'd guess that there is a problem with the way I'm saving the geometry, but it might take me a little while to figure out how to fix it.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
As to the positioning on dual monitors: I write in C# mostly.· I am not aware of anything extra to do when more than one monitor is in use.· I had to change none of my code when I shifted to 2 monitors.· But Hanno had a similar problem with ViewPort, and he did something that fixed it.· Maybe he could shed some light on it.
Another not so nice clue is this: Usually after a unplug/replug or a 1-2-3 sequence on the Serial Terminal, F7 works once.· But sometimes it works twice.· I should add that I am NOT running the connection in high speed mode and I have a high quality short USB cable.
I'm off to bed.· 'til tomorrow...gnite
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
On multiple displays the window's horizontal position is negative if it's placed on the left monitor. If you restrict this number you may see what Bob's experiencing.
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
I wonder if what I'm experiencing has something to do with what is running on the Prop.· I have the chip loaded with a program that is using ViewPort as a debugger.· ViewPort loads a cog with a high speed (1Mbps in this case) serial comm program that is continuously sending bits until interrupted by bits coming in.
I'll run some experiments.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Jessica set up a Parallax web page for BST. We welcome any input to make this page more complete, too.
http://www.parallax.com/tabid/828/Default.aspx
Thanks Brad and others for the fine work.
Sincerely,
Ken Gracey
Congats Brad for getting on the Parallax web site!
Jim
I can't seem to find that web page.· Is there something wrong with URL ?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Brad: I updated my FTDI driver from 2.4.16 to 2.6.0· No change.· I have tried loading innocuous programs to the Propeller chip.· Again, no change in the "F7 only works once" problem.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Thanks Bob. Puzzling, but I'll keep looking. Is there anything that might be special about your hardware configuration? I got hold of a Windows XP SP3 machine, but of course it works perfectly here. Sods law.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Thanks Hanno, that narrowed my search considerably. You are spot on, my routine that parses the geometry saved in the registry was ignoring the '-' sign.
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.
Hanno
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
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
On another line of thought I was playing with "constants", I mean double-quoted ones.
This compiles:
mov 0, "A"
but this does not...
mov 0, "AB"
I was wondering if "AB" is a valid constant... it is smaller than 511... I looked into this because I needed pPropellerSim to compile some code with these kind of constants (just one char). They were not recognized by the compiler thus I added them to it and then I thought what does BST with them ?... (I implemented the second case as valid).
Any thoughts on this ?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Visit some of my articles at Propeller Wiki:
MATH on the propeller propeller.wikispaces.com/MATH
pPropQL: propeller.wikispaces.com/pPropQL
pPropQL020: propeller.wikispaces.com/pPropQL020
OMU for the pPropQL/020 propeller.wikispaces.com/OMU
I'm not really sure to be honest. By my maths "AB" is represented as $4142. How are you encoding it?
▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
Life may be "too short", but it's the longest thing we ever do.