• Locked Locked
  • Replies 4 replies
  • Subscribers 98 subscribers
  • Views 955 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.

DSPC-8681 vuart console in SYS/BIOS project

Roelof Berg
Intellectual 640 points

Hello,

we want to use the virtual uart console that comes along with a DSPC-8681 (from Advantech which contains four TI C6678).

- We are able to see traces by using "dsp_demo connect 0 0" and the IPC-Demo.

- I tried to port the console code from the IPC-Demo to the WEB-Demo (SYS/BIOS-Based)

- When we execute "dsp_demo connect 0 0" we run into error no 5

- Strange: When we boot, then run the IPC-sample (with success), then reset the DSPs, then run the SYS/BIOS based application (web demo plus console code) we can successfully see a trace line. But if we don't run the IPC-sample before we run the SYS/BIOS based code, we allways see error no 5.

- Also strange: When we use the above mentioned procedure that works (first IPC-sample, then our code), we can print out only one single line at system startup. If we print out more than one line: Error 5.

Questions:

A) Documentation ?

Is there any documentation of the Advantech vuart console ? There is some external cirquit-logic at 0x800800, right ?

B) Am I the only one ?

Is anyone using the vuart console in a SYS/BIOS Project ? What has to be done more than copying the files and calling the init-method ?

 

Thank you very much, we're really stuck here,
Roelof

 

  • Intellectual 640 points
    • Windows 7 32 bit
    • Advantech Drivers 0.7.7
    • original dsp_demo binary from Advantech
    • ipc .out binaries from Advantech behave equal to our own build of ipc (both succeed to run a console)

    -> So we assume it is not related to the build System.

    We call serial_init() and then uart_printf(), nothing else.

     

  • TI__Mastermind 45025 points

    Hi Roelof,

    I'm trying to better understand the software that you are working with here.  It sounds like you are working with a product that is made by Advantech, and this product contains TI hardware.

    It also seems that you are working with some demo or SDK of sorts, also from Advantech, which was built around TI software (BIOS, IPC).

    Is this correct?

    More specifically, could you provide some clarifications on the following?

    Roelof Berg said:
    - I tried to port the console code from the IPC-Demo to the WEB-Demo (SYS/BIOS-Based)

    Can you please provide more info on these demos?  Where are these demos coming from?

    Roelof Berg said:
    - When we execute "dsp_demo connect 0 0" we run into error no 5

    I'm not familiar with the the tool "dsp_demo".  What is this tool?

    Steve

  • in reply to Steven Connell
    Intellectual 640 points

    Hello Steve,

    thank you for responding to my post.

    The only purpose of the DSPC-8681 hardware from Advantech is to give access to four TI C6678 chips over PCIe. I originally posted my questions to TIs C66x-Forum because I know that people visit the C66x-Forum who also own the same hardware. (And in the C66x-Forum also other questions regarding the DSPC-8681 can be found).

    Unfortunately my forum post was moved to the TI-RTOS forum meanwhile and possibly my questions can't be answered here as the hard- and software I refer to was designed by Advantech. We also contact the Advantech support and will ask then if they have a user forum similar to this one, that would be a better place to post our questions.

    Have a nice wheekend,
    Roelof

     

  • in reply to Roelof Berg
    Intellectual 640 points

    We found the information (and post it here just in case anyone else will come across the same topic).

    The protocols source code is available in the file vuart.cpp in the PC application. The protocols endpoint is the memory 0x800800 | ((N + 0x10) << 24 which points to CorePacN L2 SRAM according to the C6678 data sheet (Table 2-2). So reserving the memory beginning at 0x800800 in L2 SRAM should be the missing piece.