• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 40 subscribers
  • Views 261 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.

Custom Uniflash tool and Embedded Programming

Kevin N
Prodigy 20 points
Part Number: CC3235SF
Other Parts Discussed in Thread: UNIFLASH,

Tool/software:

Hi,

I have been facing some buggy/unstable behavior using Uniflash with my custom board that integrates the CC3235SF when trying to program the device through UART and the UARTLOAD bootloader.

So I started developing my own flashing utility to overcome this, and have read through and implemented the functionality described in the Embedded programming guide for the CC3235SF https://www.ti.com/lit/pdf/swpa231)

Though I found that there is a discrepancy I am seeing between the amount of features available through UniFlash and the features described in the embedded programming guide for the CC3235SF.

I am specifically thinking about the lack of ability at receiving device information as documented in the embedded programming guide. I am specifically thinking about the ability to get the device's MAC and device info. The embedded programming system has the "Get Version Info" command. The response though does not contain the MAC address as reported by the uniflash device info. It responds with a MAC Version that is all zeros.

Main Two questions:

1. Is there a way to get the CC3235SF's mac address through the embedded programming command/response flow as reported by the uniflash tool? (not all zeros)

2. Is there more commands available to interact with the device's bootloader that clearly is being utilized by uniflash but is not documented within the embedded programming guide?

  • 0
    Guru 80425 points

    Hi Kevin,

    Why do you need to read MAC address using embedded programming code? Do you want to create own development image for each device separately?

    Yes, there is more commands but they are not documented and TI does not provide detail documentation about them.

    1) Yes, it is (at least for CC3220 devices, and for CC3235 I expect that this will be same). You can do small "reverse engineering" by capturing UART communication.

    2) Lets say image creator at Uniflash is written at Python 2.7. I expect I don't need to say more Slight smile

    Jan