search

dinuxbg / pru-gcc-examples

Simple example projects for PRU-GCC
49 stars 12 forks source link

Makefile update to ease the loading of PRU firmware #13

Open deebot opened 4 years ago

deebot commented 4 years ago

The existing makefile only compile the code. It was difficult to copy the code first to lib/firmware and then to go in /sys/class/remoteproc and echo the state to start and stop. The new Makefile makes it easier. Now the user just need to do make install_PRU0 after running make and the PRU is loaded with the new firmware. Also there are situations when the firmware is already in place and only a starting or stopping of PRU core is required. In such a case start_PRU0 and stop_PRU0 can be used. For PRU 1 just change the number to 1. Hope this will be of help to other users

deebot commented 4 years ago

It was difficult to copy the code first to lib/firmware and then to go in /sys/class/remoteproc and echo the state to start and stop

Could you elaborate why it is difficult? I did not expect copy-pasting a few commands to be a hurdle.

So when sombody just wants to run already written code , it is just copy- pasting once. But when i was doing development and trying to write and debug new code, every time i make some changes to the code and want to try out i had to run the commands again and again. In such a case it becomes tedious to copy and paste everytime to /lib/firmware then start from remotroc directory. Also after reboot the history is gone. So just doing make install would be simpler.

dinuxbg commented 4 years ago

It was difficult to copy the code first to lib/firmware and then to go in /sys/class/remoteproc and echo the state to start and stop

Could you elaborate why it is difficult? I did not expect copy-pasting a few commands to be a hurdle.

So when sombody just wants to run already written code , it is just copy- pasting once. But when i was doing development and trying to write and debug new code, every time i make some changes to the code and want to try out i had to run the commands again and again. In such a case it becomes tedious to copy and paste everytime to /lib/firmware then start from remotroc directory. Also after reboot the history is gone. So just doing make install would be simpler.

Please include such justification in the commit message and address the rest of the comments. Thanks.