Hello Brent,

Is it possible for you to share your schematic?

I have worked with other hardware platforms, but not the Beagleboard... 

Thanks
Chris

On Wednesday, December 5, 2012 7:55:01 PM UTC-8, Brent wrote:
>
> No, everything is working great.  Let me know if you have any problems.
>
> On Thursday, November 15, 2012 7:38:07 AM UTC-5, Andrzej wrote:
>
>> Hi Brent!
>> I am planning to use CAN BUS in beaglebone. Do you have some troubles 
>> with can since your last messege?
>>
>>
>> W dniu środa, 25 lipca 2012 19:21:16 UTC+2 użytkownik Brent napisał:
>>>
>>> For anyone reading this post, the method I used to initialize the can 
>>> bus did work.  I had a (very stupid) wiring problem which is why I thought 
>>> it was not working.  I used a standard 3.3V CAN Transceiver: TI SN65HVD231 
>>> and everything works perfectly.
>>>
>>> On Thursday, June 28, 2012 9:44:22 PM UTC-4, Brent wrote:
>>>
>>>> Nope, not working.  I've been fighting this too long and I'm ready to 
>>>> give up.  I'll just order the cape from Tower 
>>>> Technologies<http://www.towertech.it/en/products/hardware/tt3201-can-cape/>and
>>>>  pay out the nose...
>>>>
>>>> On Tuesday, June 26, 2012 10:53:37 PM UTC-4, Brent wrote:
>>>>
>>>>> I may have it working now, but won't be able to test for sure until 
>>>>> tomorrow.  can0 is now showing up... here is what I did:
>>>>>
>>>>> Added these two lines somewhere in the beaglebone_cape_setup() 
>>>>> function in the /arch/arm/mach-omap2/board-am335xevm.c file.
>>>>> setup_pin_mux(uart1dcan1_pin_mux);
>>>>> am33xx_d_can_init(1);
>>>>>
>>>>> A bit of a hack, but it seems to have done the trick.  I'll know for 
>>>>> sure when I plug it into my can bus tomorrow.
>>>>>
>>>>> On Tuesday, June 26, 2012 3:51:23 PM UTC-4, Koen Kooi wrote:
>>>>>>
>>>>>> You need platform data to init the can bus. Or as has been popular 
>>>>>> recently, emulate a can cape with an eeprom :) 
>>>>>>
>>>>>> Op 26 jun. 2012, om 20:00 heeft Brent het volgende geschreven: 
>>>>>>
>>>>>> > Well, still more problems...   Going back to my very first post 
>>>>>> about adding can0 by typing "ip link add dev can0 type can", I still get 
>>>>>> the same error message.  However, vcan works just fine (I enabled this 
>>>>>> in 
>>>>>> the config as well).  I even tried marking yes to everything in the CAN 
>>>>>> section, but still no luck.  Am I missing something else?  My config is 
>>>>>> shown below: 
>>>>>> >   
>>>>>> > # 
>>>>>> > # Network testing 
>>>>>> > # 
>>>>>> > # CONFIG_NET_PKTGEN is not set 
>>>>>> > # CONFIG_HAMRADIO is not set 
>>>>>> > CONFIG_CAN=y 
>>>>>> > CONFIG_CAN_RAW=y 
>>>>>> > CONFIG_CAN_BCM=y 
>>>>>> > CONFIG_CAN_GW=m 
>>>>>> > # 
>>>>>> > # CAN Device Drivers 
>>>>>> > # 
>>>>>> > # CONFIG_CAN_VCAN is not set 
>>>>>> > # CONFIG_CAN_SLCAN is not set 
>>>>>> > CONFIG_CAN_DEV=y 
>>>>>> > CONFIG_CAN_CALC_BITTIMING=y 
>>>>>> > CONFIG_CAN_TI_HECC=y 
>>>>>> > # CONFIG_CAN_MCP251X is not set 
>>>>>> > # CONFIG_CAN_SJA1000 is not set 
>>>>>> > # CONFIG_CAN_C_CAN is not set 
>>>>>> > CONFIG_CAN_D_CAN=y 
>>>>>> > CONFIG_CAN_D_CAN_PLATFORM=y 
>>>>>> > # 
>>>>>> > # CAN USB interfaces 
>>>>>> > # 
>>>>>> > # CONFIG_CAN_EMS_USB is not set 
>>>>>> > # CONFIG_CAN_ESD_USB2 is not set 
>>>>>> > # CONFIG_CAN_SOFTING is not set 
>>>>>> > # CONFIG_CAN_DEBUG_DEVICES is not set 
>>>>>> > 
>>>>>> > On Monday, June 25, 2012 8:08:11 PM UTC-4, RobertCNelson wrote: 
>>>>>> > On Mon, Jun 25, 2012 at 6:56 PM, Brent <> wrote: 
>>>>>> > > Thanks, that helped a lot!  I had an issue about not finding the 
>>>>>> firmware, 
>>>>>> > > but I found your post here to resolve that one. 
>>>>>> > > 
>>>>>> > > I feel like I'm seeing the light at the end of the tunnel. 
>>>>>>  Hopefully 
>>>>>> > > these are the last questions... Is the output in the 
>>>>>> arch/arm/boot/ 
>>>>>> > > directory?  Is there a procedure somewhere on how to get the 
>>>>>> files on the SD 
>>>>>> > > card? 
>>>>>> > 
>>>>>> > Your going to copy the uImage to where your boot script looks for 
>>>>>> it.. 
>>>>>> > (older looked in the fat16 partition, newer ones look under /boot/ 
>>>>>> on 
>>>>>> > the extX partition..) 
>>>>>> > 
>>>>>> > For the modules just do: 
>>>>>> > 
>>>>>> > make ARCH=arm CROSS_COMPILE=${CC} modules_install 
>>>>>> INSTALL_MOD_PATH=/media/rootfs 
>>>>>> > 
>>>>>> > or wherever you have your mmc's rootfs mounted... 
>>>>>> > 
>>>>>> > Regards, 
>>>>>> > 
>>>>>> > -- 
>>>>>> > Robert Nelson 
>>>>>> > http://www.rcn-ee.com/ 
>>>>>> > 
>>>>>> > -- To join: http://beagleboard.org/discuss 
>>>>>> > To unsubscribe from this group, send email to: 
>>>>>> > [email protected] 
>>>>>> > Frequently asked questions: http://beagleboard.org/faq 
>>>>>>
>>>>>>

-- 
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/groups/opt_out.

Reply via email to