Actions
Forum Thread Details
  • State Not Answered
  • Replies 6 replies
  • Subscribers 330 subscribers
  • Views 651 views
  • Users 0 members are here
Related

Zedboard hangs when running HL code

jesusmgonzalez

Hi!

I'm trying to run some High Level code generated from Matlab/Simulink. I set all kind of software optimizations regarding embedded destination platform, such as RAM optimization and complex reduction, as well.

But he problem arises when I try to run the first step. The Zedboard freezes and the XSDK returns a debug error. I don't know if the problem is related with memory consumption. The total reserved space in one iteration is at least 20KB of data.

Does anybody know how to solve this problem? Could I add any hardware accelerator in PlanAhead?

Thanks,

Parents
  • 0

    Hi jesusmgonzalez,

    Yes, you are correct in that the amount of memory available to the PS is relatively large.  What I am suggesting is that you double check to see if the space allocated to your call stack and heap area is sufficient for the application you are running.

    For example, I just created a new project using the Empty Application template on the build in zed_hw_platform in SDK.  Here are the default stack and heap allocations that SDK creates for you: 

    image

    You can see that they are rather small at 2K each, so if you are running a complex application with nested function calls that go rather deep, my suggestion is to check and make sure that you are not overflowing the stack space.  Also, if you are operating on dynamically allocated memory (any space created with malloc() or call to a class constructor) make sure you are not running our of heap space.

    SDK gives you the ability to modify the size of these areas within your lscript.ld file or create a new one using the Xilinx Tools-->Generate linker script window.

    Regards,

    -Kevin

Reply
  • 0

    Hi jesusmgonzalez,

    Yes, you are correct in that the amount of memory available to the PS is relatively large.  What I am suggesting is that you double check to see if the space allocated to your call stack and heap area is sufficient for the application you are running.

    For example, I just created a new project using the Empty Application template on the build in zed_hw_platform in SDK.  Here are the default stack and heap allocations that SDK creates for you: 

    image

    You can see that they are rather small at 2K each, so if you are running a complex application with nested function calls that go rather deep, my suggestion is to check and make sure that you are not overflowing the stack space.  Also, if you are operating on dynamically allocated memory (any space created with malloc() or call to a class constructor) make sure you are not running our of heap space.

    SDK gives you the ability to modify the size of these areas within your lscript.ld file or create a new one using the Xilinx Tools-->Generate linker script window.

    Regards,

    -Kevin

Children
No Data