Re: RISC-V/HiFive memory limitations

2017-06-25 Thread Joel Sherrill
That doesn't appear to do much more than clear the bss. So no hints on more to do there. The atexit() call and init/fini are handled by RTEMS in portable code. On Jun 25, 2017 6:24 AM, "Denis Obrezkov" wrote: > 2017-06-25 2:50 GMT+02:00 Denis Obrezkov

Re: RISC-V/HiFive memory limitations

2017-06-25 Thread Denis Obrezkov
2017-06-25 2:50 GMT+02:00 Denis Obrezkov : > 2017-06-25 2:15 GMT+02:00 Joel Sherrill : > >> They are supposed to use the installed linkcmds. >> >> On Jun 24, 2017 6:04 PM, "Denis Obrezkov" >> wrote: >> >>> 2017-06-23 21:03

Re: RISC-V/HiFive memory limitations

2017-06-24 Thread Denis Obrezkov
2017-06-25 2:15 GMT+02:00 Joel Sherrill : > They are supposed to use the installed linkcmds. > > On Jun 24, 2017 6:04 PM, "Denis Obrezkov" wrote: > >> 2017-06-23 21:03 GMT+02:00 Denis Obrezkov : >> >>> 2017-06-23 20:16 GMT+02:00

Re: RISC-V/HiFive memory limitations

2017-06-24 Thread Joel Sherrill
They are supposed to use the installed linkcmds. On Jun 24, 2017 6:04 PM, "Denis Obrezkov" wrote: > 2017-06-23 21:03 GMT+02:00 Denis Obrezkov : > >> 2017-06-23 20:16 GMT+02:00 Denis Obrezkov : >> >>> 2017-06-23 16:39

Re: RISC-V/HiFive memory limitations

2017-06-24 Thread Denis Obrezkov
2017-06-23 21:03 GMT+02:00 Denis Obrezkov : > 2017-06-23 20:16 GMT+02:00 Denis Obrezkov : > >> 2017-06-23 16:39 GMT+02:00 Joel Sherrill : >> >>> >>> >>> On Jun 23, 2017 9:29 AM, "Gedare Bloom" wrote: >>> >>> On

Re: RISC-V/HiFive memory limitations

2017-06-23 Thread Denis Obrezkov
2017-06-23 20:16 GMT+02:00 Denis Obrezkov : > 2017-06-23 16:39 GMT+02:00 Joel Sherrill : > >> >> >> On Jun 23, 2017 9:29 AM, "Gedare Bloom" wrote: >> >> On Thu, Jun 22, 2017 at 8:32 PM, Denis Obrezkov >> wrote:

Re: RISC-V/HiFive memory limitations

2017-06-23 Thread Joel Sherrill
On Jun 23, 2017 9:29 AM, "Gedare Bloom" wrote: On Thu, Jun 22, 2017 at 8:32 PM, Denis Obrezkov wrote: >> Ok, then I will try to adapt the default linkcmd file today. >> >> -- >> Regards, Denis Obrezkov > > > Hello all, > It seems that data section

Re: RISC-V/HiFive memory limitations

2017-06-23 Thread Gedare Bloom
On Thu, Jun 22, 2017 at 8:32 PM, Denis Obrezkov wrote: >> Ok, then I will try to adapt the default linkcmd file today. >> >> -- >> Regards, Denis Obrezkov > > > Hello all, > It seems that data section wasn't copied from ROM, so I've added the > initialization code > and

Re: RISC-V/HiFive memory limitations

2017-06-22 Thread Denis Obrezkov
> > Ok, then I will try to adapt the default linkcmd file today. > > -- > Regards, Denis Obrezkov > Hello all, It seems that data section wasn't copied from ROM, so I've added the initialization code and now I have a proper value. Thus, I can proceed further to new errors. I haven't started to

Re: RISC-V/HiFive memory limitations

2017-06-20 Thread Denis Obrezkov
2017-06-20 16:29 GMT+03:00 Joel Sherrill : > > > On Jun 20, 2017 1:20 AM, "Denis Obrezkov" wrote: > > 2017-06-20 4:00 GMT+03:00 Joel Sherrill : > >> >> >> On Jun 19, 2017 5:37 PM, "Denis Obrezkov" >> wrote: >> >>

Re: RISC-V/HiFive memory limitations

2017-06-20 Thread Joel Sherrill
On Jun 20, 2017 1:20 AM, "Denis Obrezkov" wrote: 2017-06-20 4:00 GMT+03:00 Joel Sherrill : > > > On Jun 19, 2017 5:37 PM, "Denis Obrezkov" wrote: > > 2017-06-20 1:23 GMT+03:00 Hesham Almatary : > >> >>

Re: RISC-V/HiFive memory limitations

2017-06-20 Thread Denis Obrezkov
2017-06-20 4:00 GMT+03:00 Joel Sherrill : > > > On Jun 19, 2017 5:37 PM, "Denis Obrezkov" wrote: > > 2017-06-20 1:23 GMT+03:00 Hesham Almatary : > >> >> >> On Tue, Jun 20, 2017 at 7:33 AM, Denis Obrezkov

Re: RISC-V/HiFive memory limitations

2017-06-19 Thread Joel Sherrill
On Jun 19, 2017 5:37 PM, "Denis Obrezkov" wrote: 2017-06-20 1:23 GMT+03:00 Hesham Almatary : > > > On Tue, Jun 20, 2017 at 7:33 AM, Denis Obrezkov > wrote: > >> 2017-06-20 0:19 GMT+03:00 Joel Sherrill :

Re: RISC-V/HiFive memory limitations

2017-06-19 Thread Denis Obrezkov
2017-06-20 1:23 GMT+03:00 Hesham Almatary : > > > On Tue, Jun 20, 2017 at 7:33 AM, Denis Obrezkov > wrote: > >> 2017-06-20 0:19 GMT+03:00 Joel Sherrill : >> >>> Check the value in gdb without loading it on a target. >>> >>> Gdb

Re: RISC-V/HiFive memory limitations

2017-06-19 Thread Hesham Almatary
On Tue, Jun 20, 2017 at 7:33 AM, Denis Obrezkov wrote: > 2017-06-20 0:19 GMT+03:00 Joel Sherrill : > >> Check the value in gdb without loading it on a target. >> >> Gdb hello.exe >> >> p symbol >> > >> Since it is a constant, it should be as expected. If

Re: RISC-V/HiFive memory limitations

2017-06-19 Thread Denis Obrezkov
2017-06-20 0:19 GMT+03:00 Joel Sherrill : > Check the value in gdb without loading it on a target. > > Gdb hello.exe > > p symbol > > Since it is a constant, it should be as expected. If it is, you have a > code loading issue. > Yes, it is 512 in gdb, as expected. So, is the

Re: RISC-V/HiFive memory limitations

2017-06-19 Thread Joel Sherrill
Check the value in gdb without loading it on a target. Gdb hello.exe p symbol Since it is a constant, it should be as expected. If it is, you have a code loading issue. Is that value by any chance an instruction? On Jun 19, 2017 4:03 PM, "Denis Obrezkov" wrote: >

Re: RISC-V/HiFive memory limitations

2017-06-19 Thread Hesham Almatary
Hi Denis, If you cscope this symbol you'll end up with the following: /** > * By default, use the minimum stack size requested by this port. > */ > #ifndef CONFIGURE_MINIMUM_TASK_STACK_SIZE > #define CONFIGURE_MINIMUM_TASK_STACK_SIZE CPU_STACK_MINIMUM_SIZE > #endif > This means if you, from