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.

  • TI Thinks Resolved

TMS320C6748: Can't load secure DSP with GenericSecureUartHost.exe

Part Number: TMS320C6748

Trying to load my program in to a secure C6748 (E) using GenericSecureUartHost.exe.
I read everything I could find here.

This is the response from the loader:

(File IO): Read 149516 bytes from file C:\Projects\CCS\OMAPL138_C6748_Generic_Security\OMAP-L138_Secure\GNU\AISUtils\MXS_Gmbl.bin.
(Serial Port): Opening COM4 at 115200 baud...
(AIS Parse): Read magic word 0x41504954.
(AIS Parse): Waiting for BOOTME... (power on or reset target now)
(AIS Parse): BOOTME received!
(AIS Parse): Performing Start-Word Sync...
(AIS Parse): Performing Ping Opcode Sync...
(AIS Parse): Processing command 0: 0x58535920.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Secure key loading, entering secure mode.
(AIS Parse): Processing command 1: 0x58535923.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Setting boot exit mode...
(AIS Parse): Set exit mode to 0x00000000.
(AIS Parse): Processing command 2: 0x5853590D.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Executing function...
(AIS Parse): Secure mode; sending signature.
(AIS Parse): Processing command 3: 0x58535921.
(AIS Parse): Performing Opcode Sync...
(AIS Parse): Loading encoded section...
(AIS Parse): Loaded 145216-Byte section to address 0x11800000.
(AIS Parse): Processing command 4: 0x58535921.
(AIS Parse): Performing Opcode Sync...
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(Serial Port): Read error: The operation has timed out.
(AIS Parse): I/O Error in read!
(System): Boot aborted by user.
(Serial Port): Read error: The I/O operation has been aborted because of either a thread exit or an application request.

