uVision allows setting the code editor font and size where creator does not.
The free C51 that comes with PSoC Creator does do some optimization, but it wasn't adequate enough for us so we went ahead and purchased the Keil CA51. Here is the version that we downloaded from the Keil web page: C51 V9.51a. It installs uVision 4. How do you get PSoC creator to use the C51 compiler in uVision?
1 of 1 people found this helpful
You can select the compiler from the Project->Build Settings dialog. Pick "DP8051 Keil Generic" from the Toolchain pull-down. Note that you need to do this in every project (a feature to choose your default compiler is on the works).
Depending upon where you installed the compiler, you may also need to tell the tool where to find it. In the Tools->Options dialog. Under Project Management / Generic Toolchains add the full path to the compiler.
Here is the image I managed to fail to add to the last post!
I just get Keil license and download and installed the latest version c51v952.exe.
In the PSoc Creator, Tools\Option\Generic Toolchains I put C:\Keil\C51\BIN in DP8051Keil Generic.
But I cannot find C:\Keil\ARM\ARMCC\BIN in my C:\Keil folder
What should I put in ARM MDK Generic ?
In my installation these paths all empty, looks like a default is in effect.
That being said I would think entry should be, based on my distribution, C:\Keil\ARM\BIN
Something about his post does not look right, given this is PSOC 3, which
is not ARM, you might contact author and ask for clarification.
You will get the C:\Keil\ARM\ARMCC\BIN in your C:\Keil folder when you install the MDK-ARM Microcontroller Development Kit. You could buy a licence or download the lite version.
In the mean time just leave it as it was by default.
Since my installed folder Keil do not have ARM sub-folder so that I leave this path not selected.
When I compile Creator sample project :Music_Creation, It generate 151 errors: something like:
How can I resolve these errors?
Robert left Cypress one year ago, better try to find someone else or file a technical case.
I suspect I am having a problem with how the Keil is managing memory on a PSoC 3 using Creator 3.0.
Who should I contact?
If you do not (want to) file a technical case, ask your question, maybe I can help you. I am much older than the 8051 design, so I may know something about.
Thanks. I have a module that I place all my global variables in with little regard for data type and the order in which they are listed. Already quite a lot of values. I'm up around the 84% FLASH and 52% on RAM usage. I placed a new UINT16 and began having other UINT16 variable that are updated ADC readings began getting stomped on. I removed the variable but it didn't fix the problem. I had to drop back to a previously archived version to get the product to work again. I then tried renaming the variable and placing it next to the variables that were getting corrupted and it solved the problem.
I need to understand if there is some issue with byte boundaries or a preferred order for declaring variables. Do I lump all the 8 bits together, all the 16s together etc?