Re: Universal Demo Remover.app.zip

0 views

Skip to first unread message

Message has been deleted

Onofre Alamillo

unread,

Jul 8, 2024, 12:44:41 AM7/8/24

to tolningrumen

I am working with an NXP MTRCKTSPS5744P dev kit and got a PE Micro multilink universal FX connector to be able to flash code to it. When trying to flash the demo code, following the guide here, I encounter errors. Weirdly, the errors aren't consistent. The latest error I am getting is error 216. Here is the console output:

What can you see in the affected area (01002000-01002B77 as I can see in the log) when you attach the debugger? You can take a look at this thread - it describes how to attach the debugger without loading of new code:

Universal Demo Remover.app.zip

Download File https://tinourl.com/2yMaEZ

Thanks for your reply. I did manage to connect to the board without flashing code, but I'm not sure how to check the block in question, could you perhaps tell me where to look to find that information?

stm_periodic_interrupt_mpc5744p could be a good one. It uses only one GPIO, so you can only comment out PINS_DRV_Init function and toggling in interrupt by PINS_DRV_TogglePins to be sure it does not touch the pins. If you can load this project, I would try to put some constant arrays to make the project bigger.

If you can see all '??' in the memory map, it means it cannot be read, probably due to double bit ECC errors. But the erase should do the recovery. If not, the flash could be damaged for some reasons.

I downloaded and ran the utility. There was not reset script originally running, so I went to Configuration>Automated Script Options and linked the reset script that was running in the S32 IDE, so if this script was the issue this would not be solved. When I ran the script, I saw that all the registers were set back to 0, so I assume it is at least doing something. I still only saw XX in the memory window, as you suggested might happen.

Once I did all this, I went back to S32 and tried flashing the periodic_interrupt project again, but it still didn't work and the error was the same. I have also attached my workspace to this post if you want to take a look at it and see if the error is caused by something in there.

Do you know the history of this MCU? Is it brand new or did you got it from someone? Did anyone play with DCF records? There's a feature called OTP (One Time Programable) Blocks when a flash block can be make OTP by writing a DCF record to the UTEST flash.

I think it was possible to execute the command from the utility, using the reset script that was getting used in the S32 IDE (see attached screenshot). However, I still encounter the same error when trying to program the flash.

As far as I know, the only time this MCU was flashed before was at NXP when putting the MTRCKTSPS5744P_S32DS project on it as part of the motor control dev kit. We have had it for a while, but we had not flashed anything to it as we did not have a jtag or nexus cable, but we did play around in freemaster a bit, mostly checking and controlling the run states. This issue is therefore on out first attempt at flashing code to the MCU.

And as far as I know, the only time the flash was erased was when trying to flash and debug the MTRCKTSPS5744P_S32DS project the first time on my end, which was using the same reset script as I used in the pemicro utility

I had some issues trying to install a new version of the plugin as my company's firewall was getting in the way. I can however get updates from S32 Design Studio for Power Updates, and the GNU E200 PEMicro Interface Debugging Support does show up here. When I tried to install that one, S32 told me that I had a newer one installed.

I have submitted a ticket with my company's IT system, but in the meanwhile is there anyway to download the package and perform the update manually? Or is the one I have currently installed, which is version 2.0.4.202103012147, good enough?

Now I realized that that you probably used ICDPPCNEXUS.EXE because you was talking about reset script. My fault, I should provide more details what to do. Let me describe how to use the Pemicro utility in detail:

Thanks a lot for the information. Unfortunately, I am currently on winter break (I am an intern and cannot work during break) and will not be able to work on it until mid January at the earliest. I will try your solution as soon as I get back and let you know then.