Hello AMF 
I have 5 year old quad core win 8.1 64 bit 8 G ram laptop running Ubuntu 16.04 
VM  I used it to build SDK kernel no problems and 
a new Debian 10 VM with a 64 bit GCC on same machine. The Debian VM is flaky 
last attempt  I just got memory calloc error on building 5.5 TI BSP from the 
instructions on Digikey.


I have a 10 year old win 7 quad core desktop I think it has 8 gig ram I never 
used I was contemplating either a dual boot or nuke win 7 a native Linux build 
box. Problem is it's probably 32 bit.
Which compiler are you using? 32 bit or 64 bit and a link to it would be great 
and Is this 5.x or 5.x 
I have several BBW, an am335x SK and two BBB for hardware. I'm also a JTAG user 
so I'd prefer nothing in EMC I don't know if that's possible?
I also probably need SD preparation instructions to go with kernel.
You know something like Robert has and the SDK has that even a college student 
can follow
Thanks alot!!
Mark


Sent from Yahoo Mail on Android 
 
  On Sun, May 30, 2021 at 11:02 AM, amf<fittere...@gmail.com> wrote:   Hi 
lazarman,on ubuntu 20.04, this builds ok
git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
cd ti-linux-kernel-dev
git checkout remotes/origin/ti-linux-rt-5.4.y -b ti-linux-rt-5.4.y
./build_kernel.sh

I've used VirtualBox before with Ubuntu 16/18/20 without any issues, what VM 
are you using?Several years ago a company that I worked for used some other VM, 
it was a pain in the azz to get to work, if i hear the name again i'll know if 
that was the one.I haven't used Debian for a desktop, so I can't help you with 
that. 

On Saturday, May 29, 2021 at 3:45:46 PM UTC-5 lazarman wrote:

 Hello 
I've failed to build following those instructions twice in Mainline  and twice 
using the TI BSP.version. the 2nd attempt of TI BSP is hung as we speak after 
resolving dependencies for several hours. Each attempt takes hours and the 
build_kernel script doesnt care you already cloned 2G of code it clones 
torvald.gitso I retried 4 times by running build_kernel.sh twice in both 
directories
The Mainline had some git branch errors today
I paid to upgrade my internet for this testing and was ready to buy a 64 bit 
box but am scared these instructions need a refresh and I will waste $$
what would be lovely is a 2 line like is in the instruction pasted below with 
something that will work for sure.the two directories I created are both on 
wrong branches and  dont complete a buil d
Be nice not keep downloading the 2G kernel source I know there is  a rebuild.sh 
but I am assuming that is used after a successful buildIf these instruction 
need I tweek I can understand I can test them. If it old and not supported a 
heads up would be appreciated. So I need something like this below with 
everything needed to build a kernel including the previous two steps as my two 
directories are on the wrong branches
Thanks

For TI v5.4.x: Real-Time#~/ti-linux-kernel-dev/
git checkout origin/ti-linux-rt-5.4.y -b tmp


Build:




Build:
#user@localhost:~/ti-linux-kernel-dev$
./build_kernel.s


Build:
#user@localhost:~/ti-linux-kernel-dev$
./build_kernel.s

Build:
#user@localhost:~/ti-linux-kernel-dev$
./build_kernel.sh



    On Friday, May 28, 2021, 02:56:38 PM CDT, Robert Nelson 
<robert...@gmail.com> wrote:  
 
 On Fri, May 28, 2021 at 2:53 PM Robert Nelson <robert...@gmail.com> wrote:
>
> On Fri, May 28, 2021 at 2:45 PM Robert Nelson <robert...@gmail.com> wrote:
> >
> > On Fri, May 28, 2021 at 2:41 PM Mark Lazarewicz <laza...@yahoo.com> wrote:
> > >
> > > Thanks!!
> > >
> > > Think of it as I'm validating the instructions I think having these is 
> > > something good. Unfortunately my VM blew up just now.
> > >
> > > I KNOW your adamant about not supporting VM.
> > >
> > > So I'll build a dedicated Debian 8 dev box.
> > >
> > > Any hints tips lessons learned what you use be appreciated.
> > >
> > > Have a great long weekend.
> >
> > VM's usually fail when using 'dd'.. so MLO/u-boot.img is usually the
> > failure point..
>
> I think mainline might work:
>
> debian@beaglebone:~$ uname -r
> 5.13.0-rc3-bone2.2
> debian@beaglebone:~$ dmesg | grep pru
> [    2.044506] remoteproc remoteproc1: 4a334000.pru is available
> [    2.045701] remoteproc remoteproc2: 4a338000.pru is available
> debian@beaglebone:~$ ls /dev/remoteproc/pruss-core*
> /dev/remoteproc/pruss-core0:
> coredump  device  firmware  name  power  recovery  state  subsystem  uevent
>
> /dev/remoteproc/pruss-core1:
> coredump  device  firmware  name  power  recovery  state  subsystem  uevent
>
> @Mark Yoder can you test? ;)

debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "start" > state
[  243.355728] remoteproc remoteproc1: powering up 4a334000.pru
[  243.366533] remoteproc remoteproc1: Booting fw image
am335x-pru0-fw, size 32456
[  243.374135] remoteproc remoteproc1: remote processor 4a334000.pru is now up

debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "stop" > state
[  296.981371] remoteproc remoteproc1: stopped remote processor 4a334000.pru

Regards,

-- 
Robert Nelson
https://rcn-ee.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/6dcb2683-2d69-45fa-a4a8-62bb6c6e3ed0n%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/787069572.912528.1622395347483%40mail.yahoo.com.

Reply via email to