notify project of EVM6670l

xu fei

Other Parts Discussed in Thread: TMS320C6670

Hi,Thanks for your kindly reply.It helps me so much.

The board which I used is TMDXEVM6670L.And the number is ESE0079266.

Now I have a new trouble about the use of EVM6670L.When I debug the notify project (muticore ) with EVM6670L in CCS5.0,the result is not correct.

This is the result:

[C66xx_2] main: MultiProc id = 2

[C66xx_2] main: MultiProc name = CORE2

[C66xx_3] main: MultiProc id = 3

[C66xx_3] main: MultiProc name = CORE3

[C66xx_0] main: MultiProc id = 0

[C66xx_1] main: MultiProc id = 1

[C66xx_0] main: MultiProc name = CORE0

[C66xx_1] main: MultiProc name = CORE1

[C66xx_0] tsk1_func: Sent request #0 to CORE1

The program is stopped after core0 send a request.I think there is something wrong with the communication of cores.It seems that other cores can not receive the send notify. When I debug the MessageQ project,There is something wrong too.

I choose the SHANNON board in the target configuration when I debug the project.I hope that you can tell the reason.

I have an EVM6472 board (6 cores).When I debug the notify and messageQ project in CCS5.0,the result is correct.

It seems really strange.Can you explain it?

Thanks!

over 14 years ago

0 tscheck over 14 years ago

TI__Mastermind 23525 points

Do you have CCSv5.0.3? If not, you can download and install it from:

http://processors.wiki.ti.com/index.php/Category:Code_Composer_Studio_v5

Once you have that, you should be able to create a target configuration using: Texas Instruments XDS100v1 USB Emulator and select TMS320C6670 as the device. You should not use SHANNON. If you are still having problems with the notify example after that, let us know.

Regards,

Travis

0 xu fei over 14 years ago in reply to tscheck

Prodigy 100 points

Hi,

But there is no TMSC6670 in the device of CCSv5.0.3 .I can only find the TCI66xx and the result of using it is the same with using SHANNON .

Can you explain it ?

0 xu fei over 14 years ago in reply to tscheck

Prodigy 100 points

Hi,Travis

I setup the CCS_5.0.3.00028,but there is still no TMS320C6670 in the .ccxml.

I try a method I found in the setup_CCS_5.0.3.00028\extras\emu_503_win, copy the C6670.xml C6678.xml TCI6608.xml TCI6616.xml EVMC6670l.gel and EVMC6678l.gel to where they should be. After restart the CCS 5.0.3, I find the TMS320C6670 in the .ccxml.

But when I debug the notify project,the result is the same as before.I think if I need an evm6670l in the .ccxml,just like the evmc6472.

I can group cores and connect to each core of the board.But when I debug the notify project ,it seems every core is independent.

Have you ever run the notify project correctly with the EVM6670L before? And What's the reason?

Thanks,

xufei

0 tscheck over 14 years ago in reply to xu fei

TI__Mastermind 23525 points

Xu,

I'm not sure of a your install of CCS v5.0.3 was done correctly, but in either case if you copied the xml files to the correct directories manually, you should be able to create a target configuration, xxxxxx.ccml as I mentioned above that uses the XDS100v1 and you select the TMS320C6670 (not Shannon). In CCS, you go to :

View --> Target configurations

right click target configurations window --> new target configuration

Name the .ccxml file what ever you want

Connection --> Texas Instruments XDS100v1 USB Emulator

Device --> TMS320C6670

Save.

So you have been able to do this right? If you want to additionally group the cores in the target configuration you can do that. This will allow you to connect, load, and execute the programs all together. The console output will contain messages from all cores, but you can determine which core the message is from based on the c6670_n label.

Hope that helps.

Regards,

Travis

Processors

Processors forum

notify project of EVM6670l