Re: [beagleboard] Re: Debug tool for M4 processors in BBAI

['Mark Lazarewicz' via BeagleBoard]

Darren
People with 10k products in market use DSP for very fast matlab generated motor 
control the code is designed by PhDs in Control Theory. Same product uses PRU 
for LCD and extra UART. Product used every peripheral on ARM and DSP side used 
RTOS on DPS and communicated to TI c2000  DPS via SPI that did encoder. Notice 
the PRU controlled non hard realtime functions as the DSP ran bios with a clock 
tick in the nanoseconds. The only reason the PRU is deterministic is because 
it's bare bones. This product the ARM is only a host running a fail safe 
industrial redundant networking protocol. It loads the DSP and starts the 
network stack. It also loads the C2000 and dumps debug info into a custom 
messaging queue high priority and low priority. The PRU  UART ran a  monitor to 
dump debug info from queues to debug. The controls theory generated filters ran 
on DSP. I do remember the PhDs and geniuses who designed this in two years got 
an algorithm from TI application engineer's it set up the caches in in the 
shared memory the DPS code ran on to make it blazing fast. You get that kind of 
support when you buy 10k chips and deliver  real products consistently. The ARM 
ran Greenhill Integrity came with a BSP to initialize MUM and a custom second 
phase loader written by board support geniuses at GreenHills. You kind of 
support when buy a proven RTOS. Check the block diagrams to confirm the shared 
memory exists between PRU and DSP it may not exist if not make sure PRU can 
access DDR.
The advantage of using the SDK is it covers all the pieces. C6xx GCC support 
makes it less turnkey. ASK is turnkey it's what they give you with EVM to get 
products to market  fast. IMO you mix Apple's and oranges and they go rotten in 
the barrel which farmer do you ask for help? The Apple farmer points at the 
orange farmer 😃🤣😂

Sent from Yahoo Mail on Android 
 
  On Fri, Feb 19, 2021 at 12:47 PM, Darren Freed wrote:  
 I'm using Debian, and relied heavily on Mark Yoder's PRU cookbook to get one 
of the PRUs receiving analog data from an ADS1299 via SPI (bitbang on the PRU), 
and the data is then sent over to the A15 side via rpmsg.  Although I can't 
really complain about how things are working, I feel like I should be able to 
get greater efficiency from the setup if I could use one of the DSPs to do 
signal processing, and take that load off the A15. So I'm thinking 
PRU->DSP->A15 for the data flow.
Your point about the SDK is well taken.  I will work through those resources!
Many thanks,df



On Thu, Feb 18, 2021 at 9:43 PM 'Mark Lazarewicz' via BeagleBoard 
 wrote:

Hi Darren
Jeff has actual hardware I dont hopefully  we will summarize soon.
What is your application. Define it. Are you just playing or does it have 
requirements?Do you use RPMSG now?Do you have jtag?Are you open to an IDE like 
CCS to compile C66 code or want  command line Will your DSP share data with ARM 
is it barebones or RTOS?

And the biggest unresolved what happens if your Linux app can't use Debian we 
hope that's not the case but can you learn how to build stuff and have the time 
to learn in a Yocto environment and meet your project deadlines teach yourself 
TI RTOS and maybe break your PRU application 😉
How much time do you have?
At a minimum you will need to read all SDK documents,  decide about  RTOS or 
barebones it's kind of like a cookbook but Building DSP code isn't documented 
anywhere else if it is no can find it.
Basically you should start reading Linux  SDK/RTOS  docs for AI right  now 
install tools and modify  your board for JTAG debugging if you really want to 
learn real world skills with source level debugging. If your goal is copying a 
DSP binary to ARM to see DSP to ARM IPC this works right now guaranteed if you 
run SDK linux Jeff is verifying will it work on Debian it should we don't know.
Either way the answer is well documented had you looked and downloaded the SDK 
it explains how to utilize an AM5729 DSP. And with JTAG it doesn't matter what 
Linux is running on ARM and it really  shouldn't anyway. Jeff's verifying that 
true.
I suggest you got lots of reading to do and tools to install easy week of fun.
What are waiting for 🤣
You got 2 engineer's with 60 year's experience to ask questions for a 1 week go 
for it



