<<<My first intention is to post in TI E2E support forums, but it requires a
company email to do so.
Hello Cheng
I want to Help you but it appears my message is lost in translation
What it sounds like to me is TI pays these engineers $$ to answer questions
and does not want to waste time and $$$ with users that dont follow their well
written instructions which say use SDK Yocto Linux on the ARM for this example.
For me I start with a working example with instructions and documentation then
modifyit
If I undertsand correctly you have never had an example working
If you like breaking examples and working on projects that ONLY works from a
unix script and hides all the details then this is the correct group to to ask
questions (-:
I suggest you try the example you found following the intructions exactly. if
you cant or wont do that switch to DEbian/Cookbook
But if you do the latter I suggest don't change things follow the instructions
What is interesting is a Linux C application program should work correctly if
it was coded generic especially when both Linux variants are for the same chip.
Trying to figure out what is different between Linux variants to me is not
productive its not my focus for you maybe it is.
Perhaps the Linux in the SDK was configured differently which implies it handle
PRU slightly different Im not surprised by this.
Perhaps you can find what's different that may be a valid approach that works
for you and maybe someone can help. I think Dennis gave you a good clue.
I will watch the thread hopefully I can be of help should you choose to follow
the path E2E and the SDK layed out for you
Cheers
On Friday, April 30, 2021, 07:52:09 PM CDT, Cheng Chen
<chenc2...@gmail.com> wrote:
Hey Mark,
Thanks for spending time for replying. I really appreciate it. I totally agree
with you that one should spend time investigating first. I apologize if they
are dumb questions, but I have stuck there for two weeks. I am more a circuit
guy and just started picking up Beaglebone as a hobby and potential career
expansion.
My first intention is to post in TI E2E support forums, but it requires a
company email to do so. If this particular .org is not a good place for rookie
questions, would you please advise some place for suitable for discussion?
Regarding to the documents, are you referring to processor SDK Linux Software
Developer's guide? If that is the one, I did follow its instructions, but maybe
I missed something. I will go over it again. If that's not the one, which
document are you referring to? I also went through PRUcookbook and Exploring
BeagleBone by Derek Molly. Not a lot are mentioned regarding this topic.
The code is built-in in the Beaglebone Black, this is one of the reasons I am
confused why it cannot be compiled. One can also download freely from TI github
(https://git.ti.com/cgit/pru-software-support-package/pru-software-support-package/).
Again thanks for the advice and suggestion. I am very glad that there is such a
nice place that I can call for help and I hope after some practice I am also
able to contribute here.
Regards,Cheng
在2021年4月30日星期五 UTC-4 下午5:09:01<lazarman> 写道：
Hello
I know the code. It's all explained in the SDK documention. I also like these
examples.Your asking questions about an SDK that's supported by Texas
Instruments. You do understand this .org group you posted in may contain TI
employees but is NOT TI support it's Beagle board Debian.
I think if you read the documents you will understand the answers
I'm sure you could compile this with some work the sdk instructions talk about
This.
Hypothetical question ❓If the instructions told you a virtual box build was not
supported and not recommended would you use one anyway and then ask the person
who told you not too do this why it doesn't work.
I'm struggling to be nice in this reply.
I remember asking questions as a young engineer that clearly showed I made
zero effort to research anything.
Then one day I got some really critical replies about my skills.
Do some reading then if stuck ask questions
Or better yet follow what the sdk instructions suggest.
If you found this code on internet and don't have a TI account or are not
eligible for ITAR restrictions to download the sdk you have a big problem.
I see you have a Gmail account
Sent from Yahoo Mail on Android
On Fri, Apr 30, 2021 at 3:09 PM, Cheng Chen<chen...@gmail.com> wrote:
Hi all,
I am practicing PRU skills through some TI examples. I am playing with
PRU_ADC_onChip example and ran into a few questions. I wonder if you can help
me with.
The nice thing about this example is it has a README.txt with all the
procedures. The idea is to use rpmsg to communicate between arm and pru module
and read out ADC value. I am using a Beaglebone Black wireless.Here is the
basic procedures.
FILE STRUCTUREPRU_ADC | |--pru_adc_firmware.c firmware loaded into PRU0 |
|--pru_adc_userspace |--pru_adc_userspace.c userspace code that interacts
with PRU0
BUILD FIRMWARE & USERSPACE CODE$ cd
<PATH_TO_PRU_SW_SUPPORT_PACKAGE>/examples/am335x/PRU_ADC_onChip/$ make clean$
make$ cd pru_adc_userspace/$ make clean$ make
My BBB wireless can compile pru code successfully because I installed PRU_CGT
compiler. But it is unable to compile ARM code. I think that is because ARM_CCT
cross-compiler toochain environment is missing, in another word, I need to
install processor-sdk-am335x
My first questions is can I install processor-sdk-am335x into Debian system I
currently have (Linux beaglebone 4.19.94-ti-r62 ) ? I am a little confused
about the relationship between this SDK and Debian system. Why is the tutorial
asking me to compile pru_adc_userspace.c in the Beaglebone. I thought it is
supposed to be executed in a cross-compilation environment.
I ended up installing processor-sdk-am335x on my linux desktop and compiled
successfully. Then I copied the generated file back to BBB wireless. But when I
tried to run the program, it shows the following error.
Reading voltage at ADC Channel: 5/dev/rpmsg_pru30 could not be opened.Trying to
initialize PRU using sysfs interface.ERROR: Could not open /dev/rpmsg_pru30
Attached is the excerpt where the problem happened. Could anyone help me with
some hints of what is going on here? Much appreciated.
struct shared_struct message;
/* use character device /dev/rpmsg_pru30 */ char outputFilename[] =
"/dev/rpmsg_pru30";
/* test that /dev/rpmsg_pru30 exists */ FILE *ofp; uint16_t returnedVoltage;
ofp = fopen(outputFilename, "r");
if (ofp == NULL) {
printf("/dev/rpmsg_pru30 could not be opened. \n"); printf("Trying to
initialize PRU using sysfs interface.\n");
FILE *sysfs_node; char firmware[] =
"/sys/class/remoteproc/remoteproc1/firmware"; char firmwareName[] =
"PRU_ADC_onChip.out"; sysfs_node = fopen(firmware, "r+"); if (sysfs_node ==
NULL) { printf("cannot open firmware sysfs_node"); return EXIT_FAILURE; }
fwrite(&firmwareName, sizeof(uint8_t), sizeof(firmwareName), sysfs_node);
fclose(sysfs_node);
char pruState[] = "/sys/class/remoteproc/remoteproc1/state"; char start[] =
"start"; sysfs_node = fopen(pruState, "r+"); if (sysfs_node == NULL) {
printf("cannot open state sysfs_node"); return EXIT_FAILURE; } fwrite(&start,
sizeof(uint8_t), sizeof(start), sysfs_node); fclose(sysfs_node);
/* give RPMSG time to initialize */ sleep(3);
ofp = fopen(outputFilename, "r");
if (ofp == NULL) { printf("ERROR: Could not open /dev/rpmsg_pru30\n");
exit(EXIT_FAILURE); } }
--
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/msgid/beagleboard/1d43aa7b-0e94-4431-9e31-13545213940bn%40googlegroups.com.
--
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/39813de1-fa27-41d7-9422-7ef375ae36b4n%40googlegroups.com.
--
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/1521394189.1581958.1619887550289%40mail.yahoo.com.
