• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 32 subscribers
  • Views 241 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.

AWRL6432: How to change memory partition? (to use Data Cube 512KB, Usage 3)

Hayden Kim
Genius 15580 points
Part Number: AWRL6432

Champs,

By default (OOB demo), it is configured to use Data Cube as 256KB (Usage 1).

Can you provide guide how to change it to use Data Cube as 512KB, Usage 3?

Is it correct to apply below two changes?

_

from,
(1) HWASS_SHM_MEM : ORIGIN = 0x60000000, LENGTH = 0x00040000 (linker.cmd)
(2) Uint8_t gMmwL3[0x40000] (motion_detect.c)

to,
(1) HWASS_SHM_MEM : ORIGIN = 0x60000000, LENGTH = 0x00080000 (linker.cmd)
(2) Uint8_t gMmwL3[0x80000] (motion_detect.c)

_

Best regards,

Hayden

  • 0
    TI__Mastermind 38645 points

    Hi, Hayden:

    I see there is some memory partition options listed in the datasheet, section 9.5

    https://www.ti.com/lit/ds/symlink/awrl6432.pdf?ts=1674080125617&ref_url=https%253A%252F%252Fwww.ti.com%252Fproduct%252FAWRL6432

    Let me know if this is helpful.

    Best,

    Zigang

  • 0 in reply to zigang Yang
    TI__Genius 15580 points

    Hi Zigang,

    From the data sheet, he checked the partitioning options.

    He asked how to apply the config options from the OOB demo.

    Can you please check again about config settings in the OOB demo?

    Thanks and regards,

    Hayden

  • 0 in reply to Hayden Kim
    TI__Mastermind 18991 points

    Hi Hayden,

    I believe the changes you are showing are correct. Please allow me to confirm internally and get back to you with an answer tomorrow.

    Best Regards,

    Josh

  • +1 in reply to Josh Dye
    TI__Mastermind 18991 points

    Hi Hayden, 

    Sorry about the delay here. The proposed changes are appropriate. 

    Best Regards,

    Josh

  • 0 in reply to Josh Dye
    TI__Genius 15580 points

    Hello Josh,

    He modified one more thing, "CSL_APP_CPU_SHARED_RAM_U_SIZE" from (0x00040000U) to (0x00080000U).

    There is still an issue of accessing the memory.

    (it was expected  to have access of total 512KB, from 0x6000000 to 0x60080000)

    When he tested with using the Memory Browser tool of CCS,

    He can write (fill) the memory from 0x60000000 to 0x60067FFF, but he cannot write after 0x60068000 (256KB + 160KB).

    So, after the application runs,

       * 0x60000000 ~ 0x6003FFFF : memory was initialized with "0"

       * 0x60040000 ~ 0x60067FFF : memory was not initializes (not 0, random values)

       * 0x60068000 ~ : value remains as "0x00", not changed

    So, how can he write (use) the total 512KB (0x6000000 ~ 0x60080000) memory region?

    Is above sympthom (cannot write memory above 256KB+160KB) expected behavior or not?

    Best regards,

    Hayden

  • +1 in reply to Hayden Kim
    TI__Mastermind 18991 points

    Hi Hayden,

    My apologies. The customer's findings are expected. 

    There is a total of 512KB memory of shared RAM. Current SDK configuration is such that 256KB is allocated to APPSS, 160KB to HWASS and 96KB to FECSS. APPSS can also access the 160KB of shared RAM allocated to HWASS and can be used as data memory. Latest SDK initializes 256KB memory allocated to APPSS and does not initialize Shared RAM allocated to HWASS (160KB).

    I am checking internally to see how the additional 96KB allocated to FECSS can be used by APPSS. I will provide an update this week. 

    Best Regards,

    Josh