J-LinkARM.dll read size problem

  • Hello,

    I am facing a problem on NXP LPC1788 with reading content of the EMAC registers.
    Any attempt to read the content fails with WARNING: Failed to read cacheable memory @ address ADDRESS(e.g.0x20084000, EMAC1).

    My configuration: LPC1788, Ubuntu 12.04, JLinkGDBServer v 4.74 command line "-device LPC1788 -vd -log status.log", Eclipse Juno CDT C/C++, OpenJDK, J-Link
    Firmware: J-Link ARM V8 compiled Jul 17 2013 11:24:15, Hardware: V8.00

    My observations:
    Reading by using JLinkExe, mem32 0x20084000, 1 - success
    Reading by using JLinkExe, mem32 0x20084000, 256 - fails (Could not read memory.)

    From the JLinkGDB log, I can see attempt to read 256 items even if the request requires only 4.
    02-00-00020007-00AA: TB2EBAB40 019:994 JLINK_ReadCodeMem(0x20084000, 0x0004 Bytes, ...) -- CPU_ReadMem(256 bytes @ 0x20084000) -- Data: 00 00 01 10 returns 0xFFFFFFFF (0013ms, 2981ms total)
    03-00-00020007-003D: WARNING: Failed to read cacheable memory @ address 0x20084000
    03-00-00020007-0035: Read 4 bytes @ address 0x20084000 (Data = 0x10010000)

    To the Eclipse is returned - failed.

    The question is: Can I set the read size to respect the request?

    Best
    Martin

  • The Windows version 4.76a works correctly,

    T1464 171:807 JLINK_ReadMem (0x20084000, 0x0004 Bytes, ...) -- CPU_ReadMem(4 bytes @ 0x20084000) -- Data: 02 00 00 00 returns 0x00 (0003ms, 1967ms total)

    Martin

  • Hi Martin,

    Sorry for not getting back to you earlier.
    You were faster than me :)
    Just wanted to write the same.


    Best regards
    Alex

    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: https://www.segger.com/ticket/

    Or you can contact us via e-mail.

  • Hi Martin,

    An update for the Linux version is planned soon (to bring it also to V4.76a).
    Anyhow, I am wondering why it is failing with the old version at all. This area should not be considered as cacheable memory.


    Best regards
    Alex

    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: https://www.segger.com/ticket/

    Or you can contact us via e-mail.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!