CTRL/STAT.STICKERR set

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

CTRL/STAT.STICKERR set

508件の閲覧回数
anuragm_ec1991
Contributor I

Hello Team,

I am trying to use S32k148EVB along with the Green Hills v4 probe.

I am not able to establish successful communication between the debugger probe and the target board. Since if I pass any command its throws me this error CTRL/STAT.STICKERR set.

I could not find the proper solution to rectify this issue.

Any quick solution to this error would be appreciated.

I believe this error occurred after I was able to load my application on to the target flash memory.

Thanks and Regards

Anurag Mahajan

Design and APplication Engineer

0 件の賞賛
4 返答(返信)

468件の閲覧回数
anuragm_ec1991
Contributor I

Hi Lukas,

 
Many thanks for your email and information.
I have added the S-Rec files in the attachment for your reference.
As I could not read and find out the information properly in the files.
Please let me know in case you need any additional information.
 
Thanks and Regards
Anurag Mahajan
0 件の賞賛

454件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi Anurag,

it looks like there's some garbage on the 0x400. The security seems to be enabled and FOPT contains some weird value. I guess that's not intention.

When you create a project in S32 Design Studio, this field is placed to 0x400:

/* Flash Configuration */
.section .FlashConfig, "a"
.long 0xFFFFFFFF /* 8 bytes backdoor comparison key */
.long 0xFFFFFFFF /* */
.long 0xFFFFFFFF /* 4 bytes program flash protection bytes */
.long 0xFFFF7FFE /* FDPROT:FEPROT:FOPT:FSEC(0xFE = unsecured) */

Is there something similar in your project?

I can see that mass erase is enabled, so you can try to perform mass erase. But if CSE is enabled, it won't be possible to recover because it would be necessary to destroy the partition as a first step. And that would not be possible if you can't establish the connection.

Regards,

Lukas

0 件の賞賛

450件の閲覧回数
anuragm_ec1991
Contributor I

Hi Lukas,

Thanks again for your reply and information.

I believe our probe is not able to get access to the CPU memory since it is not able to read the status of the debug port/register. 

I tried reading and writing to that memory using the probe however it throws the memory read and writes error.

I am not sure if the mass error is possible as there is no access to the memory till now using the debugger probe.

However, I will try to work out on the points you mentioned and let you know.

Thanks and Regards

Anurag

0 件の賞賛

475件の閲覧回数
lukaszadrapa
NXP TechSupport
NXP TechSupport

Hi,

I'm sorry for delayed response caused by Christmas holidays.

Do you know what was loaded to Flash configuration field at 0x400? We do not have Green Hills v4 probe here, so the only idea I have is that some garbage was loaded to the 0x400. If you still have mentioned application, please check the content of Flash configuration field in s-record file.

Regards,

Lukas

0 件の賞賛