Smells like the problem is at the nodejs side, maybe you can try not
running the node program and cat'ing the device to see if the characters
are shown. What's the value of the 'data' received in the callback?
Saludos,
Nahuel Greco.
On Fri, Oct 27, 2017 at 11:05 AM, Hugh Frater <hugh.fra...@gmail.com> wrote:
> Hi Nahuel,
>
> You can't cat the device file because linux doesn't allow concurrent
> access to the device file descriptor from more than one userspace program,
> and we need to open that device file from within our node.js program to
> write to the PRU. I do have a hardware UART looped back from the PRU into
> userspace, so I could use that for the communication back into userpace,
> but I would rather persevere and get the rpmsg subsystem working in a
> bi-directional mode.
>
>
> On Thursday, 26 October 2017 21:57:02 UTC+1, Nahuel Greco wrote:
>>
>> doing "cat /dev/rpmsg_pruXX" shows any data? do you have a github repo
>> with a complete sample?
>>
>> Saludos,
>> Nahuel Greco.
>>
>> On Mon, Oct 9, 2017 at 1:11 PM, Hugh Frater <hugh....@gmail.com> wrote:
>>
>>> Does anyone have any experience of working with /dev/rpmsg_pruXX files
>>> from within Node.Js/Bonescript? I've been playing around with the
>>> file-duplex package and have data going into the PRU just fine, but I'm
>>> having an issue getting data back into my userspace program. I've got the
>>> stream.on('data', function(data)) picking up that a data has been pushed
>>> into the rpmsg file from the PRU side, but I can't get any meaningful data
>>> into my program. I'm sending single character ascii characters as my data.
>>>
>>> Am I missing the 'proper' way to do this?
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/beagleboard/666d2c51-fa4f-464b-83db-ffc7a158fecf%40googlegroups.com
>>> <https://groups.google.com/d/msgid/beagleboard/666d2c51-fa4f-464b-83db-ffc7a158fecf%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/07c3768b-461a-456f-aecd-f31600184ec7%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/07c3768b-461a-456f-aecd-f31600184ec7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CAHRTM8BAn0Q4caTj1nH%2Bbk9H6EG-Ez6%2BEabpc8ChA%3DHf4aybzQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
