|
Hello. I'm new to Ride and just trying it out. I have been bugged with the following problem.
OS and Ride7 Version Information
OS Name: Microsoft Windows Vista Home Basic 32-Bit
OS Version: 6.0.6002 Service Pack 2
Ride7 Version: 7.30.10.0159
Rkit-51 Version: 6.08.10.0309 Eval License
Ride7 Patch: 7.30.10.0169
Problem:
- When I compile a whole project, I get a "Unknown Tool: RL51" error.
- If I right click a project and choose 'Run' and select '80C51 CodeCompressor', I get a "ERROR: Cannot create backup copy of file ..................." (I am not sure if this is a limited function in Rkit-51 Eval)
Things I have tried:
- Uninstall Ride7 and Rkit51 then reinstalling them.
- Registered msscript.ocx.
- Double checked my OS to make sure its not a 64-Bit system.
- Opened an example project and try building (did not work).
Speculation:
- LX51 Linker not working as intended? Since in project settings I don't see any options under 'Linker', I am guessing that Ride7 was unable to find a linker to build codes? (maybe it was looking for RL51 but only found LX51? I certainly did not see any RL51 under Rkit51 Eval)
Also, I was wondering if there was suppose to be anything in the 'Linker' setting? If there was and since its empty on my Ride7, then could it be a symptom of the problem (missing linker)?
Thanks in advance.
|
Hi,
Thanks for this report. We have been looking at this problem, which looks related to non-ANSI (Unicode) Windows machines.
In the linker configuration file there is a non-ANSI character (with hexadecimal value above 127), which causes the whole file to be incorrectly parsed, so the RL-51 tool cannot be run from Ride7.
Workaround: Run notepad.exe, and open the RL51.config file in your Ride installation directory, subdir "Config\8051" (by default this will be "C:\Program Files\Raisonance\Ride\Config\80C51\RL51.config").
This is an XML text file.
Look for the following line:
And replace the "µC" by "MCU". This will remove the "µ" character, which has code 0xB5 and is then above 127.
Save the modified file, close notepad.
Restart Ride7, which should work fine.
This problem will be fixed in the next RKit-51 release.
Best Regards,
Hi Bruno.
After several testing, it seems like modifying the single file was not enough to solve the problem. I have looked at other linker related config files and didn't find another file with non-ANSI characters. I'm sure the RL51.config is fine now though, since I re-saved the config file in ANSI to make sure no non-ANSI character exists in that file.
Considering that when I re-ran Ride the Linker settings still fail to appear, I'm guessing the problem may be related to something controlling Linker configurations and settings but is probably several levels higher than RL51.config. Thanks.
Hi,
The problem is more about the editor you use to correct the file. Most editors will keep the same (Unicode) encoding for files that contain non-ASCII characters.
If you want to check that the file is correct, you *really* need to view it in hexadecimal, and verify that the first 2 bytes are NOT 0xFFFE. You can open the file as a source file in Ride7, then press Ctrl+H, which toggles hexadecimal mode.
Anyway I placed a corrected RL51.config file at ftp://www.raisonance.com/temp/80C51/RL51-Non-Unicode.zip. Can you use it instead of the default one, and check whether the problem is fixed?
Thanks.
Hi Bruno.
After loading up the file in Ride, I found some gibberish that appeared at the very beginning (it wasn't 0xFFFE, but it wasn't suppose to be there either) without even having to load up Hex mode (I did load up Hex mode which was why I noticed it wasn't FFFE). Delete that little bit of nonsense before and Ride works perfectly.
I did not see it in notepad, so my guess is that, somehow, notepad added that little piece of data and hid it from being seen.
Company internet forbid me from downloading the file, but the problem was solved regardless.
Thanks for all the help.