AnsweredAssumed Answered

Memtool access of 0x020F.... address space hangs

Question asked by jayakumar2 on Jun 15, 2015
Latest reply on Jun 15, 2015 by Yuri Muhin

Hi fsl friends,

 

I noticed that on my 6sololite board, memtools works fine for some address spaces but causes the system to hang when the 0x020Fxxxx address space is accessed. For example:

 

root@imx6slevk:~# /unit_tests/memtool -32 0x021b8020 1

E

Reading 0x1 count starting at address 0x021B8020

 

 

0x021B8020:  17010000

 

whereas:

 

root@imx6slevk:~# /unit_tests/memtool -32 0x020F4220 1

E

Reading 0x1 count starting at ad

<hang>

 

and another address in that range:

oot@imx6slevk:~# /unit_tests/memtool -32 0x020F4000 1

E

Reading 0x1 count starting at ad

<hang>

 

The system does not complete the printf (shows ad instead of address) and the system hangs. That leads me to suspect that the read transaction causes the system to hang. The same behavior also occurs with devregs so the fault is not specific to memtool. Both use /dev/mem so I presume the issue comes from something to do with memory mapping setup.

 

I'm wondering what could cause this and if you have any advice/suggestions on how to enable userspace access to that region.

 

Thanks,

jaya

Outcomes