• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 719 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCS/IWR1443BOOST: Verification failed: Internal error while writing 0x0001F550

Sushen T
Intellectual 555 points
Part Number: IWR1443BOOST
Other Parts Discussed in Thread: IWR1443, MMWAVE-SDK, IWR1642BOOST, IWR1642

Tool/software: Code Composer Studio

Hello,

We are using the IWR1443BOOST RevA. We modified the code to run using CAN. While building the project we do not get any errors but while debugging and uploading to the board we get an error "Verification failed: Internal error while writing 0x0001F550". I should however mention that we changed the memory allocation of Prog_RAM. Could this be the issue? If yes, how do we change the allocation such that the Prog_RAM can fit our code. This error does not occur when we run the out of the box demo with the modified memory allocation.

The original allocation is :

MEMORY{
PAGE 0:

VECTORS (X) : origin=0x00000000 length=0x00000100 
PROG_RAM (RX) : origin=0x00000100 length=0x0001FF00 
DATA_RAM (RW) : origin=0x08000000 length=0x00010000 
L3_RAM (RW) : origin=0x51020000 length=0x00040000 
HWA_RAM (RW) : origin=0x52030000 length=0x00010000 

PAGE 1:
L3_RAM (RW) : origin=0x51020000 length=0x00040000
}

Modified allocation is :

MEMORY{
PAGE 0:

VECTORS (X) : origin=0x00000000 length=0x00000100
PROG_RAM (RX) : origin=0x00000100 length=0x00020F58
DATA_RAM (RW) : origin=0x08000000 length=0x00010000
L3_RAM (RW) : origin=0x51020000 length=0x00040000
HWA_RAM (RW) : origin=0x52030000 length=0x00010000

PAGE 1:
L3_RAM (RW) : origin=0x51020000 length=0x00040000
}

If it is not an issue with the memory, please suggest what else it could be.

Thanks in advance,
-Sushen

  • 0
    TI__Mastermind 30405 points
    Hi Sushen,

    Please allow me a couple of days to look into this. I'll get back to you by 10/13. Thanks for your patience.

    Regards
    -Nitin
  • 0 in reply to Nitin Sakhuja
    TI__Mastermind 30405 points

    Hi Sushen,

    Thanks for the patience.

    Whether you can increase the code memory allocation (at the expense of Radar Cube memory) depends upon the revision of the IW1443 silicon on your EVM. The following picture shows how to identify the ES version of the 1443 device. This can also be identified indirectly by knowing the version of SDK you're using.

    1. IWR1443 ES2.0: ES2.0 is compatible only with MMWAVE-SDK 1.2.0.5 and vice-versa. The program memory can not be increased beyond 128KB. Please refer to the Device datasheet under section 6.4.2 Master(Control) System for the memory map and allocation options available.
    2. IWR1443 ES3.0: i.e. the production version of the device, is compatible only with MMWAVE-SDK 2.1.0.4 (and above) and vice-versa. The amount of usable memory is increased by 128KB on this revision as specified in the device errata. On ES3.0, you can allocate up to 2 more banks (64KB each) to program memory thereby creating a total of 256KB program space (reducing the Radar cube memory by the same amount).
      1. This is done by changing the SHMEM (Shared Memory Allocation) variable in the file C:\ti\mmwave_sdk_02_01_00_04\packages\ti\common\mmwave_sdk_xwr14xx.mak.
      2. The default used for building the SDK demo is 0x00000006 which allocates 6 banks (i.e. 384KB) for Radar Cube and 128KB for program space.
      3. Other examples are provided in the same makefile which take away banks (up to a maximum of 2) from Radar cube space and add it to the program memory.
      4. For instance: 0x00000105 increases the program memory to 192KB while reducing Radar cube to 320KB.  Refer to the Image Generator user guide under section 2.2 (Multicore image generation) to understand the SHMEM allocation in more detail. C:\ti\mmwave_sdk_02_01_00_04\packages\scripts\ImageCreator\Image_Creator_User_Guide.pdf

       

    Regards

    -Nitin

  • 0 in reply to Nitin Sakhuja
    Intellectual 555 points
    Hi Nitin,
    We are using ES 2.0. So this means we cannot increase the program memory.. We are going to purchase the IWR1642BOOST. Hope this does not have limitations such as the ES2.0 version.
    Thanks
    -Sushen
  • 0 in reply to Sushen T
    TI__Mastermind 30405 points
    Sushen,

    Please note that IWR1642 has 2 TX channels (as compared to 3TX channels on IWR1443) so you don't get elevation angle information on IWR1642BOOST. Please consider the requirements of your application.

    I would also like to re-iterate that IWR1443 ES3.0, i.e. the production version of IWR1443 allows you to increase program memory to a max of 256 KB as explained earlier and it is available on the latest IWR1443BOOST EVM.

    Regards
    -Nitin
  • 0 in reply to Nitin Sakhuja
    Intellectual 555 points
    Hi Nitin,
    The main attraction to pick up a 1642 over a 1443 is the on board hardware to perform clustering operations. Our main application is for object detection within a workspace of any machine. Please suggest which would be better. Ideally, we were looking at using the people counting demo and modify it as per our requirement.
    Regards,
    -Sushen