• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 96 subscribers
  • Views 757 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM6446 DaVinci 6446 help 1-644938363

Tyler Holeman
Prodigy 230 points

Factory Team,

Please see the request below from Americas Sales and Apps.  If you choose to post a response here, I will communicate it to the field requestor.  If you prefer to contact the field requestor directly, please indicate so in a post and I will close this request in our tracking system.

 

Thank you,

Tyler Holeman

Americas Sales Support Line

*****************************************************************************************

AFA/FAE Requestor's Information


Date Opened:          5/13/2010 05:44:37 PM
Company Name:      Texas Instruments
Contact Name:        Alex Scott
Contact Phone:        (408) 242-4893
Contact Email:         ascott@ti.com
Address:                  165 Gibraltar Court
City and State:         Sunnyvale, CA
Postal Code:            94089

Customer's Application

GPN:                      
Non GPN:               Other
Application:

FW:

SS, Can you please post the below question to the technical forum for the DM6446 or speak with the technical expert? When you have an answer, can you please report back with the answer so I can communicate to the customer? Thank you.

Best Regards, Alex Scott Technical Sales Representative Texas Instruments Incorporated (C): (408) 242-4893 (O): (408) 745-2739 (E): ascott@ti.com 165 Gibraltar Court Sunnyvale, CA 94089 ________________________________

From: Yan Guo [mailto:yguo@vasonova.com] Sent: Thursday, May 13, 2010 9:26 AM To: Scott, Alexander (Alex) Subject: RE:

Alex, It is nice to receive your email.

We are using DaVinci 6446. I used the LOG_printf(...) before on the other DSP, but don't know why it is not working here. As I have just started to take over the software, I need to learn a lot. I have just used "LOG_printf(&dbgTrace, "Start Processing"); " at the beginning of main(), and used emulator to run through it in single step.

The message displayed in Message Log window is ERROR: 0xXXXX, 0xXXXX The followed hexadecimal data may change when I play around. (I have created the LOG(dbgTrace) in the configuration file and included the cfg.h in main() file. What else I may miss? I am using v6.1.6 code generation tool and 5.32.04 BIOS now.) T

Thank you for your help. Yan

From: Scott, Alexander (Alex) [mailto:ascott@ti.com] Sent: Wednesday, May 12, 2010 9:51 PM To: Yan Guo Subject: RE: Yan, What part are you using? Anymore info is greatly appreciated so I can help more. -Alex ________________________________

From: Yan Guo [mailto:yguo@vasonova.com] Sent: Wednesday, May 12, 2010 3:40 PM To: Scott, Alexander (Alex) Subject: Hello Alex, I am Yan working in Vasonova. I have got your email address from Jin. I have just had a problem in using LOG_printf( ...) function in BIOS. I have inserted a LOG(dbgTrace) under Instrumentation





***Please do not delete the below Thread ID when replying to this email, doing so will delay our response to your inquiry***
[SR THREAD ID: 1-ANZ9MJ]

  • 0
    TI__Mastermind 20805 points

    Do you see the same issue with any of the provided examples that we ship with the product (i.e. packages/ti/bios/examples/hello should print  "Hello World"  from main()).  Make sure the default examples work if you can.

    This problem is usually due to a bad pointer or memory corruption.  The host tool thinks the data is invalid and  cannot decode it.

    Are you using custom memory map?  Be careful that the DSP memory doesn't conflict with the Arm memory.

    Another thing to try would be to close the RTA windows (all of them!) and look at the raw buffer in memory.  It should be the log name followed by $buf -- dbgTrace$buf.   Every 4th word of this buffer should be an even number which indicates a sequence number.  And "empty" records should be filled with -1 as first word.  Records are 4 words each.  First word is sequence number.