On Sat, Apr 3, 2021 at 4:04 PM zack_on_the_speed_chanel
<zack_on_the_speed_cha...@protonmail.ch> wrote:
>
> Thanks so much I was able to get it working! I was able to modify the test 
> code and i was able to create the clock with the  clock monotonic.
>
> I basically changed the the clock create argument to CLOCK_MONOTONIC which 
> should test the branch. During test it failed at
>
>
>   puts( "timer_create - OK" );
>   status = timer_create( CLOCK_MONOTONIC, NULL, &timer );
>   posix_service_failed( status, "timer_create OK" );
> which  gave me the error of   FAILED -- errno (22 - Invalid argument)
>
>
> I only see a case in psxcreatetimer.c for CLOCK_REALTIME which could be that 
> it's just unimplimented.
>
>
>
> My question is there anything I overlooked for this issue? I think the only 
> thing was to change the create argument? Also if this is the extent of the 
> code that that has to be test I'm thinking just to add it into the exiting 
> psxtimer02.c file.

It is preferable that each test provides somewhat self-contained
API/feature testing so that we can easier isolate what is
broken/missing.

In general, the first step toward implementing features in RTEMS is to
create/submit a test case. then follow a test-driven development
approach to implement features until the test works. We don't always
merge broken tests though for unimplemented features.

> Also for coverage testing I was not able to get to test it due to a error: 
> symbol parser write failed for score error.
>
Alex may be able to help you with running coverage. It has been
undergoing heavy revision lately.