Sent from Yahoo Mail on Android 
 
  On Thu, Feb 18, 2021 at 8:34 PM, Darren Freed wrote:   
Gentlemen,
I have been lurking here as a total noob, trying to exploit all the goodness in 
the AI.  For my application (University level physiology project), I've got the 
AI running well, using one of the PRUs for deterministic I/O (Thanks to Mark 
Yoder's PRU Cookbook), but I would love to be able to get the DSPs going as 
well.  So please keep up the good work and let us know what you're able to 
uncover and get working.
df

On Thu, Feb 18, 2021 at 6:55 PM 'Mark Lazarewicz' via BeagleBoard 
 wrote:

 Jeff
I have found much more documentation including how to move and change the DSP 
and M4 carve outs sizes 

[beagleboard] Using robot control library with beaglebone black with motor cape?

[Natalie Ferrante]

Hi all,

I am trying to run 4 DC motors with encoders at around 36V, and I am using 
the Beaglebone black with the motor cape. It doesn't seem like the motor 
cape has encoder functionality set up, so I wanted to be able to use the 
robot control library to control the motors and read the encoders. 

My question is what would it take to use the robot control library with the 
motor cape? I know that there is at least one pin conflict, one of the 
encoder 4 pins is used by the M2HIGH pin for the motor cape, and I am sure 
there are other conflicts that I have not caught. I need to be able to 
drive the motors at a higher voltage, so I can't just use the robotics 
cape. 

Thanks!

-- 
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/2fab2a1d-6eb9-4fcd-b1fa-f4898c48bd3cn%40googlegroups.com.

[beagleboard] Can you get past the 8V limit to the DC motors on the robotics cape?

[Natalie Ferrante]

Hi,

I am trying to use the robotics cape with the Beaglebone black, and I want 
to run 4 DC motors with encoders. I am not using a LiPo battery to power 
the system, I am just powering it from the barrel connector with 12V. 

The problem I am having is that I want to be able to run the motors at 12V, 
but the voltage that the motor drivers are seeing is being limited to 8V, 
regardless of if I am powering it from the barrel jack or from the battery 
terminals. I know that the motor driver chip is capable of driving 12V, but 
the board never sends more than 8V to it. My question is, is there a way 
for me to modify the board so that I can get past that 8V limit? 

Thanks!

-- 
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/fcf7341a-eb7a-4050-8915-d3637582e8afn%40googlegroups.com.

Re: [beagleboard] Re: Debug tool for M4 processors in BBAI

[jeff....@gmail.com]

I'm still learning Linux and how the multi-processor scheme works, but I'll 
share what I find out.

I forgot about that... probably worthwhile to read Professor Yoder's PRU 
Cookbook as it would some light on pmsg/rproc and the IPC considerations 
for the C66x from the BeagleBone/BeagleBoard perspective.. 

On Thursday, February 18, 2021 at 11:43:18 PM UTC-5 lazarman wrote:

> Hi Darren
>
> Jeff has actual hardware I dont
>  hopefully  we will summarize soon.
>
> What is your application. Define it. Are you just playing or does it have 
> requirements?
> Do you use RPMSG now?
> Do you have jtag?
> Are you open to an IDE like CCS to compile C66 code or want  command line 
> Will your DSP share data with ARM is it barebones or RTOS?
>
>
> And the biggest unresolved what happens if your Linux app can't use Debian 
> we hope that's not the case but can you learn how to build stuff and have 
> the time to learn in a Yocto environment and meet your project deadlines 
> teach yourself TI RTOS and maybe break your PRU application 😉
>
> How much time do you have?
>
> At a minimum you will need to read all SDK documents,  decide about  RTOS 
> or barebones it's kind of like a cookbook but Building DSP code isn't 
> documented anywhere else if it is no can find it.
>
> Basically you should start reading Linux  SDK/RTOS  docs for AI right  now 
> install tools and modify  your board for JTAG debugging if you really want 
> to learn real world skills with source level debugging. If your goal is 
> copying a DSP binary to ARM to see DSP to ARM IPC this works right now 
> guaranteed if you run SDK linux Jeff is verifying will it work on Debian it 
> should we don't know.
>
> Either way the answer is well documented had you looked and downloaded the 
> SDK it explains how to utilize an AM5729 DSP. And with JTAG it doesn't 
> matter what Linux is running on ARM and it really  shouldn't anyway. Jeff's 
> verifying that true.
>
> I suggest you got lots of reading to do and tools to install easy week of 
> fun.
>
> What are waiting for 🤣
>
> You got 2 engineer's with 60 year's experience to ask questions for a 1 
> week go for it
>
>
>
>
> Sent from Yahoo Mail on Android 
> 
>
> On Thu, Feb 18, 2021 at 8:34 PM, Darren Freed
>  wrote:
>
> Gentlemen,
>
> I have been lurking here as a total noob, trying to exploit all the 
> goodness in the AI.  For my application (University level physiology 
> project), I've got the AI running well, using one of the PRUs for 
> deterministic I/O (Thanks to Mark Yoder's PRU Cookbook), but I would love 
> to be able to get the DSPs going as well.  So please keep up the good work 
> and let us know what you're able to uncover and get working.
>
> df
>
>
> On Thu, Feb 18, 2021 at 6:55 PM 'Mark Lazarewicz' via BeagleBoard <
> beagl...@googlegroups.com> wrote:
>
> Jeff
>
> I have found much more documentation including how to move and change the 
> DSP and M4 carve outs sizes  some of it references the TRM but summarizes 
> it for a newb like myself and the three people in this group including you 
> that needed it and asked 
> There a professor at UIC who needs this data as well his use case is TI 
> RTOS DSP apps /Debian for his class
>
> Part of the problem is the SDK documents which describe RPMsg and Remote 
> Proc were shuffled around for some reason
>
> I saw a panic post in this group about preserving some wiki data I hope 
> its not this data I am grabbing everything I can related including TRM
>
> Bottom line you can do anything you want in SDK with any core and the Docs 
> are Gonzo good 
>
>  I'm not seeing the OP even responding and dont know why they didnt dig 
> deeper maybe they waiting for you to code it all up LOL
>
> I see no value in confusing anyone more in here except a summary after 
> this post to help the students and Professor
>
> You are confusing me abit about what you have working  probally because I 
> have not digested all the docs I found and digested your comments and 
> replys which are very generous
>
> Give me a day to digest the SDK provided docs and email me directly if you 
> have questions I feel confident enough to buy a board probally AI and play 
> with SDK Linux and TI RTOS examples with and without JTAG and CCS  we have 
> different goals I dont need Debian but you and me are good if you need me 
> or think I can help your doing quite well.
>
> reply directlyto lazarman and  please watch that you dont share private 
> stuff in this group like the recruiter story you posted i  this group that 
> doesnt belong in here  Im sure that was an accident but I feel I have found 
> a friend and appreciate your feedback.
>
> Lets regroup for a day and do our homework so we can summarize our 
> research I need HW so I am envious you are a step ahead but I have more 
> than enough docs to realize this is very well documented 
>
> Cheers my friend
>
> Mark
>
> On Thursday, February 18, 2021, 07:05:35 PM CST, jeff..

Re: [beagleboard] Re: Debug tool for M4 processors in BBAI

[Darren Freed]

I'm using Debian, and relied heavily on Mark Yoder's PRU cookbook to get
one of the PRUs receiving analog data from an ADS1299 via SPI (bitbang on
the PRU), and the data is then sent over to the A15 side via rpmsg.
Although I can't really complain about how things are working, I feel like
I should be able to get greater efficiency from the setup if I could use
one of the DSPs to do signal processing, and take that load off the A15. So
I'm thinking PRU->DSP->A15 for the data flow.

Your point about the SDK is well taken.  I will work through those
resources!

Many thanks,
df



On Thu, Feb 18, 2021 at 9:43 PM 'Mark Lazarewicz' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Hi Darren
>
> Jeff has actual hardware I dont
>  hopefully  we will summarize soon.
>
> What is your application. Define it. Are you just playing or does it have
> requirements?
> Do you use RPMSG now?
> Do you have jtag?
> Are you open to an IDE like CCS to compile C66 code or want  command line
> Will your DSP share data with ARM is it barebones or RTOS?
>
>
> And the biggest unresolved what happens if your Linux app can't use Debian
> we hope that's not the case but can you learn how to build stuff and have
> the time to learn in a Yocto environment and meet your project deadlines
> teach yourself TI RTOS and maybe break your PRU application 😉
>
> How much time do you have?
>
> At a minimum you will need to read all SDK documents,  decide about  RTOS
> or barebones it's kind of like a cookbook but Building DSP code isn't
> documented anywhere else if it is no can find it.
>
> Basically you should start reading Linux  SDK/RTOS  docs for AI right  now
> install tools and modify  your board for JTAG debugging if you really want
> to learn real world skills with source level debugging. If your goal is
> copying a DSP binary to ARM to see DSP to ARM IPC this works right now
> guaranteed if you run SDK linux Jeff is verifying will it work on Debian it
> should we don't know.
>
> Either way the answer is well documented had you looked and downloaded the
> SDK it explains how to utilize an AM5729 DSP. And with JTAG it doesn't
> matter what Linux is running on ARM and it really  shouldn't anyway. Jeff's
> verifying that true.
>
> I suggest you got lots of reading to do and tools to install easy week of
> fun.
>
> What are waiting for 🤣
>
> You got 2 engineer's with 60 year's experience to ask questions for a 1
> week go for it
>
>
>
>
> Sent from Yahoo Mail on Android
> 
>
> On Thu, Feb 18, 2021 at 8:34 PM, Darren Freed
>  wrote:
> Gentlemen,
>
> I have been lurking here as a total noob, trying to exploit all the
> goodness in the AI.  For my application (University level physiology
> project), I've got the AI running well, using one of the PRUs for
> deterministic I/O (Thanks to Mark Yoder's PRU Cookbook), but I would love
> to be able to get the DSPs going as well.  So please keep up the good work
> and let us know what you're able to uncover and get working.
>
> df
>
>
> On Thu, Feb 18, 2021 at 6:55 PM 'Mark Lazarewicz' via BeagleBoard <
> beagleboard@googlegroups.com> wrote:
>
> Jeff
>
> I have found much more documentation including how to move and change the
> DSP and M4 carve outs sizes  some of it references the TRM but summarizes
> it for a newb like myself and the three people in this group including you
> that needed it and asked
> There a professor at UIC who needs this data as well his use case is TI
> RTOS DSP apps /Debian for his class
>
> Part of the problem is the SDK documents which describe RPMsg and Remote
> Proc were shuffled around for some reason
>
> I saw a panic post in this group about preserving some wiki data I hope
> its not this data I am grabbing everything I can related including TRM
>
> Bottom line you can do anything you want in SDK with any core and the Docs
> are Gonzo good
>
>  I'm not seeing the OP even responding and dont know why they didnt dig
> deeper maybe they waiting for you to code it all up LOL
>
> I see no value in confusing anyone more in here except a summary after
> this post to help the students and Professor
>
> You are confusing me abit about what you have working  probally because I
> have not digested all the docs I found and digested your comments and
> replys which are very generous
>
> Give me a day to digest the SDK provided docs and email me directly if you
> have questions I feel confident enough to buy a board probally AI and play
> with SDK Linux and TI RTOS examples with and without JTAG and CCS  we have
> different goals I dont need Debian but you and me are good if you need me
> or think I can help your doing quite well.
>
> reply directlyto lazarman and  please watch that you dont share private
> stuff in this group like the recruiter story you posted i  this group that
> doesnt belong in here  Im sure that was an accident but I feel I have found
> a friend and appreciate your feedback.
>
> Lets regroup for a day 

Re: [beagleboard] Re: Simple application to start with: blink LED slowly

['Mark Lazarewicz' via BeagleBoard]

 Also please describe your tools versions in help requests Hopefully you have 
CCS 9.3
On Friday, February 19, 2021, 09:01:36 AM CST, 'Mark Lazarewicz' via 
BeagleBoard  wrote:  
 
  Code Composer Studio needs to know which Core you are targeting you didnt say 
which one?Modern IDE now make example code autogenerated its a template but 
there may be a project described in getting started bare metal please read 
quick start and CCS tutorial foe SOC for correct coreDo you have JTAG? the 
tutorials usually have a cookbook guideThings get more difficult with no JTAG . 
Please google the E2E forum or browse all help requests under sm5729
Good Luck
CCS/AM5728: CCS/AM5728: CCS Support for Beagle Bone AI with XDS200 - Code 
Composer Studio™ forum - Code Composer Studio™ - TI E2E support forums


| 
| 
|  | 
CCS/AM5728: CCS/AM5728: CCS Support for Beagle Bone AI with XDS200 - Cod...


 |

 |

 |





On Friday, February 19, 2021, 08:48:10 AM CST, ankit...@gmail.com 
 wrote:  
 
 
What is CCS?On Friday, February 19, 2021 at 7:34:15 PM UTC+5:30 
satzk...@gmail.com wrote:


OK, now I have my Beaglebone AI, installed TI's CCS, found a suitable compiler 
for the AI's SoC  in CCS, and want to start with a simple, bare-metal 
application to try things out.
So my question: what's next? What is necessary to e.g. have a timer which lets 
one of the user-LEDs blink slowly? Are there any tutorials or examples 
available for this somewhere?
Thanks :-)


-- 
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/3d4588c8-8338-45a8-bca6-969ff1b39dc1n%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/1090503506.135465.1613746877396%40mail.yahoo.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/1693306642.162176.1613752003842%40mail.yahoo.com.

Re: [beagleboard] Re: Simple application to start with: blink LED slowly

['Mark Lazarewicz' via BeagleBoard]

 Code Composer Studio needs to know which Core you are targeting you didnt say 
which one?Modern IDE now make example code autogenerated its a template but 
there may be a project described in getting started bare metal please read 
quick start and CCS tutorial foe SOC for correct coreDo you have JTAG? the 
tutorials usually have a cookbook guideThings get more difficult with no JTAG . 
Please google the E2E forum or browse all help requests under sm5729
Good Luck
CCS/AM5728: CCS/AM5728: CCS Support for Beagle Bone AI with XDS200 - Code 
Composer Studio™ forum - Code Composer Studio™ - TI E2E support forums


| 
| 
|  | 
CCS/AM5728: CCS/AM5728: CCS Support for Beagle Bone AI with XDS200 - Cod...


 |

 |

 |





On Friday, February 19, 2021, 08:48:10 AM CST, ankit...@gmail.com 
 wrote:  
 
 
What is CCS?On Friday, February 19, 2021 at 7:34:15 PM UTC+5:30 
satzk...@gmail.com wrote:


OK, now I have my Beaglebone AI, installed TI's CCS, found a suitable compiler 
for the AI's SoC  in CCS, and want to start with a simple, bare-metal 
application to try things out.
So my question: what's next? What is necessary to e.g. have a timer which lets 
one of the user-LEDs blink slowly? Are there any tutorials or examples 
available for this somewhere?
Thanks :-)


-- 
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/3d4588c8-8338-45a8-bca6-969ff1b39dc1n%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/1090503506.135465.1613746877396%40mail.yahoo.com.

[beagleboard] Re: Simple application to start with: blink LED slowly

[ankit...@gmail.com]

What is CCS?
On Friday, February 19, 2021 at 7:34:15 PM UTC+5:30 satzk...@gmail.com 
wrote:

>
> OK, now I have my Beaglebone AI, installed TI's CCS, found a suitable 
> compiler for the AI's SoC  in CCS, and want to start with a simple, 
> bare-metal application to try things out.
>
> So my question: what's next? What is necessary to e.g. have a timer which 
> lets one of the user-LEDs blink slowly? Are there any tutorials or examples 
> available for this somewhere?
>
> Thanks :-)
>

-- 
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/3d4588c8-8338-45a8-bca6-969ff1b39dc1n%40googlegroups.com.

[beagleboard] Simple application to start with: blink LED slowly

[Satz Klauer]

OK, now I have my Beaglebone AI, installed TI's CCS, found a suitable 
compiler for the AI's SoC  in CCS, and want to start with a simple, 
bare-metal application to try things out.

So my question: what's next? What is necessary to e.g. have a timer which 
lets one of the user-LEDs blink slowly? Are there any tutorials or examples 
available for this somewhere?

Thanks :-)

-- 
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/43efed19-37c7-43d2-a339-6911c1b2e8bao%40googlegroups.com.