Re: Couverture-Qemu Testing Results

> Does pc386 look similar? I haven't been able to get a decent set of results for PC386. For RSB-Qemu all the tests time out. Using command qemu-system-i386 -m 128 -boot b -hda path_to/rtems-boot.img -no-reboot -monitor null -serial stdio -nographic -append "--console=com1;boot;" --

Re: RISC-V interrupts

I found out that there is 16 KiB of RAM. So, Freedom E310 chip has only 16 KiB of RAM. And Freedeom E310 chip is based on E31 Coreplex core that allows maximum of 64 KiB of RAM. So, I was just a bit confused with these names at first. 2017-06-09 11:49 GMT+03:00 Hesham Almatary : > On Fri, Jun 9,

Interrupt handling for RISCV

Hello Hesham, I found out that your code in interrupt handling routine is outdated - the format of mstatus and sstatus registers was changed. I can produce some patches in a few days, though, I still don't understand how to deal with local and global interrupts. -- Regards, Denis Obrezkov __

Re: Couverture-Qemu Testing Results

On Jun 11, 2017 4:13 AM, "Cillian O'Donnell" wrote: > Does pc386 look similar? I haven't been able to get a decent set of results for PC386. For RSB-Qemu all the tests time out. Using command qemu-system-i386 -m 128 -boot b -hda path_to/rtems-boot.img -no-reboot -monitor null -serial stdio -no

Re: Couverture-Qemu Testing Results

>You might should hand check hello on all the bsps. I recall that some do not >have a way for the bsp to "reset" the board and exit back to Linux. The tests >run but since qemu doesn't exit at RTEMS shutdown, you have to timeout. Actually I've already done this and that is the exact problem I'm

Re: Couverture-Qemu Testing Results

On Jun 11, 2017 1:14 PM, "Cillian O'Donnell" wrote: >You might should hand check hello on all the bsps. I recall that some do not have a way for the bsp to "reset" the board and exit back to Linux. The tests run but since qemu doesn't exit at RTEMS shutdown, you have to timeout. Actually I've al

Re: RISC-V interrupts

Hi Denis, As per my previous reply, it is gonna be a challenge to make RTEMS exes fit in 16 KiB of RAM, so it's a good idea to do some analysis on the compressed ISA. Cheers, Hesham On Sun, Jun 11, 2017 at 9:36 PM, Denis Obrezkov wrote: > I found out that there is 16 KiB of RAM. So, Freedom E31

Re: Interrupt handling for RISCV

Hi Denis, On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov wrote: > Hello Hesham, > > I found out that your code in interrupt handling routine is outdated - Which interrupt handling routine? The port doesn't handle interrupts. The only relevant code is enable/disable interrupts, but it doesn't

Re: Interrupt handling for RISCV

2017-06-11 22:43 GMT+03:00 Hesham Almatary : > Hi Denis, > > > > On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov > wrote: > > Hello Hesham, > > > > I found out that your code in interrupt handling routine is outdated - > Which interrupt handling routine? The port doesn't handle interrupts. > The

Re: RISC-V interrupts

2017-06-11 22:38 GMT+03:00 Hesham Almatary : > Hi Denis, > > As per my previous reply, it is gonna be a challenge to make RTEMS > exes fit in 16 KiB of RAM, so it's a good idea to do some analysis on > the compressed ISA. > > Cheers, > Hesham > > Ok, I will investigate this. Also, there is 8 KiB o

Re: Interrupt handling for RISCV

On Mon, Jun 12, 2017 at 6:01 AM, Denis Obrezkov wrote: > 2017-06-11 22:43 GMT+03:00 Hesham Almatary : >> >> Hi Denis, >> >> >> >> On Sun, Jun 11, 2017 at 11:52 PM, Denis Obrezkov >> wrote: >> > Hello Hesham, >> > >> > I found out that your code in interrupt handling routine is outdated - >> Which

Re: RISC-V interrupts

On Mon, Jun 12, 2017 at 6:11 AM, Denis Obrezkov wrote: > 2017-06-11 22:38 GMT+03:00 Hesham Almatary : >> >> Hi Denis, >> >> As per my previous reply, it is gonna be a challenge to make RTEMS >> exes fit in 16 KiB of RAM, so it's a good idea to do some analysis on >> the compressed ISA. >> >> Cheer

new warning in libmisc/capture

Hi Not sure the best way to fix this warning that occurs in 161 BSPs. :( 161 ../../../../../../rtems/c/src/../../cpukit/libmisc/capture/rtems-trace-buffer-vars.c:22:12: warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier] The code is const char const* __rtld_trace_n

Re: new warning in libmisc/capture

On 12/6/17 10:09 am, Joel Sherrill wrote: > Not sure the best way to fix this warning that occurs in 161 BSPs. :( > > 161 > ../../../../../../rtems/c/src/../../cpukit/libmisc/capture/rtems-trace-buffer-vars.c:22:12: > warning: duplicate 'const' declaration specifier [-Wduplicate-decl-specifier

[PATCH] Review and help

These are the changes I made to read the ini files also, this does succeed in reading them. But there are a lot of problems to solve. --- rtemstoolkit/configuration.py | 11 --- rtemstoolkit/git.py | 1 + rtemstoolkit/macros.py| 16 +++- rtemstoolkit/options.

[PATCH 2/2] Review and help

Few of the new ini files --- tester/rtems/testing/bsps/erc32-run.ini | 54 ++ tester/rtems/testing/bsps/erc32.ini | 56 ++ tester/rtems/testing/defaults.ini | 126 tester/rtems/testing/testing.ini| 57 +++ 4

Re: [PATCH 2/2] Review and help

Hello Chris, What do you think of the changes above? Did you imagine it this way? Right now: python rtems-test --log=erc32_winpdb_5 --rtems-bsp=erc32-run --rtems-tools=$HOME/development/rtems/4.12 /home/thd/development/rtems/src/builds/erc32_new_state/sparc-rtems4.12/c/erc32/testsuites/samples/hel

Re: [PATCH 2/2] Review and help

On 12/6/17 12:55 pm, Tanu Hari Dixit wrote: > What do you think of the changes above? Did you imagine it this way? As discussed on IRC please fork the repo on github and push the changes to a branch I can review on and comment. This way I can track you repo without need to handle these patches.