Aurix flashing failed after flashing DRIVE Software 10.0

Hello again,

Everytime it fails on same spot:

here is flashing log:

my board version is E3550: 699-63350-0001-500 B.2 RWO

bin files:
DRIVE-V5.1.6-E3550-EB-Aurix-With3LSS-StepA-3.05.04.hex
DRIVE-V5.1.x-E3550-NV-Aurix-UPDATE-StepA-1.29.10.hex

If someone have some idea I would be grateful.

Thanks,
Nikola

This issue seems to only happen with Infinion Memtool 4.8 (new version).
Please try with not checking the “Eanble” checkbox to ignore UCB section for now. UCB does not change for long time so it’s ok to ignore it.

Important: In any case, do NOT click erase button to erase the UCB area. Once UCB is erased, the chip is dead.

Or do you have a chance to try it?

This issue seems to only happen with Infinion Memtool 4.8 (new version).
Please try with not checking the “Eanble” checkbox to ignore UCB section for now. UCB does not change for long time so it’s ok to ignore it.

Important: In any case, do NOT click erase button to erase the UCB area. Once UCB is erased, the chip is dead.

Or do you have a chance to try it?

May I know you are using v4.7 or v4.8?

I tried with both 4.7 and 4.8, with Enable checked and unchecked. I also didn’t add the blocks related to UCB and UPDATE was successfully finished. But the xaviars can’t start anyway and AURIX is in Target reset mode.

I found you created the similar topic in Feburary.

May I know if the system is never working after your receiving it?
What happened in between the system working and not working?
Thanks!

Yes , after posting topic from February I managed to flash the Aurix but now I have problem with locked UCB section whic is different problem.

Could you check if any relevant UART messages about this?

I don’t have access to uart since Aurix is in target reset mode.

Has it ever been working after you receiving the system (even before you flashing anything)? What happened in between the system working and not working? Was the system ever in a vehicle? Do you have any other system? Thanks!

Yes, it worked fine with Drive Software 9. Then I think that I locked BMHD1 section, probably I clicked on ‘Erase configuration’ button but i’m not sure about that. Then I used BMHD0 and still was able to flash .hex files from Drive Software 9 and everything worked fine even with that UCB_BMHD1 locked. Then when I tried to upgrade to newest version it fails on UCB section (described in comments above).
Thanks,
Nikola

Is “showvoltages” command available in your aurix console? If yes, could you help to provide the status by running it? If no, please refer to below post to flash IFW firmware and then get the status.

Yes, but how to copy anything on Tegra B if Tegra B doesn’t boot because Aurix is in target reset mode… I already described that in posts above… Thanks.

How do you tell you locked BMHD1 section?

Using 4.7 with the “Eanble” checkbox checked, can you flash successfully?

Yes, tried with 4.7 Enable checked and unchecked and also with 4.8 Enable checked and unchecked.
But now after multiple tries I can’t even connect to MCU…

Thanks,
Nikola

Did you mean you cannot access aurix via minicom + uart? Did you erase the UCB section (where BMHD are located)?

Yes, I can’t acces aurix via minicom + uart.

Also I locked UCB_BMHD1 (or erased, i’m not sure) on PFLASH0, It’s all gray and I’m unable to change anything. But if I remember I was able to flash it after that and everything worked fine (with old image), I used UCB_BMHD0 for Internal start for Flash (that was few mnonths ago),
but maybe now I have problems with this new software because of that:

Thanks

Are you still able to use Memtool + UART to connect to the chip?

No.