Please help.

  • In reply to Daniel Allred:

    There seems to be no change:

    Command:
    SecureHexAIS_OMAP-L138 -ini Secure.ini -otype binary -o MXS_Gmbl.ais MXS_Gmbl.out

    C:\Projects\CCS\OMAPL138_C6748_Generic_Security\OMAP-L138_Secure\GNU\AISUtils>SecureHexAIS_OMAP-L138 -ini Secure.ini -otype binary -o MXS_Gmbl.ais MXS_Gmbl.out
    -----------------------------------------------------
    TI Secure AIS Hex File Generator for OMAP-L138
    (C) 2011, Texas Instruments, Inc.
    Ver. 1.25
    -----------------------------------------------------


    Creating boot image for a generic secure device.
    INFO: Boot exit type has been selected as NONSECURE.
    WARNING: Encrypted Key Header data is absent - generating plaintext version.
    The Customer Encryption Key will be transferred in plaintext!
    WARNING: Generic Secure device was specified, but no input sections were indicated for encryption.
    Only boot image signing will take place.
    INFO: Current SHA algorithm is SHA256.
    Begining the Secure AIS file generation.
    AIS file being generated for bootmode: NAND.
    Signature Hash: 03-4A-6E-78-B5-52-94-E3-50-40-C7-47-0F-6F-03-7A-07-27-9B-7A-97-48-04-1A-32-45-6D-99-ED-56-9B-FB
    Signature Byte Count = 60
    Parsing the input object file, MXS_Gmbl.out.
    Signature Hash: DD-89-C5-19-EB-6A-37-19-D8-CD-00-E6-68-D5-1C-BC-67-8C-10-D4-EB-15-74-6B-BA-D0-D9-15-5D-37-A8-30
    Signature Byte Count = 149392
    AIS file generation was successful.
    Wrote 149516 bytes to file MXS_Gmbl.ais.
    Conversion is complete.

    ----------------------------------------------------------------------------------------------------------------------
    GenericSecureUartHost.exe
    "
    (File IO): Read 149516 bytes from file C:\Projects\CCS\OMAPL138_C6748_Generic_Security\OMAP-L138_Secure\GNU\AISUtils\MXS_Gmbl.ais.
    (Serial Port): Opening COM4 at 115200 baud...
    (AIS Parse): Read magic word 0x41504954.
    (AIS Parse): Waiting for BOOTME... (power on or reset target now)
    (AIS Parse): BOOTME received!
    (AIS Parse): Performing Start-Word Sync...
    (AIS Parse): Performing Ping Opcode Sync...
    (AIS Parse): Processing command 0: 0x58535920.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Secure key loading, entering secure mode.
    (AIS Parse): Processing command 1: 0x58535923.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Setting boot exit mode...
    (AIS Parse): Set exit mode to 0x00000000.
    (AIS Parse): Processing command 2: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 3: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading section...
    (AIS Parse): Loaded 145216-Byte section to address 0x11800000.
    (AIS Parse): Processing command 4: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (Serial Port): Read error: The operation has timed out.
    (AIS Parse): I/O Error in read!
    (Serial Port): Read error: The operation has timed out.
    (AIS Parse): I/O Error in read!
    (System): Boot aborted by user.
    (Serial Port): Read error: The I/O operation has been aborted because of either a thread exit or an application request.
    "
    -----------------------------------------------------------------------------------------------------------------
    The Secure.ini file:

    [General]
    busWidth = 16
    BootMode = NAND
    crcCheckType = NO_CRC
    seqReadEn = ON

    [Security]

    securityType = GENERIC
    bootExitType = NONSECURE
    ;encryptSections = ALL
    encryptionKey = 4A7E1F56AE545D487C452388A65B0C05
    ;rsaKeyFileName =
    genericSHASelection = SHA256
    ;genKeyHeaderFileName = gen_keyhdr_encrypted.bin

    ;[PLLANDCLOCKCONFIG]
    ;[PLL0CONFIG]
    ; |------24|------16|-------8|-------0|
    ; PLL0CFG0: | CLKMODE| PLLM | PREDIV | POSTDIV|
    ; PLL0CFG1: | RSVD | PLLDIV1| PLLDIV3| PLLDIV7|
    ;PLL0CFG0 = 0x00120000
    ;PLL0CFG1 = 0x00010113

    ; |------24|------16|-------8|-------0|
    ; PLL1CFG0: | PLLM| POSTDIV| PLLDIV1| PLLDIV2|
    ; PLL1CFG1: | RSVD | PLLDIV3|
    ;[PLL1CONFIG]
    ;PLL1CFG0 = 0x00010101
    ;PLL1CFG1 = 0x00000005

    ;[SecureLegacy]
    ;encryptImage = TRUE

    [TAPSCONFIG]
    TAPSCFG = 0x0000FFFF

    ;[BinaryInputFile]
    ; L2 RAM 0x11800000 256K
    ; DDR2 0xC0000000 256M
    ;fileName = MXS_Gmbl.out
    ;loadAddress = 0x11800000
    ;entryPointAddress = 0x11800000
    ;entryPointAddress = 0xc1080000 (in DDR2)
    ;useEntryPoint = TRUE
    ;encrypt = TRUE
  • In reply to Daniel Allred:

    It does not work:
    --------------------------------------------------------------------------
    Command:
    SecureHexAIS_OMAP-L138 -ini Secure.ini -otype binary -o MXS_Gmbl.ais MXS_Gmbl.out

    Response:
    C:\Projects\CCS\OMAPL138_C6748_Generic_Security\OMAP-L138_Secure\GNU\AISUtils>SecureHexAIS_OMAP-L138 -ini Secure.ini -otype binary -o MXS_Gmbl.ais MXS_Gmbl.out
    -----------------------------------------------------
    TI Secure AIS Hex File Generator for OMAP-L138
    (C) 2011, Texas Instruments, Inc.
    Ver. 1.25
    -----------------------------------------------------

    Creating boot image for a generic secure device.
    INFO: Boot exit type has been selected as NONSECURE.
    WARNING: Encrypted Key Header data is absent - generating plaintext version.
    The Customer Encryption Key will be transferred in plaintext!
    WARNING: Generic Secure device was specified, but no input sections were indicated for encryption.
    Only boot image signing will take place.
    INFO: Current SHA algorithm is SHA256.
    Begining the Secure AIS file generation.
    AIS file being generated for bootmode: NAND.
    Signature Hash: B6-FE-9F-C5-6B-8C-37-12-39-9E-11-06-56-54-7E-FB-BE-A5-73-A1-60-D3-F3-3B-BF-FB-D4-14-45-D1-7F-E4
    Signature Byte Count = 60
    Parsing the input object file, MXS_Gmbl.out.
    Signature Hash: DD-89-C5-19-EB-6A-37-19-D8-CD-00-E6-68-D5-1C-BC-67-8C-10-D4-EB-15-74-6B-BA-D0-D9-15-5D-37-A8-30
    Signature Byte Count = 149392
    AIS file generation was successful.
    Wrote 149516 bytes to file MXS_Gmbl.ais.
    Conversion is complete.

    --------------------------------------------------------------------------
    Command:
    GenericSecureUartHost.exe

    Response:
    (File IO): Read 149516 bytes from file C:\Projects\CCS\OMAPL138_C6748_Generic_Security\OMAP-L138_Secure\GNU\AISUtils\MXS_Gmbl.ais.
    (Serial Port): Opening COM4 at 115200 baud...
    (AIS Parse): Read magic word 0x41504954.
    (AIS Parse): Waiting for BOOTME... (power on or reset target now)
    (AIS Parse): BOOTME received!
    (AIS Parse): Performing Start-Word Sync...
    (AIS Parse): Performing Ping Opcode Sync...
    (AIS Parse): Processing command 0: 0x58535920.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Secure key loading, entering secure mode.
    (AIS Parse): Processing command 1: 0x58535923.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Setting boot exit mode...
    (AIS Parse): Set exit mode to 0x00000000.
    (AIS Parse): Processing command 2: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 3: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading section...
    (AIS Parse): Loaded 145216-Byte section to address 0x11800000.
    (AIS Parse): Processing command 4: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (Serial Port): Read error: The operation has timed out.
    (AIS Parse): I/O Error in read!
    (Serial Port): Read error: The operation has timed out.
    (AIS Parse): I/O Error in read!
    (System): Boot aborted by user.
    (Serial Port): Read error: The I/O operation has been aborted because of either a thread exit or an application request.

    --------------------------------------------------------------------------
    Hi Lets try to solve this problem.
    Thanks
    Attila
  • In reply to Patyi:

    Current ini file:

    [General]
    busWidth = 16
    BootMode = NAND
    crcCheckType = NO_CRC
    seqReadEn = ON

    [Security]

    securityType = GENERIC
    bootExitType = NONSECURE
    ;encryptSections = ALL
    encryptionKey = 4A7E1F56AE545D487C452388A65B0C05
    ;rsaKeyFileName =
    genericSHASelection = SHA256
    ;genKeyHeaderFileName = gen_keyhdr_encrypted.bin

    ;[PLLANDCLOCKCONFIG]
    ;[PLL0CONFIG]
    ; |------24|------16|-------8|-------0|
    ; PLL0CFG0: | CLKMODE| PLLM | PREDIV | POSTDIV|
    ; PLL0CFG1: | RSVD | PLLDIV1| PLLDIV3| PLLDIV7|
    ;PLL0CFG0 = 0x00120000
    ;PLL0CFG1 = 0x00010113

    ; |------24|------16|-------8|-------0|
    ; PLL1CFG0: | PLLM| POSTDIV| PLLDIV1| PLLDIV2|
    ; PLL1CFG1: | RSVD | PLLDIV3|
    ;[PLL1CONFIG]
    ;PLL1CFG0 = 0x00010101
    ;PLL1CFG1 = 0x00000005

    ;[SecureLegacy]
    ;encryptImage = TRUE

    [TAPSCONFIG]
    TAPSCFG = 0x0000FFFF

    ;[BinaryInputFile]
    ; L2 RAM 0x11800000 256K
    ; DDR2 0xC0000000 256M
    ;fileName = MXS_Gmbl.out
    ;loadAddress = 0x11800000
    ;entryPointAddress = 0x11800000
    ;entryPointAddress = 0xc1080000 (in DDR2)
    ;useEntryPoint = TRUE
    ;encrypt = TRUE
  • In reply to Patyi:

    Can you please indicate what is the value of the OSCIN that you have used on your custom board. Do the PLLM, divider values match with the OSCIN that you have used. Is the image that you are trying to use loading any section of code into mDDR/DDR2 memory? If there is any load section fro DDR then you need to configure PLL1 and EMIF using your INI script.  Based on your description, this appears to be an IO issue rather than security related issue.

    I recommend that you use the INI sectting from from the file  OMAP-L138_sec2nonsec.ini or OMAP-L138_generic_secure.ini in the OMAPL138 secure package that is available here and try and see if you can unlock the JTAG using a simple binary. Do you have a version  of the board with non-secure device, have you performed any regression tests on the UART interface there is no issues with serial IO?

    I have attached an example JTAG unlock binary that you can try on your board that simply unlocks the JTAG:

    Secure_LCDK.zip

    these have been tested to work on TI evaluation platforms.

    Regards,

    Rahul

    --------------------------------------------------------------------------------------------------------------------------------------
    Please click the
    This resolved my issue button on this post if the responses on this E2E thread answers your question.
    --------------------------------------------------------------------------------------------------------------------------------------

     

  • In reply to Daniel Allred:

    I sent this yesterday but it disappeared!

    I want to continue debugging my problem.

    =====================================================
    My conversion command is:

    SecureHexAIS_OMAP-L138 -ini Secure.ini -otype binary -o MXS_Gmbl.ais MXS_Gmbl.out

    -----------------------------------------------------
    TI Secure AIS Hex File Generator for OMAP-L138
    (C) 2011, Texas Instruments, Inc.
    Ver. 1.25
    -----------------------------------------------------


    Creating boot image for a generic secure device.
    INFO: Boot exit type has been selected as NONSECURE.
    WARNING: Encrypted Key Header data is absent - generating plaintext version.
    The Customer Encryption Key will be transferred in plaintext!
    WARNING: Generic Secure device was specified, but no input sections were indicated for encryption.
    Only boot image signing will take place.
    INFO: Current SHA algorithm is SHA256.
    Begining the Secure AIS file generation.
    AIS file being generated for bootmode: NAND.
    Signature Hash: CC-C8-8C-07-11-76-9B-83-15-8B-14-21-69-E8-EE-DA-85-E2-EB-23-28-AE-FA-BB-04-9F-49-67-55-9F-C9-1F
    Signature Byte Count = 60
    Parsing the input object file, MXS_Gmbl.out.
    Signature Hash: DD-89-C5-19-EB-6A-37-19-D8-CD-00-E6-68-D5-1C-BC-67-8C-10-D4-EB-15-74-6B-BA-D0-D9-15-5D-37-A8-30
    Signature Byte Count = 149392
    AIS file generation was successful.
    Wrote 149516 bytes to file MXS_Gmbl.ais.
    Conversion is complete.
    --------------------------------------------------------------------------

    =====================================================
    My ini file is:

    [General]
    busWidth = 16
    BootMode = NAND
    crcCheckType = NO_CRC
    seqReadEn = ON

    [Security]

    securityType = GENERIC
    bootExitType = NONSECURE
    ;encryptSections = ALL
    encryptionKey = 4A7E1F56AE545D487C452388A65B0C05
    ;rsaKeyFileName =
    genericSHASelection = SHA256
    ;genKeyHeaderFileName = gen_keyhdr_encrypted.bin

    ;[PLLANDCLOCKCONFIG]
    ;[PLL0CONFIG]
    ; |------24|------16|-------8|-------0|
    ; PLL0CFG0: | CLKMODE| PLLM | PREDIV | POSTDIV|
    ; PLL0CFG1: | RSVD | PLLDIV1| PLLDIV3| PLLDIV7|
    ;PLL0CFG0 = 0x00120000
    ;PLL0CFG1 = 0x00010113

    ; |------24|------16|-------8|-------0|
    ; PLL1CFG0: | PLLM| POSTDIV| PLLDIV1| PLLDIV2|
    ; PLL1CFG1: | RSVD | PLLDIV3|
    ;[PLL1CONFIG]
    ;PLL1CFG0 = 0x00010101
    ;PLL1CFG1 = 0x00000005

    ;[SecureLegacy]
    ;encryptImage = TRUE

    [TAPSCONFIG]
    TAPSCFG = 0x0000FFFF

    ;[BinaryInputFile]
    ; L2 RAM 0x11800000 256K
    ; DDR2 0xC0000000 256M
    ;fileName = MXS_Gmbl.out
    ;loadAddress = 0x11800000
    ;entryPointAddress = 0x11800000
    ;entryPointAddress = 0xc1080000 (in DDR2)
    ;useEntryPoint = TRUE
    ;encrypt = TRUE


    =====================================================
    Trying to load with GenericSecureUartHost.exe :

    (File IO): Read 149516 bytes from file C:\Projects\CCS\OMAPL138_C6748_Generic_Security\OMAP-L138_Secure\GNU\AISUtils\MXS_Gmbl.ais.
    (Serial Port): Opening COM4 at 115200 baud...
    (AIS Parse): Read magic word 0x41504954.
    (AIS Parse): Waiting for BOOTME... (power on or reset target now)
    (AIS Parse): BOOTME received!
    (AIS Parse): Performing Start-Word Sync...
    (AIS Parse): Performing Ping Opcode Sync...
    (AIS Parse): Processing command 0: 0x58535920.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Secure key loading, entering secure mode.
    (AIS Parse): Processing command 1: 0x58535923.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Setting boot exit mode...
    (AIS Parse): Set exit mode to 0x00000000.
    (AIS Parse): Processing command 2: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 3: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading section...
    (AIS Parse): Loaded 145216-Byte section to address 0x11800000.
    (AIS Parse): Processing command 4: 0x58535901.
    (AIS Parse): Performing Opcode Sync...
    (Serial Port): Read error: The operation has timed out.
    (AIS Parse): I/O Error in read!
    (Serial Port): Read error: The operation has timed out.
    (AIS Parse): I/O Error in read!
    (System): Boot aborted by user.
    (Serial Port): Read error: The I/O operation has been aborted because of either a thread exit or an application request.


    Please advise

    Attila
  • In reply to Rahul Prabhu:

    Our messages crossed.
    I will do what you asked and let you know.
    Thanks.
    Attila
  • In reply to Rahul Prabhu:

    OSCIN = 24.000MHz
    Your test file programmed.
    ==============================================================================
    (File IO): Read 1580 bytes from file C:\Projects\CCS\OMAPL138_C6748_Generic_Security\OMAP-L138_Secure\GNU\AISUtils\dsp_exitnonsecure_unlockjtag.bin.
    (Serial Port): Opening COM4 at 115200 baud...
    (AIS Parse): Read magic word 0x41504954.
    (AIS Parse): Waiting for BOOTME... (power on or reset target now)
    (AIS Parse): BOOTME received!
    (AIS Parse): Performing Start-Word Sync...
    (AIS Parse): Performing Ping Opcode Sync...
    (AIS Parse): Processing command 0: 0x58535920.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Secure key loading, entering secure mode.
    (AIS Parse): Processing command 1: 0x58535923.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Setting boot exit mode...
    (AIS Parse): Set exit mode to 0x00000000.
    (AIS Parse): Processing command 2: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 3: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 4: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 5: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 6: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 7: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 8: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 9: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 10: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 11: 0x5853590D.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Executing function...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): Processing command 12: 0x58535921.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading encoded section...
    (AIS Parse): Loaded 864-Byte section to address 0x00831000.
    (AIS Parse): Processing command 13: 0x58535921.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Loading encoded section...
    (AIS Parse): Loaded 84-Byte section to address 0x00831360.
    (AIS Parse): Processing command 14: 0x58535906.
    (AIS Parse): Performing Opcode Sync...
    (AIS Parse): Performing jump and close...
    (AIS Parse): Secure mode; sending signature.
    (AIS Parse): AIS complete. Jump to address 0x00831260.
    (AIS Parse): Waiting for DONE...
    (AIS Parse): Boot completed successfully.
    (Serial Port): Closing COM4.
    ==============================================================================

    The PLLM, divider values match with the OSCIN that I use.
    Not using mDDR/DDR2 memory for code or data when loading.
    I have over 30 the boards with non-secure device, did not performed any regression tests on the UART interface but there are no issues with the serial IO.The UART is used for initial programming on about 30 boards. Also the same interface is use on an operating system to connect to a PC to setup and monitor the system.
  • In reply to Patyi:

    Thanks for providing the information.  I have attached the INI file that was used to generate the binary that I shared which seems to be loading fine on your board. Can you use it to regenerate the secure binary using your .out and let us know if there is any change in behavior.

    OMAP-L138_sec2nonsec.zip

    Also, if possible please post the .map file for the binary you are trying to load for our reference.  I am not completely sure what is causing the issue with your binary yet but it could be clock related which is why I was suspecting issue with the PLL setup. 

    Regards,

    Rahul

    --------------------------------------------------------------------------------------------------------------------------------------
    Please click the
    This resolved my issue button on this post if the responses on this E2E thread answers your question.
    --------------------------------------------------------------------------------------------------------------------------------------

     

  • In reply to Rahul Prabhu:

    It does not work with your .ini file.
    How do I post the .map file?
  • In reply to Patyi:

    I uploaded the map file, but not sure if you have it?

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.