Is it compulsory to erase UCB area before flashing any valid data to UCB

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
abhishekmahto16
Level 1
Level 1
First reply posted First question asked Welcome!

I m working in bootloader updater application. In my application I m updating bootloader area, MDT, HSM and enabling HSM using UCB20 and UCB28.

In standalone testing using MVD tool i m facing problem that after updater functionality is over control is not coming to bootloader.

In my updater application after updating all area and enabling HSM, I m invalidating the updater application and then performing ECU reset operation so that in next cycle control should come to updated bootloader.

With debugger control is coming to bootloader but in standalone control is not coming to bootloader after updater process.

I checked all updated area and flashing is happening properly.

Yesterday while testing one issue occurred during this process.

Now when I m connecting trace32 getting debug port fail error. 

Query need to resolve:

Q1: Is it compulsory to erase before flashing to UCB area.

Q2: After enabling HSM using UCB, control is not coming to bootloader. But If i exclude updating HSM and enabling HSM from my updater application I m able to get control in bootloader in standalone testing.

Q3: How I will remove debug port fail error issue. I am not able to see any memory dump area.

 

Any inputs will be very helpful for me.

Thanks

 

 

 

 

 

0 Likes
1 Solution
Sharath_V
Moderator
Moderator
Moderator
First comment on blog 250 sign-ins 100 replies posted

Hi @abhishekmahto16 ,

This thread should solve your Q1 and Q3 queries.

Q2: I assume this is due to some conditions not fulfilled during HSM update, like maybe some valid or invalid patterns not written properly. We need more detailed info on this to solve or reproduce the issue.

View solution in original post

0 Likes
5 Replies
Nambi
Moderator
Moderator
Moderator
500 replies posted 50 likes received 5 likes given

Hi,

Could you let us know the device part number being used here?

Best Regards.

0 Likes

Hi Nambi,

 

Device part number- 8P4G 609-21657-00

 

Thanks,

Abhishek kr

0 Likes
Nambi
Moderator
Moderator
Moderator
500 replies posted 50 likes received 5 likes given

Hi Abhishek,

I wanted to understand the part number details similar to TC397 or TC233.

Best Regards,
Nambi.

0 Likes

Ohh sorry,

TC387 TP

 

 

0 Likes
Sharath_V
Moderator
Moderator
Moderator
First comment on blog 250 sign-ins 100 replies posted

Hi @abhishekmahto16 ,

This thread should solve your Q1 and Q3 queries.

Q2: I assume this is due to some conditions not fulfilled during HSM update, like maybe some valid or invalid patterns not written properly. We need more detailed info on this to solve or reproduce the issue.

0 Likes