TMDSCNCD263P: Uniflash/Bootflow

Marcel Pfeifer said:

1.Question: Does any µC Chip have a RBL SW flashed by default?

At the moment most of the time iam using the board in DEV Bootmode. 

Yes there is a rom code present.

Learn more about bootloaders on Am26x devices:

AM263x MCU+ SDK: Understanding the bootflow and bootloaders

Marcel Pfeifer said:

2. Question: What exactly does DEV Bootmode mean? Where is the code saved? I imagine its in RAM because after every Powercycle the code is gone.

Now i wanna save the code in flash. Academy says ive to put the board into DEV Bootmode, flash and put it to OSPI mode.

Yes your understanding is correct, we use jtag to place code into ram.

For putting code in flash you need to use interface like JTA or UART to send application and write it into flash.

Flashing using UART: AM263x MCU+ SDK: Loading an Application

Flashing using JTAG: Uniflash tool: AM263x MCU+ SDK: TI Uniflash Tool

Marcel Pfeifer said:

3.Question: Now its okay to switch bootmode because ive dip switches but later in our costum board we won't have them. How to flash without changing the bootmode?

You can still use JTAG interface to do the flashing.

Marcel Pfeifer said:

Console in Uniflash says load was successfully. But when i powercycle and change Bootmode to OSPI ( 1 or 8 ) it just prints (over UART):

4.Question: What iam doing wrong?

When i flash with Bootmode OSPI choosen, it prints the following after powercycle:

5.Question: What does that indicate

Looks like some issue with flashing, 

1. What is EVM revison can you attach a pic.

Nilabh Anand said:

3.Question: Now its okay to switch bootmode because ive dip switches but later in our costum board we won't have them. How to flash without changing the bootmode?

You can still use JTAG interface to do the flashing.

So for flashing i don't have to change anything to bootmode? Because in acadamy it says i should switch to DEV mode when flashing via JTAG

Nilabh Anand said:

Looks like some issue with flashing

flashing "sbl_null.release.tiimage" the same way i tried with "sbl_ospi.release.tiimage" works just fine. 

Nilabh Anand said:

1. What is EVM revison can you attach a pic.

its PROC159E2

Marcel Pfeifer said:

So for flashing i don't have to change anything to bootmode? Because in acadamy it says i should switch to DEV mode when flashing via JTAG

Yes it woks even without changing the boot mode as it connects with CPU core and resets the core, then loads the flasher which can write to flash.

Marcel Pfeifer said:

Nilabh Anand said:

Looks like some issue with flashing

flashing "sbl_null.release.tiimage" the same way i tried with "sbl_ospi.release.tiimage" works just fine. 

Nilabh Anand said:

1. What is EVM revison can you attach a pic.

its PROC159E2

Could you please once again the steps mentioned here: software-dl.ti.com/.../GETTING_STARTED_FLASH.html

Nilabh Anand said:

Could you please once again the steps mentioned here: software-dl.ti.com/.../GETTING_STARTED_FLASH.html

I am not sure how this could fix my problem.

First of all this is for AM263x MCU+ SDK and iam using AM263Px MCU+ SDK. As far as i know QSPI isn't running with the flash of AM263P-CC.

Nevertheless i did the steps mentioned in https://software-dl.ti.com/mcu-plus-sdk/esd/AM263PX/09_02_00_56/exports/docs/api_guide_am263px/GETTING_STARTED_FLASH.html

Result stays the same:

Best Regards,
Marcel

Hi Marcel,

Thanks for the correct links, It was a mistake on my side the links I pasted were for am263x, instead of am263px, but you got the point.

I checked this on my setup, I was able to figure out the issue.

It is because of stale binary in Uniflash tool. you can check is using the flashed present in SDK instead of the default one: software-dl.ti.com/.../TI_UNIFLASH_TOOL.html

Steps :1 Build the jtag flasher example for AM263Px-LP

Then use the freshly built .out for custom flasher in Uniflash:

C:\ti\mcu_plus_sdk_am263px_10_00_00_35\tools\flasher\jtag_uniflash\am263px-lp\r5fss0-0_nortos\ti-arm-clang

OR

Meanwhile you can get unblocked by using UART COM port for flashing.:

In the drop down of device Search for AM263Px-LP(Serial), then select the com port

software-dl.ti.com/.../TOOLS_FLASH.html

I am also trying to reproduce it on my setup

Hey Nilabh,

Nilabh Anand said:

I am also trying to reproduce it on my setup

Nilabh Anand said:

I checked this on my setup, I was able to figure out the issue.

Iam not quite sure if i understand you correctly, could you reproduce my issue or not?
Because i dont think its a problem of flashing. As i said before :

Marcel Pfeifer said:

flashing "sbl_null.release.tiimage" the same way i tried with "sbl_ospi.release.tiimage" works just fine. 

So why du you think its a flashing problem?

Nilabh Anand said:

Steps :1 Build the jtag flasher example for AM263Px-LP

Then use the freshly built .out for custom flasher in Uniflash:

Iam using the Controlcard so i build it for AM263Px-CC. Then i get this error when iam trying to flash:

Nilabh Anand said:

Meanwhile you can get unblocked by using UART COM port for flashing.:

In the drop down of device Search for AM263Px-LP(Serial), then select the com port

software-dl.ti.com/.../TOOLS_FLASH.html

Also tryied this. Same result as before. When flashing the sbl_ospi.release.tiimage

flashing sbl_null.release.tiimage shows:


Best Regards

Marcel

Can you share the SBL OSPI .tiimage that you are using let me try that on my setup.

Also one very fundamental question- are you flashing the application image also along with sbl ospi,

As Sbl ospi expects an application image to be at 0x80000 offset else the SBL fails. But you might be already doing doing that, same was mentioned in the document also and you said you have tried it again.

Iam using the prebuild version out of the sdk : mcu_plus_sdk_am263px_10_00_00_35\tools\boot\sbl_prebuilt\am263px-cc.
My addresses look like this:

this are the default ones. I think the 0x60000000 is the base address of the flash and then the 0x800000 is just added to this for the application.

Any progress here, could you reproduce the issue?