Re: [U-Boot] U-Boot malloc implementation on arm - problem after relocation

2015-10-07 20:25 GMT+02:00 mar.krzeminski : > > > W dniu 07.10.2015 o 19:38, Andreas Färber pisze: > >> Hi Marcin, >> >> Am 07.10.2015 um 15:58 schrieb Marcin Krzemiński: >> >>> Since I use qemu it >>> is very hard to debug with gdb u-boot after relocation( or I do not

Re: [U-Boot] U-Boot malloc implementation on arm - problem after relocation

W dniu 07.10.2015 o 19:38, Andreas Färber pisze: Hi Marcin, Am 07.10.2015 um 15:58 schrieb Marcin Krzemiński: Since I use qemu it is very hard to debug with gdb u-boot after relocation( or I do not know how to do it), so I am almost blind. QEMU has a built-in gdb stub that you can just

[U-Boot] U-Boot malloc implementation on arm - problem after relocation

Hello, In my board I have some problems with malloc functionality. In config I have settings for malloc: #define CONFIG_SYS_MALLOC_LEN (2 * 1024 * 1024) #define CONFIG_SYS_MALLOC_F_LEN (1024) I am running u-boot without SPL. Uboot starts from SRAM and then relocates to DRAM. When I run u-boot

Re: [U-Boot] U-Boot malloc implementation on arm - problem after relocation

Hi Marcin, Am 07.10.2015 um 15:58 schrieb Marcin Krzemiński: > Since I use qemu it > is very hard to debug with gdb u-boot after relocation( or I do not know > how to do it), so I am almost blind. QEMU has a built-in gdb stub that you can just connect to as gdb remote target, similar to how you