Good stuff Thanks! and I am guessing the ICCS_SDK just provides examples/ and sw support of how to implement the various various protocols like DeviceNet and CAN? I got two Bones today and the CAN capes should be shipped soon so this caught my attention thanks. Now if I just knew where I could get the JTAG adapter installed I would be elated. The link posted earlier by Gerald suggests an RMA but I was NOT sure if this referred to after being damaged adding the JTAG by a novice or I could just either pay for it or request it by RMA. |
--
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.
For more options, visit https://groups.google.com/groups/opt_out.
Hi Max Present(paid) Well I am doing a CAN device drivers for TI C2000 for RTOS(SYSBIOS) at work so the peripherals(CAN controller) are what I am focused on and interested inRelavent to this group Future(hobby/career enhancement) for Sitara the can controller is called DCAN this code that talks to this is provided in starterware(bare bones no OS). From what have read the kernel for Bone supports the network driver for CAN developed by Volkswagen so I start with getting two bones talking study/tweek linux device drivers Non relavent to opensource Sysbios or barebones OS running the starterware./sdk CAN code on A8 of Bone using JTAG and codecomposer. spend $78 for xds100 CCS is free. JTAG shortens debug of
complez hard real time bugs Email me anytime if you think I can be of help for general firmware questions. its not that I dont want to share here I have little experience presently doing Linux device drivers but 28 years doing other RTOS drivers hope to change this and help out the cause as a driver is driver for most OS . Linux drivers are SLIGHTLY different than LynxOS and QNX cpmmercial RTOS One last comment I saw the first consulting opening for a Sitara job this means people are using the chip beyond handsets and opensource tinkering. the chip has all the peripherals and low power so I think this chip is here to stay. also linux is making inroads into more embedded systems where hard realtime RTOS have been used(now I better go as I dont want to step on any toes). They both have a place and it looks like Gerad and Jason have ensured that TI is the best choice for support in
open arena and the E2E forum is OK for TI SYSBIOS help --- On Thu, 5/16/13, Max <lisa...@gmail.com> wrote: |
--
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/u28ytaoNenU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
Hello,
I am also very interesting about this.
I need to complete a fast ADC / DAC with some numeric matrix calculation. I thought about using a BBB, and the PRUs seemed to be a very interesting point. The numeric part could be done using Xenomai.
Apparently the use of SPI with the PRUs is possible. So can I use SPI ADC / DAC with the PRU?
Could anyone be more precise on how to do it? Write SPI drivers for the PRU?
If I was not clear enough, tell me :)
Thank you very much
>It is a slightly updated version from the one I've been providing in
>beta. I've been waiting for a response to my request for a direct
>download, rather than needing to download all of CCS, before I posted
>something. Seems the cat is out of the bag!
Very cool, thanks Jason. Hopefully you get a response to the direct download request, that would be preferable over all of CCS.
--
Mark
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+un
Each PRU has it's own r30, which drives the direct outputs (assuming you
have the pinmux setup properly). You can only drive a limited number of
the BeagleBone header pins using PRU direct I/O, and a lot of the pins
are shared with the LCD/HDMI interface.
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/u28ytaoNenU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
--
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.
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/u28ytaoNenU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.
Hi,
I want to use the DCAN interface on PRU-ICSS to send/receive data present on DDR RAM at a fixed physical address.
- Address of DDR is 0x8000_0000 to 0x9000_0000(256MiB)
- My buffer is present at 0x8FF0_0000 to 0x9000_0000 (1MiB)
As soon as I access the hardware address 0x8FF0_0000 the PRU-ICSS goes into some faulty state and becomes unresponsive.
Is there some other way to access DDR from PRU-ICSS ?
Rakesh