CCS/TMS320F28030: Problem with GUI composer

Sagar,

When creating the GUI Composer Project and selecting XDS as the transport were you able to specify the program file?

i.e. were you able to fill out this screen:

If not you can get back to those settings here:

Regards,

John

HI Sagar,

Are you able to preview your app in the online version after you upload the .out file and bind the widgets?

When you export the app for CCS Desktop, the app will work like any other views inside CCS. i.e it read/write memory base on the selected core in the debug view. So, in you case, are you not seeing this experience when you drop your app into CCS?

If you don't want to use CCS, you can also export your app as a standalone app. Download the runtime and install your app into the runtime. There should be instruction in the export dialog regarding the runtime and the required instruction to install your app in the standalone mode.

Regards,
Patrick

Hi Patrick,

I will try using it as a stand alone app and let you know if I face any difficulties.
I have one more question regarding the code below. I am simply blinking led widget on and off. (led_state has binding with LED widget).
I am seeing that it runs only once i.e. whenever I click play it goes on and off once. it does not run infinitely. I am able to see the expected results in watch expressions in CCS but in GUI I am able to see it only once. Could you help me on that?

code:

int 16 led_state = 0;
while (1)
{
led_state = 1;
DELAY_US((500000));
led_state = 0;
DELAY_US((500000));
}


Thanks
Regards
Sagar Shah

Example_2803xGpioToggle.zip

Hi Sagar,

Please take a look at this post 

Patrick

Also I would like to add that it works fine without using Delay_US() and when I run it using RAM.

sagar shah54 said:

Also I would like to add that it works fine without using Delay_US() and when I run it using RAM.

Do mean that if you change the GEL to boot from RAM that it works as long as you are not using Delay_US() or do you mean that even without uncommenting the line it works from RAM as long ad Delay_US() is not used?  If the former that doesn't make sense to me but I will ask a C2000 expert.

As far as not using the cloud version yes this is possible.  You can export your GUI to either a standalone application to run on the desktop or as a view to use inside CCS.  Exporting as a standalone application would still have the same issue.  If you export it as a view for inside CCS you would use CCS to load the program and then you would open the view, that might avoid the issue for you.

John

 I mean that even without uncommenting the line it works from RAM as long ad Delay_US() is not use. So the problem starts if I use  Delay_US() using FLASH.cmd file. So the solution you have mentioned Does not work. Have tried using GUI composer with 28035 using FLASH file witha DELAY_US() function? 

Sagar,

sagar shah54 said:

I have changed DELAY_US() function to .text so the code runs well on CCS and I can watch the variables

So you changed:

       .def _DSP28x_usDelay

       .sect "ramfuncs"

To:

       .def _DSP28x_usDelay

       .sect ".text"

Where is .text being placed?  I.e. what does the line in the .cmd file look like

   .text            : > RAML0_L3,   PAGE = 0

or something like?

   .text            : > FLASHA,   PAGE = 0

If you are placing it in FLASH then you need to copy it to RAM in your application.  You would not want to place it in .text as you only want to copy the relevant code to RAM so keep it in ramfunc.

There are example projects in C2000Ware that show how to copy the ramfunc section at runtime.  Just take a look at one like Example_F28035_Flash.  You still have the code going into ramfunc, the ramfunc section is placed in FLASH for loading but then at runtime it gets copied to RAM.

On this device if it is working in CCS don't assume it is going to work in GUI Composer.  Please note that if the program is being placed in RAM CCS will still work fine.  The extra reset that causes the device to start executing from FLASH does not occur when using CCS.  The problem is specific to GUI Composer.

John

Yes I did change  .def _DSP28x_usDelay

      .sect "ramfuncs"

To:

      .def _DSP28x_usDelay

      .sect ".text".

In Cmd File this what it shows in screen clippling-

Sagar,

I was able to modify your code to get it working from Flash on a F28035.

As John mentioned before, the Delay_US function needs to run from RAM, so it is placed in a separate section that is then copied from Flash to RAM at runtime. This is not done automatically and is something the user needs to do by making a call to memcpy. I would suggest taking a look at the flash_f28035 example and reading through the comments in the source code that show you when and why this section should be copied. 

I have added the memcpy to your source file along with some other minor updates and attached the updated project below. I was able to bind the variable led_state to a GUI Composer LED widget and view its status. Please give this a try and let us know if this resolves the issues you were seeing.

Example_2803xGpioToggle_sagar.zip