Has anybody ported RTEMS to the Qualcomm Snapdragon?
Sent from my iPhone
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
Does JFFS2 provide bad block management and wear leveling? If so, is there
anything we need to do to enable it?
Sent from my iPhone
___
users mailing list
users@rtems.org
http://lists.rtems.org/mailman/listinfo/users
That’s kind of my point. The low priority shell task is working perfectly.
The higher priority task is pended by time. I do have some sleep functions in
the driver code but they are short sleeps. They shouldn’t just pens
indefinitely until a run any random command in the shell. Unless I’m
Trying the other list. Is RTEMS actually running on a Zynq Ultrascale? The
instructions I found for the Ultra96 make me think 1) either it doesn’t
actually work, or 2) there are undocumented assumptions including running the
A53’s in 32bit mode.
What I’m most interested in is running RTEMS
Can I call you later this morning? What is your number?
Sent from my iPhone
> On Oct 23, 2019, at 09:18, Joel Sherrill wrote:
>
>
>
>> On Wed, Oct 23, 2019 at 8:26 AM Mathew Benson
>> wrote:
>> Is there a version of RTEMS that is FACE compliant? Possibly certified? If
>> so, how do we
I take it that’s a no on the documentation. Can somebody just tell me what
these mean or point me where in the code it is? It’s not an easy follow.
Sent from my iPhone
> On Oct 31, 2019, at 13:43, Mathew Benson wrote:
>
> is there any documentation that explains the actual output of the
I’m fairly certain I’m running into this reported issue:
https://devel.rtems.org/ticket/2792
Is there any status change on this? Is there a temporary workaround recovery
procedure? I’m tempted to give the conditional wait a timeout.
Sent from my iPhone
> On Oct 9, 2019, at 23:05, Mathew
I basically just copied and renamed the existing function that prints to the
console, but changed it to return a struct. I couldn’t personally give it
back. I thought my customer at the time would roll it back in. Looks like
that never happened. Sorry.
> On Jan 13, 2023, at 17:05, Joel
