Final try with the Tiva C

Martin Andersson

I got until friday to get the Tiva C with the CC3000 up and working. If I can not get this done I will be forced to stop all further work on the platform because of other projects that need my time.

I am right now working on moving the EEPROM updater from the MSP430 platform to the Tiva C so I can update the internal software on the CC3000 to the 1.13 version. But it hash´t gone smoothly and I got a few errors left as can be seen below. I am willing to send this project to you if that will help you help me.

I just removed the line following on line 423in the main function

// WDTCTL = WDTPW + WDTHOLD; //Removed

I don´t know if this is something I should but the error is gone!

How do I solve the error below when it refers to unresolved declaration.

Description Resource Path Location Type
#10010 errors encountered during linking; "Updater.out" not built Updater C/C++ Problem
#225-D function "unsolicicted_events_timer_init" declared implicitly Updater_DR.c /Updater line 270 C/C++ Problem
#169-D argument of type "char *" is incompatible with parameter of type "UINT8 *" Updater_DR.c /Updater line 365 C/C++ Problem
unresolved symbol unsolicicted_events_timer_init, first referenced in ./Updater_DR.obj Updater C/C++ Problem
#10234-D unresolved symbols remain Updater C/C++ Problem

As for my own project that I am working on I got the following errors that I just can solve. I have had something like this before and all I needed to do was to export the project and delete the original project and workspace and import it once again and the errors went away. But not this time...

Description Resource Path Location Type
#10010 errors encountered during linking; "TivaC_WBSAM.out" not built TivaC_WBSAM C/C++ Problem
unresolved symbol FlashIntHandler, first referenced in ./wbsam_ccs.obj TivaC_WBSAM C/C++ Problem
#10234-D unresolved symbols remain TivaC_WBSAM C/C++ Problem

I only have 3 more days on this so I will happily accept any kind of help I can get!

over 11 years ago

0 INTEGRIS Dexter over 11 years ago

Intellectual 905 points

Not sure I understand your situation fully but TivaWare 2.1 has CC3000 examples on both Tiva LaunchPads. Including the patch_programmer that updates the CC3000 firmware.

C:\ti\TivaWare_C_Series-2.1.0.12573\examples\boards\ek-tm4c123gxl-boost-cc3000\cc3000_patch_programmer

http://www.ti.com/tool/sw-tm4c

0 Martin Andersson over 11 years ago in reply to INTEGRIS Dexter

Expert 1295 points

Thank you so much Dexter! I can not understand how I was not directed to that CCS project by the TI rep that directed me to the old 1.11 updater of the MSP430! My question that remains before I update the CC3000 is it enough to replace the data fields in wlan_drv_patch and fw_patch? Are there any other changes I need to make in the project so I don´t harm the hardware?

Then I "only" have this strange error left before I will be able to start up the system once again.

Any ides as to reasons for this error?

0 Markel Robregado over 11 years ago in reply to Martin Andersson

Guru 86745 points

Hi,

I suspect you have some CCS settings that are causing this. Possible that you have not set the paths at CCS correctly. Maybe some CCS basics will help. Download the workbook pdf at the link. There is a part at the workbook that discusses setting up CCS.

http://processors.wiki.ti.com/index.php/Creating_IoT_Solutions_with_the_TM4C1294XL_Connected_LaunchPad_Workshop?keyMatch=tiva%20connected%20launchpad%20workshop&tisearch=Search-EN

- kel

0 INTEGRIS Dexter over 11 years ago in reply to Martin Andersson

Intellectual 905 points

To be honest I don't know much more then what I have already divulged. I have not yet worked with the CC3000, just had seen the demos when looking through the installs and filed it away for later use.

Unresolved symbol flashinthandler seems to mean the linker cannot find the C definition of this function. I don't know in that app where it should live but either that .C file is not included in the project or it is flat missing and you need to implement it.

0 Amit Ashara over 11 years ago in reply to INTEGRIS Dexter

