• Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 796 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Memory ID errors connecting to OMAP-L138

Thomas Price7137
Intellectual 625 points

Other Parts Discussed in Thread: OMAP-L138

I am currently able to connect to my OMAP-L138 (C6748 side) using a XDS510 USB Emulator without any problems. However, I was trying to get a co-worker's machine to work as well and when he tries to connect to the target using CCS4 (Premium version) it will hang. If he tries to connect to the target using CCS3.3 (again trying to connect to it as a C6748) he will get the following error. Does anyone know why I would not receive this error with my setup but he would see this issue?

Again, on my setup, it all works with exactly the same hardware.

Trouble Reading Memory Block at 0x1c10800 on Page 0 of Length 0x4: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

GEL: Error while executing OnTargetConnect(): target access failed.

Trouble Reading Memory Block at 0x1840020 on Page 0 of Length 0x4: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x1840040 on Page 0 of Length 0x4: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x1840000 on Page 0 of Length 0x4: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x184a600 on Page 0 of Length 0x40: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x184a640 on Page 0 of Length 0x40: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x184ae00 on Page 0 of Length 0x40: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x184ae40 on Page 0 of Length 0x40: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x184a200 on Page 0 of Length 0x80: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x184a280 on Page 0 of Length 0x80: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x1c00004 on Page 0 of Length 0x4: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x1c00004 on Page 0 of Length 0x4: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x1c00004 on Page 0 of Length 0x4: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x712104 on Page 0 of Length 0x340: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.  

Trouble Reading Memory Block at 0x712104 on Page 0 of Length 0x300: Error 0x00000002/-1194 Error during: Memory,  The memory ID is not supported by the hardware.

  • TI__Mastermind 30381 points

    Make sure you are using the right GEL file(s).  If you are using the L138 device, use the ARM & DSP GEL files given in the L138 board support library (BSL).  If you are using the C6748 device, use the DSP GEL file in the C6748 BSL.  Note: Even if connecting to the DSP only on an L138, you still need to use the L138 BSL GEL files; specifically you should run the ARM GEL file since it takes the DSP out of reset.  If all else fails, you can try to put the device in debug boot mode.

  • in reply to Gus Martinez
    Intellectual 625 points

    I have verified that the GEL files match between the system that throws this error and the system that doesn't throw the error. What do you mean by putting the device into debug boot mode?

  • in reply to Thomas Price7137
    TI__Guru**** 483111 points

    With either SW2 or SW7 on the board, you can change the boot mode. See the user guide for the board for more details.

    ki

  • in reply to Ki
    Intellectual 625 points

    Ki-

    I know for sure that the boot mode on the board is Emulator mode. If it weren't in Emulator mode it would hang on both PCs, which is something I've actually experienced on the PC on which the hardware works. Also, I've tried swapping out the XDS510 USB Emulator and that does not seem to be the problem either.

                   -Thomas

  • in reply to Thomas Price7137
    TI__Mastermind 30381 points

    Thomas Price said:
    I know for sure that the boot mode on the board is Emulator mode. If it weren't in Emulator mode it would hang on both PCs, which is something I've actually experienced on the PC on which the hardware works.

    Not necessarily.  Emulation boot mode basically tells the L138 (or C6748) ROM bootloader to wait in a loop, take both cores out of reset, and don't do anything.  In any other boot mode, the L138 (or C6748) the ROM bootloader would proceed with the boot process (load UBL, the uBoot, etc.).  The emulator can connect to the device in any boot mode.  Using emulation boot just puts the breaks on the whole boot process so that you are sure the issues you are seeing are not related to the boot process gone awry.

  • in reply to Gus Martinez
    Intellectual 625 points

    Fair enough, then let me answer in this way. I am able to connect to the ARM on both PCs. I know that the boot switches are set to emulation mode in the hardware. This has been verified on the board. However, on the non-functioning PC he can connect to the ARM but not the DSP. On the functioning PCs (plural) we can connect to both the DSP and ARM. Also, the PC that is experiencing the error connecting to the DSP is also able to connect to MSP processors without any issues.

  • in reply to Thomas Price7137
    TI__Mastermind 30381 points

    Only thing I can think of is to double check your CCS configuration:

    http://processors.wiki.ti.com/index.php/How_to_connect_to_the_OMAP-L138/C6748/AM1808_EVM_board_using_CCS%3F

    The error messages you pointed out before indicate CCS is trying to access several registers (PSC, cache configuration, EDMA).  CCS is doing these accesses because your DSP GEL file is telling it to do so.  I find this perplexing given that the DSP GEL for the OMAP-L138 SOM doesn't do much on connect.  It certainly doesn't access any of the registers being listed in the error log.