I’ve been trying to program my Basic Atom Pro 28 Pin, and I’ve gotten it to connect to my computer via USB to serial cable. But whenever I compile/run the program, I get the same error message:
Starting Compiler…
Preparing files…
C:\PROGRAM FILES\BASIC MICRO STUDIO\FIRST.BAS
Compiling…
Linking…
Assembler messages:
Error: Can’t open Micro for reading.
Micro: No such file or directory
Micro:0: Error: Can’t open Studio\bin\ for reading.
Micro:0: Studio\bin: No such file or directory
C:\BasicMicro\Basic Micro Studio\bin\ld.exe : cannot open linker script file C:\BasicMicro\Basic: No such file or directory
Errors Detected
I get that message on two different computers, and I’ve reinstalled Basic Micro Studio twice on both. Another computer can get past that message, but after the program is compiled and loaded on to the Board, I get another message like this:
“Error: 0. No errors in running.”
Any help or suggestions would be really appreciated!
Which version of the compiler did you install? What is your computer? Which OS? Are you an administrator on the computer(s) What USB adapter? Have you manually selected the Basic Atom Pro and correct communication port on the drop down lists at the top of the IDE?
I’ve been browsing through the forums for a few days before posting this question, so I made sure to check the common mistakes in set up.
I have the latest version of the compiler, 2.0.0.15 from the Basic Micro website (uninstalled and reinstalled twice on different computers to see if there was a problem with installation causing files to be misplaced)
I’m running an older version of Windows, XP Professional SP3 2002, and I’m an administrator on the account. I made sure to get an FTDI wire, the Sewell SW-1301.
I’ve definitely manually selected the BAP 28, COM8 from the drop down menu, which is where it’s plugged in. In fact, I can connect to the Board (when I go to Preferences and click Find Processor, it locates the one on my COM8 port).
It’s only when I compile the program that it is interrupted by the weird linkage error.
Thanks for all your help. I’m definitely willing to post more information if you need it.
Not sure what to suggest here, but some thoughts:
a) Had problems before that was cleaned up when I did a complete uninstall/reinstall. That is I used the Remove Program Control panel app to do the uninstall. Reboot computer, Then re-install. If it was just one machine, I would suggest that you verify that you have free disk space. Also check to see where your temp files go, … But with two machines?
b) Likewise for the FTDI driver.
c) Try different USB to serial adapter. My Google of Sewell SW-1301, makes me think this is not an FTDI based adapter (from spec: PL 2303HX Chipset)
d) Also Ask up on BasicMicro forum, as maybe the developer (Nathan) may know what is going on.
Hey guys,
I seem to have found a new issue. I took mgrob’s advice and decided that I’d remove the SSC-32 from the equation. He said he noticed a problem with the connection between the ps2 remote and the receiver in the previous comments. Now, since I’ve tried it as well, I have noticed a similar thing. I have 3 ps2 receivers and only one of them works between the two arms I use. The issues they have are somewhat different.
One that doesn’t work will allow the ps2 controller to connect to it, but eventually while using the arm, I notice the Red A light on the Bot Board just fizzle out and that causes the arm goes haywire. (Battery power is not the problem, after an hour of troubleshooting.) Occasionally I won’t get the red light to come back on at all, and the BB2 speaker will blare its error tones over and over and over again. It takes a lot of power switch flicking to get the same short-lived control of the arm.
The second one seemed to work okay, because the red light actually stays lit on the Bot Board 2 and the red light on the ps2 receiver blinks. Once I try connecting a controller to it, no dice. I’ve tried all three controllers (I know that they all run the same frequency, but still…) and to no avail.
Should I consider replacing these receivers? Is there a spot in my program that I should focus on to help the connection? They are the Lynxmotion controllers and receivers. Like I said, one still works, and I haven’t had a problem with it. I’ve tested all three on both of the arms I have.
If you would like a copy of my latest modified program, please request it and leave an email and I will gladly send it to you.
Can you provide an image of the setup? Note that there are two versions of the PS2 controller - the “older” one which has a red and green LED in the receiver, and the “newer” one which has two red LEDs in the receiver. The old transmitter has the logo perfectly flat while the new version the logo is more “3D”. The two are not compatible with one another, and the new one is not compatible with the old PS2C cable - it needs a level shifter.
I have the older controller I believe, because it does have a red and green LED on both the transmitter and receiver. I just took a bunch of pictures of what I have… here ya go