TI__Guru**** 244400 points

Hello All,

The FlashIntHandler has been defined in the startup file as an extern. However when linking the obj the linker could not find the corresponding function definition. If you can zip and attach the project (CCSv5.5 version only), I can see as to why it is not.

I worked on a very same issue a few weeks back (search cc3000 on the E2E forum) and it finally turned to be an issue with the workspace

Regards

Amit

0 Martin Andersson over 11 years ago in reply to Amit Ashara

Expert 1295 points

Hello Amit, thank you once again for helping me!

Here is the project.

0 Martin Andersson over 11 years ago in reply to INTEGRIS Dexter

Expert 1295 points

Thanks for you help Dexter! :)

0 Martin Andersson over 11 years ago in reply to Martin Andersson

Expert 1295 points

I just now saw you stated CCS5.5 and I am using CCS6...

0 Martin Andersson over 11 years ago in reply to Martin Andersson

Expert 1295 points

Can you check it even if it is CCS6?

0 Martin Andersson over 11 years ago in reply to Martin Andersson

Expert 1295 points

What does this mean:

Description Resource Path Location Type
#10247-D creating output section ".sysmem" without a SECTIONS specification WBSAM Tiva C C/C++ Problem

Is there a guide here somewhere that will let me export my entire project with all CCS settings and all so I can move it to another PC with CCS and get it working without doing any changes on the new system? I have been using File->Export->General->Archive File but I have always been forced to do settings setups.

0 Amit Ashara over 11 years ago in reply to Martin Andersson

TI__Guru**** 244400 points

Hello Martin,

The project attachment is missing?

Regards

Amit

0 Martin Andersson over 11 years ago in reply to Amit Ashara

Expert 1295 points

Well took a long shoot and importer the CCS project for the patch programmer, deleted all files not related to the CCS or the MCU and then imported my files from my project. That is the only warning I got then, all errors gone.

What do you mean by project attachment?

0 Martin Andersson over 11 years ago in reply to Martin Andersson

Expert 1295 points

Problem solved, forgot the .cmd file. :)

0 Markel Robregado over 11 years ago in reply to Martin Andersson

Guru 86745 points

Hi Martin,

As your problem is already solved, "Verify Answer" any replies in this post that helps solve your problem, to mark this post as "Answered".

Also, it will help other forum members who encounter the same problem as yours, if you make a summary of what you did, leading to "Problem Solved".

- kel

0 Martin Andersson over 11 years ago in reply to Markel Robregado

Expert 1295 points

I removed the data fields and replaced them with the new data fields from the new update. Don´t remember to change the size of the data fields as well.

The errors I got was removed by part removing the flashhandler since I didn´t need it. I also imported a CCS project with a relation to the Tiva C platform and that had a connection with the CC3000 and then imported my files into that project.

Then I had to spend 3 hours to change a error from the TI side!

In the board.c on line 315:

MAP_SysCtlClockSet(SYSCTL_SYSDIV_4 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN |SYSCTL_XTAL_16MHZ);
//Changes from:
MAP_SysCtlClockSet(SYSCTL_SYSDIV_3 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN | SYSCTL_XTAL_16MHZ);

This should not have to be corrected by a user! But please make sure you update this error so other users don´t need to waste their time fixing this.

0 cb1 over 11 years ago in reply to Martin Andersson

Guru 47900 points

This reporter - for one - seriously doubts that, "change of system clock from 50 to 66.6MHz" qualifies as a, "correction!"

0 Martin Andersson over 11 years ago in reply to cb1

Expert 1295 points

Well it is stated ich 50Mhz in the board.c but the Tiva is unstable in connection with the CC3000 if the system clock is set over 50Mhz. As could be seen in my system directly where all communications went down and only sent out jibbrich.

Main correction here is focus surrounding the workspace when strange errors occur.

Arm-based microcontrollers

Arm-based microcontrollers forum

Final try with the Tiva C