CCS/UNIFLASH: Error trying to run uniflash_setup_3.4.1.00012.bin

Hi,

I suspect that Uniflash 3.4.1 was never fully validated with Ubuntu 18.04, therefore the chances of having a problem are very high (too many changes between the Linux versions). In this case, can you try to download the latest version 5.0.0? It does work with Sitara devices.

processors.wiki.ti.com/.../CCS_UniFlash_v5.0.0_Release_Notes

The major reason to try the newer release is that it is actively supported.

Hope this helps,
Rafael

Hello Rafael,

I downloaded and installed Uniflash 5.0.0 however I cant find the AM335X chips in the chips/boards available. Also, in the instructions I was following (https://octavosystems.com/app_notes/bare-metal-on-osd335x-using-u-boot/) they said that I needed to install a BeagleBone Black patch onto the system. Is there a way to do this with the 5.0.0? Thanks!

Hello Rafael,

I also installed Ubuntu 16.04 and tried installing Uniflash 3.4.1 with the exact same error as when I was on 18.04. Just letting you know that I went down this path as well. The instructions I was following said that they used Ubuntu 16.04 as well, so its weird that this is happening. If you recommend to use Uniflash 5.0.0, can you reply to my last post? Thanks!

I am also attaching the log file I got when I tried installing 3.4.1 on Ubuntu 16.04. 

2313.uniflash_3.4.1.00012.log

Hello Rafael,

Thanks for the update. I will attempt to use Uniflash v5 and see if I can modify the instructions I have from v3.4.1 to it.

I am also trying to get the instructions to work on Windows which did install successfully I believe (no errors on any of the installations). I am running into issues making the binary file necessary to boot to the AM3358 as per the instructions (https://octavosystems.com/app_notes/osd335x-eeprom-during-boot/#_Toc382081428

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -ldrivers

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lutils

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lplatform

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lsystem_config

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lc

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lgcc

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -ldrivers

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lutils

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lplatform

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lsystem_config

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lc

C:\Program Files (x86)\GNU Tools ARM Embedded\4.7 2012q4\bin\arm-none-eabi-ld.exe: cannot find -lgcc

I dont know if this is up your alley, but if you have any advice on how to solve this issue that would be great! Updating the EEPROM of the chip is a very crucial part that I need to do in order to move forward with my design with the AM3358.

Thanks!

Hi Rafael,

So I downloaded Uniflash v5.0 on my Ubuntu 18.04 VM successfully. I was also able to successfully make the binary file necessary to send to the PocketBeagle. Right now I am having issues sending the data over to the processor. Following the instructions you provided me (software-dl.ti.com/.../index_board.html I write:

sudo ./dslite.sh --mode processors - c /dev/ttyUSB0 -f <path_to_binary_file>

Everything seems to be going well. I get:

Flashing Flash Writer to RBL..
Opening Port successful!

But then it hangs at this point. I let it sit for about 5 mins and I do not think it should take this long. I also opened a UART port using:

sudo screen /dev/ttyUSB0 115200

I do not get anything in this this terminal while the previous line was running.

I power the pocket beagle with USB power and for communication I am using a FTDI cable (www.adafruit.com/.../70) connecting:

FTDI uP
GND GND
TX RX
RX TX

Am I missing anything in my command? Has other people run into this issue before? Let me know if you need more information.

Thanks!

Isaac,

Please apologize for the delay; this week we had product releases and everything got backed up.

Let me ping someone more knowledgeable than I in the Uniflash/Sitara operation.

Regards,
Rafael

Hi,

Can you please share below details

- What is the boot mode setting of the board. Is it set to UART boot
- Have you made changes to the Uniflash programmer to support your platform? Currently BeagleBone/PocketBeagle are not supported officially

- Pratap.

1. I have set it to UART mode. The chip automatically goes to that mode when no SD card is connected.

2. PocketBeagle uses an AM335x internally, so thats why I believed it would work. Uniflash 3.4.1 supported its so thats why I also assumed 5.0 supported it (it also said that it was supported on the website).

Hi,

Can you please check the following and update:
1. Power On the board and check if character 'C' is printed on the serial console.
2. From the log shared above, I believe you are trying to transmit Flash Programmer binary to RBL. Please share the details of the Flash Programmer binary that are you transmitting using uniflash?

Please check the list of supported platforms here software-dl.ti.com/.../index_board.html

Hi,

Were the suggestions provided by the other users helpful to have further progress on this?

The reason is that, since Uniflash is not returning any errors, from a pure tools standpoint we can't necessarily pinpoint the root cause for the problem - any logs coming from the tool would not expose anything in addition to what is already shown in the console view you are seeing.

Therefore this is a system-level issue.

By the way, I was able to connect to my BeagleBone Black using the procedure mentioned in the Processors SDK User's Guide, but I couldn't program the Flash Writer to it. Therefore, I suspect that at least this board is not fully supported.

Regards,
Rafael