• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 51 subscribers
  • Views 579 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC2564: help with "logger" tool

Tim Bernasch66
Prodigy 70 points
Part Number: CC2564

I am trying to get the "logger" tool working with a cc2564_moda part. I have connected the txdbg pin of the module to a FTDI ft230x usb-rs232 bridge chip. I can successfully connect to the COM port and load the definition files and view the log stream, but something about it seems horribly wrong. Other than the fact that the messages on startup don't match the example output on the wiki page at all, the inclusion of random numbers and characters makes me think that this is broken.

I am starting to suspect that maybe my outdated usb-serial bridge is just not up to the task of sending 1-mbit serial to the operating system. One complicating issue is that the correct driver does not even work, and windows 10 keeps trying to replace it with a driver from a different company... :/  which is making me suspect my serial port setup even more. I have yet to find a good free terminal program that will even open the port at 921600 so i might view the output to verify it is working

Does anyone have any advice, or maybe the name of a serial bridge part that for sure will work under windows 10 with the cc2564 and the logger software? Also a good serial terminal software that could actually be used to open and view a serial port above 115,200k

attached is pictures of the output I see.  notice that it repeatedly says the same thing over and over, keeps referencing "line 16384" in different files which seems unlinkely, and also the letter "a" with diacritics appearing occasionally

postimg.cc/.../
https://postimg.cc/image/ppay9ayld/


  • 0
    TI__Mastermind 29250 points

    Hi Tim,

    Tim Bernasch66 said:
    attached is pictures of the output I see.  notice that it repeatedly says the same thing over and over, keeps referencing "line 16384" in different files which seems unlinkely, and also the letter "a" with diacritics appearing occasionally

    I am not able to access the image/screenshot in the link above. Can you please upload the image directly to the e2e thread (using the "Insert Code, Attach Files and more..." button)?

    Refernce :

    Tim Bernasch66 said:
    I am trying to get the "logger" tool working with a cc2564_moda part. I have connected the txdbg pin of the module to a FTDI ft230x usb-rs232 bridge chip. I can successfully connect to the COM port and load the definition files and view the log stream, but something about it seems horribly wrong. Other than the fact that the messages on startup don't match the example output on the wiki page at all, the inclusion of random numbers and characters makes me think that this is broken.

    Couple of things you might want to check first with your level shifter (uart-usb bridge) and logger settings. 

    (i) Is the level shifter 1.8V TTL level and can it handle the 921600 baudrate required for the logger?

    (ii) Have you configured the BT Logger and HCI/LMP viewer ports of the logger exactly like shown in the Logger User's Guide?

    Best regards,

    Vihang

  • 0 in reply to Vihang Parmar
    Prodigy 70 points


    The usb-serial bridge has a "vdd_io" line that i tied to 1.8v so Im hoping the levels are okay.
    I tried it on a second win10 computer and with an older version of the official FTDI driver... still broken

    The problem is that the FTDI driver just does not work, period, for any speed (port will not even open in any software). and the driver windows wants to use (MTK) has totally different speed choices that only go up to 128,000 in windows. But i know that the FTDI hardware requires specific configuration through its driver.. so I think this is a case of totally broken drivers.. no matter what speed i open the MTK driver at, i get roughly the same gibberish. 

     my next step is to buy a couple usb serial adapters and see if i can get anything going. Is there anything you can recommend that supports an external  VDD_IO  reference? What does TI use internally?

  • 0 in reply to Tim Bernasch66
    Prodigy 70 points

    Hey I just wanted to follow up to say I think I kind-of got this working. I used a cp2014 serial bridge adapter from Adafruit, and a BSS138 based level shifter. On my scope the signal looked like garbage after level shifting but it seems to work... all the messages are in english and seem to make sense (ie: same init sequence seen on the wiki)

    One question though: on my output I do not see any HCI/LMP traces like the wiki screenshot has. Should I be hooking a second COM port directly to the HCI bus? Currently I am setting the HCI/LMP viewer to the same COM port as the TXDBG pin.. is that wrong?

  • 0 in reply to Tim Bernasch66
    TI__Mastermind 29250 points

    Hi,

    Tim Bernasch66 said:
    One question though: on my output I do not see any HCI/LMP traces like the wiki screenshot has. Should I be hooking a second COM port directly to the HCI bus? Currently I am setting the HCI/LMP viewer to the same COM port as the TXDBG pin.. is that wrong?

    Both HCI/LMP viewer and BT Loger ports of the logger should be configured for the same physical COM port that is connected to the TX_DBG pin. 

    If you are not seeing the HCI/LMP viewer traces, please check if you have selected the correct XML file in the settings and try deselecting and selecting again the HCI/LMP viewer port in the logger settings menu.  

    Best regards,

    Vihang

  • 0 in reply to Vihang Parmar
    Prodigy 70 points

    After restarting the software are re-configuring the two ports, everything worked perfect. Thanks for your help