How to generate binary file for AM3359 using CCS5.4

Hello!

1. only

Regards,

Igor

Balwant Godbole said:

The image to download should be the binary image. Can someone help me in generating a binary image from .out image?

The example shown by Igor shows how to convert to the Intel hex format. If you wish to convert to binary the command would be a bit different. You would want to use the tiobj2bin utility.

Please see this wiki page: http://processors.wiki.ti.com/index.php/Projects_and_Build_Handbook_for_CCS#Pre_and_Post_Build_Steps

Also note that Starterware package for AM335x has several example projects that use tiobj2bin command in the post-build step to generate a binary file, which you can use as a reference as well.

Balwant Godbole said:

But when we change the setting from debug mode to release mode, CCS allows to add the libraries at above mentioned path but does not retains it. I mean when you set the library, come out of the properties and go again and check then the set library is not there. Is the evalutaion version restricting me to add the libraries in release mode?

The evaluation license does not have such restrictions. You should be able to add libraries in Release mode and have the properties saved. I will try to see if I can reproduce this behavior, but what might be better is if you could share your project to help us observe this behavior.

Thanks for the reply. Do you want me to share only the project file or you need the entire code to check the release / debug issue? Sharing the code may require some approvals at my side and may take time. But if you just want the .ccsproject or .cproject or .project file then I can share the same. Can you please let me know on this?

I have another question about a warning. I am assigning a function pointer in a structure as

void(*function)(void *). But when I assign this pointer to any of the function e.g. ptr->function = &configure_232, I do get a warning

"#515-D a value of type "void (*)(ACTION_OBJECT *)" cannot be assigned to an entity of type "void (*)(void *)" general_functions.c /CTS_Panda/source line 977 C/C++ Problem

This warning is currently not stopping the program from execution. But can you please let me know if there is any setting I need to do to remove this warning?

Thanks & Regards

-Balwant

Balwant Godbole said:

Do you want me to share only the project file or you need the entire code to check the release / debug issue? Sharing the code may require some approvals at my side and may take time. But if you just want the .ccsproject or .cproject or .project file then I can share the same

Let us start with the project files and see if that is sufficient for me to try to duplicate the problem. Please zip up the .ccsproject, .cproject and .project files and attach it here.

Balwant Godbole said:

I have another question about a warning.

I suspect this is a valid warning from the compiler, but a more complete code snippet that shows the protoypes, function declarations/definitions etc will be helpful to identify the exact reason. Also this would be better answered in the Compiler forum, so please create a new post there with this specific question and code snippet.

Hi,

Please find attached zip file containing the project files.

1460.project_files.zip

One more query on usage of clock function in SYS/BIOS. I want to use this clock function as software timer in my application. As per user guide of SYS/BIOS, the period / timeout values should be entered in micro seconds. I have not changed the ICE processor frequency (I think default it is 550MHz). When I tried to load a period value for clock function as 1000 to get a tick of 1ms, I observe that I am not getting the proper tick.

In the users manual, it is mentioned that the period is in terms of clock ticks and should be enetered in terms of micro seconds. Am I making some wrong configuration for 1ms clock function tick? How to calculate the exact count for period to have the correct clock interrupt timings in terms of ms?

I will take a look at the project, see if I can reproduce the behavior and get back to you.

We request that you kindly create a new post for new questions. This helps track them better and also helps others who are searching on specific topics. Also some questions need to be in other forums (such as the Compiler forum, BIOS forum or device forums) to be visible to the appropriate experts on that topic. In this case your second question will be better answered in the BIOS forum. Could you please create a new post for it there? Thanks.

Balwant Godbole said:

Please find attached zip file containing the project files.

I can't seem to reproduce the behavior you reported. Here are the steps I took and what I observed:

- I imported your project into CCS 5.4
- Changed the build configuration from Debug to Release
- Went into Project Properties->CCS Build->ARM Linker->File Search Path and added a library under the --library option field, clicked OK
- Went back into Project Properties and the lib file was still there

So I don't see any issues with either adding libraries or them being retained.

One comment is that the libraries have to set each time you go to a new build configuration (for instance the first time you change from Debug to Release, or even if you create a new build configuration), however once it has been changed/set it should be retained.

Unfortunately there may not be much more we can do without being able to reproduce the issue. Based on the steps I described above, if I need to do something different to see the behavior please let me know.