> thanks
> zack
>
>
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> On Friday, April 2, 2021 9:08 PM, Gedare Bloom <ged...@rtems.org> wrote:
>
> > On Fri, Apr 2, 2021 at 12:19 PM zack_on_the_speed_chanel
> > zack_on_the_speed_cha...@protonmail.ch wrote:
> >
> > > Yes the build works successfully. I tried to also just try BUILD_PSXTESTS 
> > > only and it failed midway. I also tried to do an automated build. It 
> > > failed with __start symbol not found.
> >
> > You also need to enable the POSIX API/signals, in your config.ini add
> > RTEMS_POSIX_API = True
> >
> > > Sent with ProtonMail Secure Email.
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Thursday, April 1, 2021 10:10 PM, Gedare Bloom ged...@rtems.org wrote:
> > >
> > > > On Thu, Apr 1, 2021 at 2:52 PM zack_on_the_speed_chanel
> > > > zack_on_the_speed_cha...@protonmail.ch wrote:
> > > >
> > > > > Did i do anything wrong with my .ini file?
> > > > > Sent with ProtonMail Secure Email.
> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > On Wednesday, March 31, 2021 12:20 AM, zack_on_the_speed_chanel 
> > > > > zack_on_the_speed_cha...@protonmail.ch wrote:
> > > > >
> > > > > > my waf file look like this
> > > > > > $cat config.ini
> > > > > > [sparc/leon3]
> > > > > > BUILD_TESTS=True
> > > > > > for rebuilding the bsp I ran:
> > > > > > ./waf configure
> > > > > > ./waf
> > > >
> > > > This looks right, nothing obvious to me.
> > > > Does the waf build finish successfully, or does it stop with an error?
> > > >
> > > > > > Zack
> > > > > > Sent with ProtonMail Secure Email.
> > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > On Tuesday, March 30, 2021 9:02 PM, Gedare Bloom ged...@rtems.org 
> > > > > > wrote:
> > > > > >
> > > > > > > On Tue, Mar 30, 2021 at 2:41 PM zack_on_the_speed_chanel
> > > > > > > zack_on_the_speed_cha...@protonmail.ch wrote:
> > > > > > >
> > > > > > > > I have both of the options and i tried to built it with 
> > > > > > > > BUILD_TESTS and PSXTESTS and the test didn't build. Is there 
> > > > > > > > anything else that could alter how rtems is built?
> > > > > > >
> > > > > > > After you set them to True, did you re-run waf configure before 
> > > > > > > waf build?
> > > > > > >
> > > > > > > > Sent with ProtonMail Secure Email.
> > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > On Tuesday, March 30, 2021 3:29 PM, Gedare Bloom 
> > > > > > > > ged...@rtems.org wrote:
> > > > > > > >
> > > > > > > > > BUILD_TESTS and BUILD_PSXTESTS are two options that
> > > > > > > > > if either is True it should build psxclock02.
> > > > > > > > > On Tue, Mar 30, 2021 at 9:20 AM zack_on_the_speed_chanel
> > > > > > > > > zack_on_the_speed_cha...@protonmail.ch wrote:
> > > > > > > > >
> > > > > > > > > > I did build the leon3 bsp and I still don't see the 
> > > > > > > > > > psxtimer02 as an executable. Is there a way build a test 
> > > > > > > > > > from source? I have the sources for psxtest02. Also i'm 
> > > > > > > > > > thinking that it could be due to the fact that i don't have 
> > > > > > > > > > posix tests enabled. Is there a way
> > > > > > > > > > that to enable posix?
> > > > > > > > > > Thanks
> > > > > > > > > > Zack
> > > > > > > > > > Sent with ProtonMail Secure Email.
> > > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > > > On Monday, March 29, 2021 8:11 PM, zack_on_the_speed_chanel 
> > > > > > > > > > zack_on_the_speed_cha...@protonmail.ch wrote:
> > > > > > > > > >
> > > > > > > > > > > Sorry that assumption was very native of me that i didn't 
> > > > > > > > > > > have a working baseline. Joel said that the erc32 was 
> > > > > > > > > > > similar to the leon bsp
> > > > > > > > > > > "
> > > > > > > > > > > The ERC32 what's the first space hardened sparc 
> > > > > > > > > > > processor. The leon3 is a
> > > > > > > > > > > later processor in the same family. Both use the same 
> > > > > > > > > > > build of GCC and are
> > > > > > > > > > > just different bsps. In fact both run on the same sis 
> > > > > > > > > > > simulator. "
> > > > > > > > > > > I also though that the bsps were the same and I can work 
> > > > > > > > > > > on the issue with only the erc32 BSP. I have one more 
> > > > > > > > > > > question: when i run the hello world test. All the test 
> > > > > > > > > > > files are within one specific directory and I don't see 
> > > > > > > > > > > the executables for specific bsps that's why i thought 
> > > > > > > > > > > all tests would be built (there would not be any specific 
> > > > > > > > > > > considerations for bsps) .
> > > > > > > > > > > Sent with ProtonMail Secure Email.
> > > > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > > > > > > > > > On Monday, March 29, 2021 2:45 PM, Gedare Bloom 
> > > > > > > > > > > ged...@rtems.org wrote:
> > > > > > > > > > >
> > > > > > > > > > > > On Sun, Mar 28, 2021 at 1:26 PM zack_on_the_speed_chanel
> > > > > > > > > > > > zack_on_the_speed_cha...@protonmail.ch wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hello all,
> > > > > > > > > > > > > I'm updating on what' i've found out with the issue 
> > > > > > > > > > > > > (forgot to reply all) . Joel recommended me check the 
> > > > > > > > > > > > > coverage for the leon BSP( to check if it's 
> > > > > > > > > > > > > supported) and i found that the branch with 
> > > > > > > > > > > > > CLOCK_MONOTONIC was not reached I think now that it's 
> > > > > > > > > > > > > supported (because the annotated assembly is in the 
> > > > > > > > > > > > > sparc instruction set). I also found out that the 
> > > > > > > > > > > > > test would be similar to Psxclock02 and it runs the 
> > > > > > > > > > > > > same tests on a different clock. Then I tried to 
> > > > > > > > > > > > > build the psxclock02 test , change the create_clock 
> > > > > > > > > > > > > to have the clock_monotonic argument and i didn't see 
> > > > > > > > > > > > > the executable or any change in the ./waf build. Then 
> > > > > > > > > > > > > I was suggested that you have to enable all tests 
> > > > > > > > > > > > > some how? How do i enable all tests?
> > > > > > > > > > > >
> > > > > > > > > > > > Do you use something like: ./waf bsp_defaults 
> > > > > > > > > > > > ---rtems-bsp=leon3 > config.ini
> > > > > > > > > > > > Then, take a look, BUILD_TESTS and BUILD_PSXTESTS are 
> > > > > > > > > > > > two options that
> > > > > > > > > > > > if either is True it should build psxclock02.
> > > > > > > > > > > > When you write code, you should first make sure you can 
> > > > > > > > > > > > build the code
> > > > > > > > > > > > as it exists if it is supposed to work, and run it to 
> > > > > > > > > > > > see that it
> > > > > > > > > > > > works. Then you should make changes from a working 
> > > > > > > > > > > > baseline. Otherwise
> > > > > > > > > > > > when you get a problem, how do you know if the problem 
> > > > > > > > > > > > is your
> > > > > > > > > > > > problem, or it already existed?
> > > > > > > > > > > >
> > > > > > > > > > > > > Thanks
> > > > > > > > > > > > > Zack
> > > > > > > > > > > > > devel mailing list
> > > > > > > > > > > > > devel@rtems.org
> > > > > > > > > > > > > http://lists.rtems.org/mailman/listinfo/devel
>
>
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to