WARNING: Failed to read memory @ address 0x00000000

cancel
Showing results for 
Search instead for 
Did you mean: 

WARNING: Failed to read memory @ address 0x00000000

2,444 Views
Contributor III

Hi,

 

I'm running k66 with MQX 4.02. I'm getting the warning randomly. When this happens the debugger is disconnected but the target keeps running and it appears it runs correctly.

Any idea how to debug?

 

Thanks,

Ariela

Labels (1)
11 Replies

77 Views
Contributor III

I have the same issue in eclipse. I am using LPC1769 and segger EDU for debugging. What should i do?

0 Kudos

77 Views
Contributor III

Hello,

I have exactly the same issue.
I'm using the FRDM-K66 and Kinetis (IDE).
When I try to monitor the value of registers, this message appears on the console.

capture.JPG
Do you have any idea?

Thanks,

Benjamin

0 Kudos

77 Views
NXP Employee
NXP Employee

Hi Benjamin,

I would recommend you to enter a new thread for this question.

Thanks in advance!

Best Regards,
Carlos Mendoza
Technical Support Engineer

0 Kudos

77 Views
NXP Employee
NXP Employee

Hi Ariela,

Could you tell us which IDE version and Flash Programmer are you using?

Does this disconnection warning happens only with a specific project?

Thanks in advance!

Best Regards,

Carlos Mendoza

Technical Support Engineer

0 Kudos

77 Views
Contributor III

Hi Carlos,

I'm using KDS 3.1.0 IDE with J-Link.

The disconnection happens for the only project I'm working with.

Thanks,

Ariela

0 Kudos

77 Views
NXP Employee
NXP Employee

Hi Ariela,

Could you share your project? If the disconnection happens only with that project then please make sure that you are not changing the function of the debugging pins in runtime.

Best Regards!

Carlos Mendoza

Technical Support Engineer

0 Kudos

77 Views
Contributor III

Hi Carlos,

Please find the attached project file.

Note that the problem appears sporadically. I can't specify when it happens and I can't reproduce.

Another stability issue I encounter is that sometimes the application gets stuck at lwmemget_next_block_internal in lwmem.c.

SW is looping forever since block_ptr->BLOCKSIZE equals 0.

The call stack is:

Thread #1 (Suspended : Signal : SIGTRAP:Trace/breakpoint trap)

lwmemget_next_block_internal() at lwmem.c:2,002 0x31f84

taskdestroy_internal() at task.c:938 0x2ceae

taskdestroy() at task.c:1,090 0x2d0c4

taskexit_function_internal() at task.c:3,119 0x2d722

lwsempost() at lwsem.c:579 0x3042c

I've found reference to a known issue in lwmem allocation and have taken the fix but it doesn't seem to help.

Thanks,

Ariela

0 Kudos

77 Views
NXP Employee
NXP Employee

Hi Ariela,

Thanks for your response and the information. Just one thing, could you attach the complete project folder?

Best Regards!

Carlos Mendoza

Technical Support Engineer

0 Kudos

77 Views
Contributor III

Here it is.

Thanks,

Ariela

0 Kudos

77 Views
NXP Employee
NXP Employee

Hi Ariela,

Apologies for the delay, I was out on vacations.

Are you still having the disconnection issue? I saw on the below thread that you moved to MQX4.2, is the disconnection problem also happening on this new project?

TCP send failure after reopening a socket

Best Regards!

Carlos Mendoza

Technical Support Engineer

0 Kudos

77 Views
Contributor III

Hi Carlos,

Since I've upgraded to 4.2.2 I haven't encountered this issue.

Thanks,

Ariela