GEL file is a simple script file CCSV6 uses to setup the SOC features like L3/L4 bus, DDR setup, Clock config, etc. The file is easy to read so you should be able to pull out the info you need.
Regards, John > On Nov 2, 2015, at 1:53 PM, William Hermans <[email protected]> wrote: > > Yeah, I hear you. This is part of what I described earlier regarding GEL > files which are necessary to configure the SOC so that the PRU’s can > function. I guess it is possible to do what you need, but then you have to > create a small bare bones file to run on the CortexA8 to replicate what the > GEL file does. Seems like a lot of work so I just use CCSV6 and a JTAG > emulator. Speak to TI and see if they have a solution for you. > > You may want to look at the demo example on > ti-processor-sdk-linux-am335x-evm-01.00.00.03 with the PRU patch applied. The > work with the PRU cape. That may be a good starting point to do what you > need. > > I'm not even sure what a GEL file is, or does. But this has to be possible > without using CCS, as remoteproc + rpmsg is a Linux specific thing. So > perhaps, maybe I need to get my hands on a GEL file, and figure out how to > "disassemble" what is being done. This, I can do, but it might take me time. > > On Mon, Nov 2, 2015 at 2:43 PM, John Syne <[email protected] > <mailto:[email protected]>> wrote: > Yeah, I hear you. This is part of what I described earlier regarding GEL > files which are necessary to configure the SOC so that the PRU’s can > function. I guess it is possible to do what you need, but then you have to > create a small bare bones file to run on the CortexA8 to replicate what the > GEL file does. Seems like a lot of work so I just use CCSV6 and a JTAG > emulator. Speak to TI and see if they have a solution for you. > > You may want to look at the demo example on > ti-processor-sdk-linux-am335x-evm-01.00.00.03 with the PRU patch applied. The > work with the PRU cape. That may be a good starting point to do what you > need. > > Regards, > John > > > > >> On Nov 2, 2015, at 1:31 PM, William Hermans <[email protected] >> <mailto:[email protected]>> wrote: >> >> John, >> >> Not an argument so much as a concern . . . those hands-on labs are specific >> to CCS, with no clear way of proceeding otherwise. e.g. I'd much prefer a >> GNU approach. But I'll gloss over those labs yet again . . . and read what >> other information is out there to see if this can be done with a gcc >> toolchain. >> >> CCS is a fine IDE, and set of tools, but not everyone has the need, or even >> want / capability to use such a tool. >> >> On Mon, Nov 2, 2015 at 2:24 PM, John Syne <[email protected] >> <mailto:[email protected]>> wrote: >> The best way to learn this is to follow the LAB >> >> http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs >> <http://processors.wiki.ti.com/index.php/PRU_Training:_Hands-on_Labs> >> >> Specifically, Lab4 onwards. Other than that, the examples are well >> documented. >> >> >> Regards, >> John >> >> >> >> >>> On Nov 2, 2015, at 12:55 PM, William Hermans <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> John Syne got the remoteproc_pruss working >>> >>> Grab the firmware: >>> >>> cd /opt/scripts/tools/ >>> git pull >>> sudo cp /opt/scripts/device/bone/pru-rpmsg_client_sample/am335x* >>> /lib/firmware/ >>> sudo reboot >>> >>> sudo modprobe rpmsg_client_sample >>> >>> So Robert, or John, >>> >>> What remoteproc's capability in our kernel right now ? Is this a simple >>> example of what's to come, or is this fully functional now ? Also, is there >>> good documentation out there other than the txt file / source code ? I know >>> that Jason Reeder ? from TI has been doing a lot of work on code, and >>> documentation here and there. But is there a comprehensive guide, or >>> documentation that covers the whole API, etc ? >>> >>> On Mon, Nov 2, 2015 at 12:33 PM, Robert Nelson <[email protected] >>> <mailto:[email protected]>> wrote: >>> 4.1.12-ti-r26 >>> We've re-enabled the shutdown button, works best with "systemd"... >>> >>> John Syne got the remoteproc_pruss working >>> >>> Grab the firmware: >>> >>> cd /opt/scripts/tools/ >>> git pull >>> sudo cp /opt/scripts/device/bone/pru-rpmsg_client_sample/am335x* >>> /lib/firmware/ >>> sudo reboot >>> >>> sudo modprobe rpmsg_client_sample >>> >>> >>> kernel updater: >>> >>> cd /opt/scripts/tools/ >>> git pull >>> sudo ./update_kernel.sh <OPTIONS> >>> >>> "--bone-kernel --testing" is now "4.3.0-bone1" vs "4.2.5-bone2" >>> >>> Consider v4.2.x now retired, yet still buildable via: >>> >>> https://github.com/RobertCNelson/bb-kernel/tree/am33x-v4.2 >>> <https://github.com/RobertCNelson/bb-kernel/tree/am33x-v4.2> >>> >>> Regards, >>> >>> -- >>> Robert Nelson >>> https://rcn-ee.com/ <https://rcn-ee.com/> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> <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 [email protected] >>> <mailto:beagleboard%[email protected]>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >>> >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> <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 [email protected] >>> <mailto:[email protected]>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> <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 [email protected] >> <mailto:[email protected]>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. >> >> >> -- >> For more options, visit http://beagleboard.org/discuss >> <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 [email protected] >> <mailto:[email protected]>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > For more options, visit http://beagleboard.org/discuss > <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 [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > > -- > For more options, visit http://beagleboard.org/discuss > <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 [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <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 [email protected]. For more options, visit https://groups.google.com/d/optout.
