On 19/9/18 11:08 am, Chris Johns wrote:
> The only recent issue I have seen is with APFS on high end MacBooks with large
> solid state disks. I thought we had a patch to work around the issue but I
> cannot find it in the RSB and I was building tools on that machine on the
> weekend without a
Hi,
Are you able to catch the interrupt, confirm the event is being raised and
the
interrupt exits via the RTEMS exit path?
-> Yes. I can see with task command in shell my USB event is set for my
task; the state is READY, but
if I enter cpuuse a few times I see the total CPU time for my task
On 26/09/2018 16:43, Catalin Demergian wrote:
> When you say "changing the makefiles" who's makefiles are these?
> -> for example lib/rtems-4.11.2/c/src/lib/libbsp/arm/stm32f7/Makefile.am
> in order to include my USB .c and .h files
Thanks.
> Did you merge your code into the RTEMS
> source
On 26/09/2018 09:21, Catalin Demergian wrote:
Hi,
Did you add your code to the RTEMS source tree?
-> yes, I had to add the USB files, because there was no USB support
in my code base
If you integrate code into the RTEMS source tree, then you should use
the master branch and try to upstream
Hi,
Did you add your code to the RTEMS source tree?
-> yes, I had to add the USB files, because there was no USB support in my
code base
There are new fatal errors in the master branch
INTERNAL_ERROR_THREAD_QUEUE_ENQUEUE_STICKY_FROM_BAD_STATE,
INTERNAL_ERROR_BAD_THREAD_DISPATCH_DISABLE_LEVEL,
HI,
When you say "changing the makefiles" who's makefiles are these?
-> for example lib/rtems-4.11.2/c/src/lib/libbsp/arm/stm32f7/Makefile.am
in order to include my USB .c and .h files
Did you merge your code into the RTEMS
source tree?
-> yes, there was no support for USB in the code base I had
