• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 40 subscribers
  • Views 606 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.

Original question:

CC3220SF-LAUNCHXL: Compilation errors when SL_INC_INTERNAL_ERRNO not defined

LAUNCHXL-CC3235SF: Using open OCD

user6391287
Prodigy 80 points
Part Number: LAUNCHXL-CC3235SF
Other Parts Discussed in Thread: CC3235SF, UNIFLASH, CC3135

Hi,

I would like to run Zephyr examples with the CC3235SF launch pad but I need to use open OCD to flash the card. The question has already been posted but the link in the answer doesn't work and the subject is closed...

Is it possible to have that documentation?

Thanks a lot,

Regards,

Pierre-Yves

  • 0
    TI__Mastermind 40965 points

    Hi Pierre-Yves,

    The SimpleLink OpenOCD download will have the needed files and setup:

    https://www.ti.com/tool/SIMPLELINK-OPENOCD

    If you try following the steps after "f for some reason you wish to continue to use your TI OpenOCD installation" in this guide here, are you able to get OpenOCD to connect to the CC3235SF?

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Prodigy 80 points

    Thank you for your answer Michael.

    I follow the guide you mention, I compile and I get the .bin, .elf, ... Then I want to use the simple link uniflash software to burn the .bin. But it does not work (I use it without problem when I generate the .bin through code composer studio for my own software based on the TI example).

    Is there somebody who managed to use the Zephyr example on your side?

    Or somebody who has compile it like the TI example in CCS? (<- That would be great!)

    Also, in the zephyr guide your mentionned, Do you understand why it is needed change the jumper ? ("Jumper SOP[2..0] (J15) to [010]" and then "Switch Jumper SOP[2..0] (J15) back to [001].")

    Regards,

    P-Yves

  • 0 in reply to user6391287
    TI__Mastermind 40965 points

    Hi P-Yves,

    As Zephyr is a third-party software package, we haven't run it and cannot provide support for it directly on these forums.

    It does seem a bit strange that the .bin generated doesn't work, and you have to load the compiled binary directly info memory using a debugger. I wonder if the .bin format generated is different from the one generated by CCS. I suggest you check the post-build steps for Zephyr to see what it is doing to go from the compiled output to the packaged .bin and compare it to the CCS post-build steps to see what might be different.

    The jumper change mentioned describes changing the operating mode of the CC3135, probably to allow for programming the device and then switching back to SWD debug mode. See section 9.10 Boot Modes of the CC3235 datasheet for more information.

    Regards,

    Michael

  • 0 in reply to Michael Reymond
    Prodigy 80 points

    Hi Michael,

    I fully understand your point regarding the support on Zephyr. I just thought that since we're talking about your board, you might have collaborated. I've been trying!

    At the end, I know why the sample does not work... There is just nothing in it! I was dealing with the tools and I don’t ever check the source code…

     

    https://github.com/zephyrproject-rtos/zephyr/blob/master/samples/net/wifi/src/wifi_test.c

     

    Anyway thanks for you help!

    Pierre-Yves