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.

AM335x GPMC wrapping burst

What is the difference between the non-wrapping burst(WRAPBURST bit = 0) and the wrapping burst(WRAPBURST bit = 1)?

Is it only different about the address boundary?

About the non-wrapping address boundary, is it variable?
Is it 2-word boundary at the least?

About the wrapping address boundary, is it fixed?
If the ATTACHEDDEVICEPAGELENGTH field value is 16-word, is it fixed in 16-word?

Best regards,

Daisuke

 

  • Maeda-san,

    This is my opinion.

    > What is the difference between the non-wrapping burst(WRAPBURST bit = 0) and the wrapping burst(WRAPBURST bit = 1)?
    To use wrapping burst, memory device need to be supporting wrapping capability.
    On wrapping burst mode, burst length is fixed and start address is aligned by memory side page length boundary.
    Of Course, ATTACHEDDEVICEPAGELENGTH must be set to burst length supported by memory device in configured in fixed-length burst mode.
    It gets optimal memory performance, and data can be read or witten to the memory at constant rate without wait state.

    > Is it only different about the address boundary?
    Also it is fixed burst length.

    > About the non-wrapping address boundary, is it variable?
    Yes, it is variable.

    > Is it 2-word boundary at the least?
    I am sorry, I can not understand above meaning.

    > About the wrapping address boundary, is it fixed?
    > If the ATTACHEDDEVICEPAGELENGTH field value is 16-word, is it fixed in 16-word?
    Yes and Yes.

    Hello TIer.
    Could you give us additional advice?

    Best regards, RY