[beagleboard] Kadkahwin Malaysia | Thank you card | Sweet kad

[worksai kumar]

*Nikmat perkahwinan*

Show your appreciation to your wedding guests with your Nikmat perkahwinan 
. Unique and purely handmade 
Malay wedding favors, wedding gifts & decorative items to make your wedding 
a memorable event. Say Good bye to your guests with creative and unique 
nikmat perkahwinan and Malay party favors. Choose a best thank you card 
that showcases your personal style. Our range includes 3D Props, 2D Props, 
Arrow, Banner, Box, Bunting, Backdrops, Button badge, Stickers, Guest book, 
bags, welcome board etc.

3D Props

Opting for 3D Props wedding favours is a great way to give a personal and 
distinctive nikmat perkahwinan , 
something so unique that your guests will have a hard time forgetting about 
it. Sweet kad provides unique and custom 3D scanning and printing.

2D Props 

Make your special event even more special with our custom 2D Props printing 
effects. Explore different shapes and sizes, color and stock finishes.

Arrow

Celebrate your great wedding with Sweet kad. We provide awesome arrow 
nikmat perkahwinan  here are 
perfect for your wedding day.

Box

Beautifully presented favors in elegant embossed boxes and simple gifts. 
Personalize with custom printed ribbon and tags. Our large array of nikmat 
perkahwinan boxes and packaging can offer you everything from formal to 
casual, colourful or black and white.

 

Banner

Customize your own unique message with banners designed for modern to 
rustic themes. One of our beautiful party banners will add style and 
personality to your wedding decor! Choose one of our popular gold foil 
letter pennant banner kits if you need to be able to create a variety of 
unique phrases with a single kit. All of these banners are made with 
high-quality materials, so you can reuse them for your engagement party, 
bridal shower, bachelorette party and reception.

Bunting 

Bunting is one of the easiest DIY decor projects you can make for a 
wedding. Mini-bunting projects are an adorable detail to add to your 
wedding decor. Pick fabric or paper that showcases your beautifully pale 
wedding colors on a smaller scale.

Back Drops

All of our backdrops are designed to cover a vast space and to complement 
your chosen topic. Our backdrops are generally made from thick plastic 
sheets and can vary in size, and all feature printed scenic details on one 
side.

Button Badge

We supply all kind of button badge accessories for example, button pin and 
Mylar in button back pin. Sweet kad provides competitive pricing on various 
sizes of button badge for you.

Guest book

Guest books are a wonderful tradition and one that will be treasured for 
years to come. Our selection of books and pens range from the traditional 
to the unique – the formal to the casual, the unrestrained to the simple.

Stickers

Our custom stickers have been lovingly designed and given a palette of 
colors that make them perfect for weddings, showers, anniversaries, and 
other special events.

Tags

Create unforgettable keepsakes with custom-designed hang tags for your 
nikmat perkahwinan . 
Personalized favor hang tags are perfect to commemorate life’s most special 
events and celebrations.

 

 

 

Welcome Board

Often one of the first details your guests see, welcome boards greet your 
friends and family and give a tiny hint to your style. We've collected the 
most popular types of welcome boards, focusing primarily on chalkboard, 
wooden, and glass designs.

*Why choose us*

Any one of these nikmat perkahwinan and decor ideas will surely add to the 
fun and festivity of your wedding day. We offer a variety of edible favors 
with pretty, floral packaging that's modified with the names of you and 
your spouse. At my nikmat perkahwinan, shopping for mementos to present to 
your guests might be the most enjoyable part of the wedding planning 
process. Sweet kad is committed to providing an unmatched selection of high 
quality thank you cards, gifts and supplies as well as exceptional customer 
service so that every celebration can be an once-in-a-lifetime event. We 
want to inspire our customers and help them find the perfect way to honour 
their achievements, and to thank their loved ones.

*Contact us:*

No 6 Jalan P2/6A

Tiara industrial Park

Bandar Teknologi Kajang

43500 Semenyih Selangor

Malaysia.

Whatsapp:012 . 341 7848

Email:  sa...@sweetkad.com
*YouTube URL:*
https://www.youtube.com/watch?v=NobvxOZq-3I&feature=youtu.be

-- 
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 ema

[beagleboard] Kadkahwin Malaysia | Thank you card | Sweet kad

[worksai kumar]

[image: http://www.sweetkad.com/nikmat-perkahwinan/] 


*Nikmatperkahwinan* 

Show your appreciation to your wedding guests with your Nikmat perkahwinan. 
Unique and purely handmade Malay wedding favors, wedding gifts & decorative 
items to make your wedding a memorable event. Say Good bye to your guests 
with creative and unique nikmat perkahwinan and Malay party favors. Choose 
a best thank you card that showcases your personal style. Our range 
includes 3D Props, 2D Props, Arrow, Banner, Box, Bunting, Backdrops, Button 
badge, Stickers, Guest book, bags, welcome board etc.

3D Props

Opting for 3D Props  wedding 
favours is a great way to give a personal and distinctive nikmat 
perkahwinan, something so unique that your guests will have a hard time 
forgetting about it. Sweet kad provides unique and custom 3D scanning and 
printing.

2D Props

Make your special event even more special with our custom 2D Props printing 
effects. Explore different shapes and sizes, color and stock finishes.

Arrow

Celebrate your great wedding with Sweet kad 
. We provide awesome arrow 
nikmat perkahwinan here are perfect for your wedding day.

Box

Beautifully presented favors in elegant embossed boxes and simple gifts. 
Personalize with custom printed ribbon and tags. Our large array of nikmat 
perkahwinan boxes and packaging can offer you everything from formal to 
casual, colourful or black and white.

 

Banner

Customize your own unique message with banners designed for modern to 
rustic themes. One of our beautiful party banners will add style and 
personality to your wedding decor! Choose one of our popular gold foil 
letter pennant banner kits if you need to be able to create a variety of 
unique phrases with a single kit. All of these banners are made with 
high-quality materials, so you can reuse them for your engagement party, 
bridal shower, bachelorette party and reception.

Bunting

Bunting is one of the easiest DIY decor projects you can make for a 
wedding. Mini-bunting projects are an adorable detail to add to your 
wedding decor. Pick fabric or paper that showcases your beautifully pale 
wedding colors on a smaller scale.

Back Drops

All of our backdrops are designed to cover a vast space and to complement 
your chosen topic. Our backdrops are generally made from thick plastic 
sheets and can vary in size, and all feature printed scenic details on one 
side.

Button Badge

We supply all kind of button badge accessories for example, button pin and 
Mylar in button back pin. Sweet kad provides competitive pricing on various 
sizes of button badge for you.

Guest book

Guest books are a wonderful tradition and one that will be treasured for 
years to come. Our selection of books and pens range from the traditional 
to the unique – the formal to the casual, the unrestrained to the simple.

Stickers

Our custom stickers have been lovingly designed and given a palette of 
colors that make them perfect for weddings, showers, anniversaries, and 
other special events.

Tags

Create unforgettable keepsakes with custom-designed hang tags for your 
nikmat perkahwinan. Personalized favor hang tags are perfect to commemorate 
life’s most special events and celebrations.

 

 

 

Welcome Board

Often one of the first details your guests see, welcome boards greet your 
friends and family and give a tiny hint to your style. We've collected the 
most popular types of welcome boards, focusing primarily on chalkboard, 
wooden, and glass designs.

*Why choose us*

Any one of these nikmat perkahwinan and decor ideas will surely add to the 
fun and festivity of your wedding day. We offer a variety of edible favors 
with pretty, floral packaging that's modified with the names of you and 
your spouse. At my nikmat perkahwinan, shopping for mementos to present to 
your guests might be the most enjoyable part of the wedding planning 
process. Sweet kad is committed to providing an unmatched selection of high 
quality thank you cards, gifts and supplies as well as exceptional customer 
service so that every celebration can be an once-in-a-lifetime event. We 
want to inspire our customers and help them find the perfect way to honour 
their achievements, and to thank their loved ones.

*Contact us:*

No 6 Jalan P2/6A

Tiara industrial Park

Bandar Teknologi Kajang

43500 Semenyih Selangor

Malaysia.

Whatsapp:012 . 341 7848

Email:  sa...@sweetkad.com
*YouTube URL:*
https://www.youtube.com/watch?v=NobvxOZq-3I&feature=youtu.be

-- 
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 vi

Re: [beagleboard] Re: BBB- DCAN1 problems using latest debian image

[Tracy Smith]

Hi John, 

Do you see support for both CAN0 and CAN1?  Need both and our pins for CAN1 are 
E17 and E18 in the TI pinmux tool.  Found the pad names and pins in uboot 
pinmux for CAN0 after this post.  Haven’t found pad names associated with 
E17/E18 yet in uboot pinmux. Will look at the kernel dts today.  

My question I guess will CAN1 be available when plugging in the CANUSB and 
where do you see CAN1 indicated?  If supported, it will appear as /dev/ttyUSB1? 
 Or, as a different device on the BBB?  Eventually may need as many as four 
CAN0-3.

Thx, Tracy

> On Oct 31, 2017, at 8:00 PM, John Dammeyer  wrote:
> 
> The CANUSB from Lawicel is a standard USB device that looks like a serial 
> port since it can use the FTDI driver.
>  
> On my MachineKit Debian Beagle 2.0 when I plug in the CANUSB I find I have a 
> /dev/ttyUSB0 device.
> I installed putty and connected to /dev/ttyUSB0
> In the terminal window
> V with a CR returns
> V1011
> An S5 sets 250kbps
> An O opens the port.
> t12327788 with a CR again of course sends SID=123, DLC=2, Data 0x77 0x88
> With nothing connected to the CANUSB the red LED goes on.  (or if bitrate is 
> wrong).
> A C closes the port.
> An F prints the error flags and shuts off the red led.
>  
> It’s a good idea to have auto line feed set in putty so that each received 
> message is on a new line.
> John Dammeyer
>  
>  
>  
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
> Behalf Of Tracy Smith
> Sent: October-31-17 3:42 PM
> To: BeagleBoard
> Subject: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
>  
> Hi John,
> 
> I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have a 
> custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2.  
> 
> The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for the 
> BBB includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names 
> for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9 
> (pin E18), 
> 
> 1. Did I miss the names for these pins in u-boot?
> 
> 2. If u-boot does not support these pins, should they be added to u-boot, 
> and/or added to the kernel to support these pins?
> 
> Should these pins be pinmuxed in both uboot and the  kernel, or only in the 
> kernel dts?  Checking now to see if the kernel has support for these pins.
> 
> thx, Tracy
> 
> On Wednesday, April 8, 2015 at 8:20:29 AM UTC-5, Mark Irwin wrote:
> Hi,
>  
> I have been trying to build a proof of concept system using two beaglebone 
> black units with there DCAN1 (pins P9_24 and P9_26) and two can transcievers 
> TI SN65HVD251P.
> The can transceivers are powered from the same 5V bench supply as both of the 
> beaglebone blacks. the canh and canl pins are terminated at both ends by 120R 
> resistors to ensure the 60R bus impedence. 
>  
> I was following the instructions in other posts about updating to the latest 
> debian version and then upgrading the kernel to 3.14. This i have done.
> uname -a
> Linux beaglebone 3.14.35-ti-rt-r56 #1 SMP PREEMPT Sun Mar 29 01:13:05 UTC 
> 2015 armv7l GNU/Linux
>  
> I added dtb=am335x-boneblack-can1.dtb to the uEnv.txt
>  
> I have also installed the canbus tools within the image so i can attempt a 
> cangen can0 and candump can0.
>  
> On system boot i am doing the following:
>  
> modprobe can
> modprobe can-dev
> modprobe can-raw
>  
> ip link set can0 type can bitrate 125000 triple-sampling on
> ifconfig can0 up
>  
> however if i use candump can0 and cangen can0 within two seperate putty 
> sessions i dont see anything. 
>  
> If I create a vcan bus i do see the messages in loopback.
> sudo modprobe vcan
> sudo ip link add dev vcan0 type vcan
>  sudo ifconfig vcan0 up
>  
> Previously I was using an older debian image and found that when i ran cangen 
> can0 that the buffer would give me an error that it was full. however now 
> with the latest image i am not getting the bufer full message but still not 
> seeing anything on the candump. What should i expect to see here?
>  
> Can anyone see where I have gone wrong or a step i am missing?
>  
> Thanks in advance.
>  
> Mark
>  
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> 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/_9u1B6ZkgCU/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/e6297438-0999-4320-916e-f41d74671533%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "BeagleBoard" group.
> To unsubscribe from

Re: [beagleboard] Re: u-boot support for pins

[Tracy Smith]

Hi William,

Using the TI pinmux tool it provides two pins associated with CAN1. One for TX 
and one for RX.  I just need to use these two pins for the uboot overlays 
instead of the I2C P9 extension header supported by the most recent kernel 
releases. On our custom BBB we don’t have a P9 and instead we use test point 
pins for CAN1. CAN0 is no longer a concern since I have the pad names 
associated with the pins I need.

I need to know the pad name or how to create the pad names for these two pins 
the pinmux tool associates with CAN1, so I can use these for the u-boot pinmux 
and the kernel device tree.  I agree this is not difficult when you have the 
pad names and the pins available. Simply copy, paste, and modify the dts and 
pinmux file as needed.

Thx, Tracy

Sent from my iPad

> On Oct 31, 2017, at 7:55 PM, William Hermans  wrote:
> 
> SO what is it that you're trying to do ? I've read your posts, but am still 
> mystified. Just sayin' . . . I've been working with this hardware for around 
> 5 years now,  have written many device tree overlays for various hardware 
> configurations. Including GPIO, I2C, UART, CAN, SPI, etc.
> 
> I'm willing to give you some guidance, but need to understand what it is 
> you're trying to do . . .
> 
> I2C really isn't that hard to get working. Nor is most of it.
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> 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/dE1bIym6rDg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CALHSORrdO87s1J7uKrJ%2BEvRKQRmKhahZBq%3DmtK1ktk4sChsbkA%40mail.gmail.com.
> For more options, visit 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/61C6671A-8967-48F3-A46A-A8F521690382%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Cannot get BBB to flash new OS image

[geert . schrooten]

 

I’m trying to upgrade my old BBB-A5B to the latest Debian as well. I’m not 
planning to use emmc.

At the moment I’m always required to press “s2-user boot” button during 
power up (physical plugin in the cable during the process) in order to boot 
from microSD with the latest versions. If I use the old image 
“bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img”, the SD boots correctly 
without the need to use the s2 button every time there is a power 
interruption or shutdown command (reboot works).

Starting without SD card also works fine (Angstrom).

With the current Debian 9.1 on SD 3 leds light up (0-3) and stay on without 
blinking (more than 6h tested). Same with Debian 8.7, 9.2.

 

*Johncarp*,

Can you help me by confirming that you got the same issue booting from SD – 
Debian 9.1 or 9.2 without pressing “s2 - user boot” button when you plug 
the power cable in. Perhaps it’s a malfunction in my BBB almost 2 years up 
and running.


Op maandag 30 oktober 2017 12:20:23 UTC+1 schreef johncarp...@gmail.com:
>
> Sorry if this is answered somewhere, I looked around and couldn't find 
> anything on it in this forum.
>
> Someone gave me a BBB to play with, it has Debian 7.x on it, I would like 
> to upgrade it to the latest OS image.
>
> I went to this page (http://beagleboard.org/getting-started#step2) and am 
> following the instructions.
>
> I downloaded an image onto my macbook from this page - 
> https://beagleboard.org/latest-images. I chose Debian 9.2 2017-10-10 4GB 
> SD IoT 
> 
>  .
>
> I used Etcher to burn the image onto a microSD card.
>
> I inserted the card into the slot on the BBB, held down the User Boot 
> button, inserted the power cord, waited until the four LEDs went off, then 
> let go of the button.
>
> No joy. I was only booting from the microSD card, not flashing the image 
> into the eMMC.
>
> I tried to follow the directions to convert the image to a "flasher". The 
> file that I am supposed to modify (/boot/uEnv.txt) was not in the specified 
> directory. However, I did find it in the /boot/uboot folder. However when I 
> edited it, the line that was I was supposed to uncomment was not there. The 
> script that the non-existent line was supposed to run (
> cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh) also is 
> nowhere to be found.
>
> The system boots just fine from the microSD card, so i think the image on 
> there is ok.
>
> So... what do I try next?
>

-- 
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/b9df7eb1-f866-4b5f-b46a-4ddcf66cf967%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] apt-show-versions

[learnerbr]

Webmin install complete. You can now login

Thx!! You saved my time!! :)

2016년 6월 22일 수요일 오후 11시 4분 13초 UTC+9, bucks...@gmail.com 님의 말:
>
> Removing /etc/apt/apt.conf.d/02compress-indexes didn't work for me (not 
> sure why). But I got webmin 1.801 installed on Jessie by doing:
> apt-get purge apt-show-versions
> rm /var/lib/apt/lists/*gz
> apt-get -o Acquire::GzipIndexes=false update
> apt-get install apt-show-versions
> dpkg -i webmin_1.801_all.deb
>
> Hope this helps any other poor souls out there.
>
>

-- 
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/0b84ffa0-2afa-40a2-b311-3aa58845dec0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cannot get BBB to flash new OS image

[Robert Nelson]

On Wed, Nov 1, 2017 at 1:51 AM,   wrote:
> I’m trying to upgrade my old BBB-A5B to the latest Debian as well. I’m not
> planning to use emmc.
>
> At the moment I’m always required to press “s2-user boot” button during
> power up (physical plugin in the cable during the process) in order to boot
> from microSD with the latest versions. If I use the old image
> “bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img”, the SD boots correctly
> without the need to use the s2 button every time there is a power
> interruption or shutdown command (reboot works).
>
> Starting without SD card also works fine (Angstrom).
>
> With the current Debian 9.1 on SD 3 leds light up (0-3) and stay on without
> blinking (more than 6h tested). Same with Debian 8.7, 9.2.

So erase the eMMC, it's getting in the way of the microSD booting..

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/CAOCHtYjcC7Fg2QedWEFs-r20bGwWvKzfO3Ejm-K8EZ7wd2qoQg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Serial Communication Via XBee, BBB, and AT Commands/Yea Boy!

[Mala Dies]

Hello Again,

I had to do some research on XBee pin spacing and breadboards. The 
"dog-gone" pin spacing is off by 0.54 from XBee to the breadboards. I found 
a link w/ some already assembled adapter boards. Now, when these items come 
in, I can start to use the book to perform basic functions w/ the XBee 
radios.

Seth

On Thursday, October 19, 2017 at 8:21:26 PM UTC-5, Mala Dies wrote:
>
> Hello,
>
> I am following along in a book, "The Hands-on XBee Lab Manual" by Titus. 
> If you are a newcomer to XBee and the BBB, get w/ me on this project. 
> Purchase the book and we can rewind and retrieve on BBB, XBee ideas, and w/ 
> AT Commands.
>
> Seth
>
> P.S. If you are experienced in XBee and serial/UART communication, jump on 
> in. There is no reason to just make this entire forum full of our 
> complaints or issues. We can use this forum as a discussion board, too. So, 
> anyway. Please contact me or leave a message to this post in the methods 
> you use to perform serial communications w/ your XBee and the BBB. Yea boy! 
> Digi International has a ton of free resources too. You can find them at 
> digi.com. So, get a BBB, a XBee, and an adapter board. Then, we can 
> serialize communications to the advancement of our forum. Oh and see here: 
> http://www.mathsisfun.com/binary-decimal-hexadecimal-converter.html. If 
> you need to convert, there is a free resource.
>

-- 
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/37a1d239-6388-4ab7-b1c6-fba2c8dc1277%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

RE: [beagleboard] Re: BBB- DCAN1 problems using latest debian image

[John Dammeyer]

CAN1 and CAN2 are available when you aren’t using any other cape and I think 
eiher HDMI or perhaps it’s the LCD interface.  It’s been a while.  There is no 
relationship between /dev/ttyUSB0 and the CAN devices.  One requires a CAN 
driver to function while the other is purely a serial port like a UART.
 
To get 5 CAN ports I chose the Freescale 9S12 series.  I think ST Micro also 
makes an ARM compatible processor with 4 CAN ports.  There aren’t a lot around.
 
If you want higher speed access along with message interrupts than what you can 
get with USB FTDI based CAN connections your alternative approach will be to 
add Microchip MCP2515s on board and use the SPI bus interface.  With 3 select 
lines to a 3:8 mux you can select one of 4 CAN devices, and wire-OR the 
interrupts.  You just have to poll which one caused the interrupt.  I believe 
there is a driver for the MCP2515 already in the Beagle CAN library.
 
Alternatively, since you are already building a cape that has CAN drivers on it 
and you now you want at least 2 more CAN devices it may be easier to use a 
second processor that has two CAN ports.  Write the firmware to look like an 
SPI based MCP2515 and you can use the stock Beagle CAN driver for it.
 
In fact, use either the ST Micro ARM and make all the CAN ports on it appear as 
if they were MCP2515s and that then frees up your other pins on the Beagle.
 
John
 
 
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Tracy Smith
Sent: November-01-17 2:51 AM
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
 
Hi John, 
 
Do you see support for both CAN0 and CAN1?  Need both and our pins for CAN1 are 
E17 and E18 in the TI pinmux tool.  Found the pad names and pins in uboot 
pinmux for CAN0 after this post.  Haven’t found pad names associated with 
E17/E18 yet in uboot pinmux. Will look at the kernel dts today.  
 
My question I guess will CAN1 be available when plugging in the CANUSB and 
where do you see CAN1 indicated?  If supported, it will appear as /dev/ttyUSB1? 
 Or, as a different device on the BBB?  Eventually may need as many as four 
CAN0-3.
 
Thx, Tracy

On Oct 31, 2017, at 8:00 PM, John Dammeyer  wrote:
The CANUSB from Lawicel is a standard USB device that looks like a serial port 
since it can use the FTDI driver.
 
On my MachineKit Debian Beagle 2.0 when I plug in the CANUSB I find I have a 
/dev/ttyUSB0 device.
I installed putty and connected to /dev/ttyUSB0
In the terminal window
V with a CR returns
V1011 
An S5 sets 250kbps
An O opens the port.
t12327788 with a CR again of course sends SID=123, DLC=2, Data 0x77 0x88
With nothing connected to the CANUSB the red LED goes on.  (or if bitrate is 
wrong).
A C closes the port.
An F prints the error flags and shuts off the red led.
 
It’s a good idea to have auto line feed set in putty so that each received 
message is on a new line.
John Dammeyer
 
 
 
From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Tracy Smith
Sent: October-31-17 3:42 PM
To: BeagleBoard
Subject: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
 
Hi John,

I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have a 
custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2.  

The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for the 
BBB includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names 
for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9 
(pin E18), 

1. Did I miss the names for these pins in u-boot?

2. If u-boot does not support these pins, should they be added to u-boot, 
and/or added to the kernel to support these pins?

Should these pins be pinmuxed in both uboot and the  kernel, or only in the 
kernel dts?  Checking now to see if the kernel has support for these pins.

thx, Tracy

On Wednesday, April 8, 2015 at 8:20:29 AM UTC-5, Mark Irwin wrote:
Hi,
 
I have been trying to build a proof of concept system using two beaglebone 
black units with there DCAN1 (pins P9_24 and P9_26) and two can transcievers TI 
SN65HVD251P.
The can transceivers are powered from the same 5V bench supply as both of the 
beaglebone blacks. the canh and canl pins are terminated at both ends by 120R 
resistors to ensure the 60R bus impedence. 
 
I was following the instructions in other posts about updating to the latest 
debian version and then upgrading the kernel to 3.14. This i have done.
uname -a
Linux beaglebone 3.14.35-ti-rt-r56 #1 SMP PREEMPT Sun Mar 29 01:13:05 UTC 2015 
armv7l GNU/Linux
 
I added dtb=am335x-boneblack-can1.dtb to the uEnv.txt
 
I have also installed the canbus tools within the image so i can attempt a 
cangen can0 and candump can0.
 
On system boot i am doing the following:
 
modprobe can
modprobe can-dev
modprobe can-raw
 
ip link set can0 type can bitrate 125000 triple-sampling on
ifconfig can0 up
 
however if i u

Re: [beagleboard] Re: Kernel 4.4 and SPI

[Will Rose]

My apologies, but it's some time since I worked with the BBB and my
knowledge is well
out of date.  The group is your best source of help.

Will


On 26 October 2017 at 11:34,  wrote:

> Hi C W Rose
>
> Any news on this issue, I am trying to setup the SPI0 on a BBB with no
> success.
>
> In uEnv I configured the cap-universal to enable and runned the
> config-pins to P9.17, P9.18, P9.21 and P9.22 as spi. No errors are reported
> but I see no clock or data being transfered on this pins...
>
> Any help on this?
>
> thanks
>
> Nuno F.
>
>
>
>
>
> quinta-feira, 9 de Junho de 2016 às 16:08:40 UTC+1, cwrse...@gmail.com
> escreveu:
>>
>>
>> I've been trying to port the driver for a SPI rtc, the DS3234, from the
>> 3.8 kernel
>> to a recent 4.4.  After minor changes the cape manager loads the dts file
>> sucessfully,
>> and the slot entry and /dev/rtc1 appear, but reading and writing to the
>> clock fails.
>>
>> Checking the pins and pin groups it seems that 4.4 isn't enabling the
>> pins group.
>> In 3.8 I get:
>> pin 100 (44e10990): 481a.spi (GPIO UNCLAIMED) function
>> pinctrl_spi1_pins group pinctrl_spi1_pins
>> pin 101 (44e10994): 481a.spi (GPIO UNCLAIMED) function
>> pinctrl_spi1_pins group pinctrl_spi1_pins
>> pin 102 (44e10998): 481a.spi (GPIO UNCLAIMED) function
>> pinctrl_spi1_pins group pinctrl_spi1_pins
>> pin 103 (44e1099c): 481a.spi (GPIO UNCLAIMED) function
>> pinctrl_spi1_pins group pinctrl_spi1_pins
>>
>> and in 4.4 the pins are unclaimed by both GPIO and MUX.
>>
>> The uEnv.txt line is: optargs=bone_capemgr.enable_pa
>> rtno=BB-SPIDEV0,BB-SPI1CLK
>> Loading SPIDEV1 in place of SPI1CLK produces the correct /dev/spidevN.N
>> devices,
>> but again these don't seem to be useable; the test programs in the kernel
>> sources fail.
>>
>> The only change between the 3.8 and 4.4 setups is that the HDMI overlay
>> has gone,
>> and there seems no way to disable HDMI.  There's a note in one of Robert
>> Nelson's
>> pages that setting dtb=am335x-boneblack-overlay.dtb in uEnv.txt will
>> achieve this,
>> but checking the new u-boot code that doesn't seem likely, and checking
>> the pins
>> and pingroups shows no change.
>>
>> Has anyone any ideas as to how to configure the pingroups under 4.4, or
>> how to
>> initialise the device tree for SPI?
>>
>> Thanks -  C W Rose
>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> 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/Z0vKttzCnww/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/84a31717-25cf-4637-a11c-405c37e191f9%40googlegroups.com
> 
> .
> For more options, visit 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CABDpLOY%2B%2B%3D878de20TcP5oj%2BaNq2XAAB-p2Y4i2j1TvD-B5qjg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB- DCAN1 problems using latest debian image

[Tracy Smith]

Hi John,

Both CANS are working on BBB even though Robert Nelson is implementing these on 
the P9 expansion header?

So what indicates the second CAN is working fine on BBB?  What do I look for to 
see the second CAN is working properly?

If this is the case, I just need to validate both are working and save myself 
time. We only saw the first CAN working.

Thx, Tracy

> On Nov 1, 2017, at 10:33 AM, John Dammeyer  wrote:
> 
> CAN1 and CAN2 are available when you aren’t using any other cape and I think 
> eiher HDMI or perhaps it’s the LCD interface.  It’s been a while.  There is 
> no relationship between /dev/ttyUSB0 and the CAN devices.  One requires a CAN 
> driver to function while the other is purely a serial port like a UART.
>  
> To get 5 CAN ports I chose the Freescale 9S12 series.  I think ST Micro also 
> makes an ARM compatible processor with 4 CAN ports.  There aren’t a lot 
> around.
>  
> If you want higher speed access along with message interrupts than what you 
> can get with USB FTDI based CAN connections your alternative approach will be 
> to add Microchip MCP2515s on board and use the SPI bus interface.  With 3 
> select lines to a 3:8 mux you can select one of 4 CAN devices, and wire-OR 
> the interrupts.  You just have to poll which one caused the interrupt.  I 
> believe there is a driver for the MCP2515 already in the Beagle CAN library.
>  
> Alternatively, since you are already building a cape that has CAN drivers on 
> it and you now you want at least 2 more CAN devices it may be easier to use a 
> second processor that has two CAN ports.  Write the firmware to look like an 
> SPI based MCP2515 and you can use the stock Beagle CAN driver for it.
>  
> In fact, use either the ST Micro ARM and make all the CAN ports on it appear 
> as if they were MCP2515s and that then frees up your other pins on the Beagle.
>  
> John
>  
>  
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
> Behalf Of Tracy Smith
> Sent: November-01-17 2:51 AM
> To: beagleboard@googlegroups.com
> Subject: Re: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
>  
> Hi John, 
>  
> Do you see support for both CAN0 and CAN1?  Need both and our pins for CAN1 
> are E17 and E18 in the TI pinmux tool.  Found the pad names and pins in uboot 
> pinmux for CAN0 after this post.  Haven’t found pad names associated with 
> E17/E18 yet in uboot pinmux. Will look at the kernel dts today.  
>  
> My question I guess will CAN1 be available when plugging in the CANUSB and 
> where do you see CAN1 indicated?  If supported, it will appear as 
> /dev/ttyUSB1?  Or, as a different device on the BBB?  Eventually may need as 
> many as four CAN0-3.
>  
> Thx, Tracy
> 
> On Oct 31, 2017, at 8:00 PM, John Dammeyer  wrote:
> 
> The CANUSB from Lawicel is a standard USB device that looks like a serial 
> port since it can use the FTDI driver.
>  
> On my MachineKit Debian Beagle 2.0 when I plug in the CANUSB I find I have a 
> /dev/ttyUSB0 device.
> I installed putty and connected to /dev/ttyUSB0
> In the terminal window
> V with a CR returns
> V1011
> An S5 sets 250kbps
> An O opens the port.
> t12327788 with a CR again of course sends SID=123, DLC=2, Data 0x77 0x88
> With nothing connected to the CANUSB the red LED goes on.  (or if bitrate is 
> wrong).
> A C closes the port.
> An F prints the error flags and shuts off the red led.
>  
> It’s a good idea to have auto line feed set in putty so that each received 
> message is on a new line.
> John Dammeyer
>  
>  
>  
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
> Behalf Of Tracy Smith
> Sent: October-31-17 3:42 PM
> To: BeagleBoard
> Subject: [beagleboard] Re: BBB- DCAN1 problems using latest debian image
>  
> Hi John,
> 
> I'm attempting to enable CAN support for a USB/CAN from a Lawicel. We have a 
> custom board and need to use pin D17/D18 and E17/E18 for CAN1 and CAN2.  
> 
> The pad names in u-boot/arch/arm/include/asm/arch-am33xx/mux_am33xx.h for the 
> BBB includes i2c0_sda (pin C17) and i2c0_scl (pin C16), but I don't see names 
> for i2c2_scl (pin D17) and i2c2_sda (pin D18), nor tstpt1 (pin E17) nor TP9 
> (pin E18), 
> 
> 1. Did I miss the names for these pins in u-boot?
> 
> 2. If u-boot does not support these pins, should they be added to u-boot, 
> and/or added to the kernel to support these pins?
> 
> Should these pins be pinmuxed in both uboot and the  kernel, or only in the 
> kernel dts?  Checking now to see if the kernel has support for these pins.
> 
> thx, Tracy
> 
> On Wednesday, April 8, 2015 at 8:20:29 AM UTC-5, Mark Irwin wrote:
> Hi,
>  
> I have been trying to build a proof of concept system using two beaglebone 
> black units with there DCAN1 (pins P9_24 and P9_26) and two can transcievers 
> TI SN65HVD251P.
> The can transceivers are powered from the same 5V bench supply as both of the 
> beaglebone blacks. the canh and canl pins are terminated at both ends by 120R 
> resistors 

[beagleboard] Using the PRU with a 433Mhz transmitter for RF Switch control

[jonlidgard]

Hi, I've just finished a little project to control my Mercury RC5 RF 
sockets using the Beaglebones' PRU.
Details at https://github.com/jonlidgard/rfsend

-- 
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/86900ebf-c7ae-4053-a4b9-15f8ca6220b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fwd: [beagleboard] Re: u-boot support for pins

[William Hermans]

-- Forwarded message --
From: William Hermans 
Date: Wed, Nov 1, 2017 at 9:58 AM
Subject: Re: [beagleboard] Re: u-boot support for pins
To: Tracy Smith 


https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-CAN1-
00A0.dts

Pad name is on the beaglebone schematic. Which for the purpose of using
overlays is useless.

On Wed, Nov 1, 2017 at 5:44 AM, Tracy Smith  wrote:

> Hi William,
>
> Thanks for the email and here is what I’m trying to do.
>
> The CANUSB from Lawicel is a standard USB device that looks like a serial
> port since it can use the FTDI driver.
>
>
>
> On the MachineKit Debian Beagle the CANUSB is a dev/ttyUSB0 device.
>
>
> On our *custom* BeagleBone Black, we want both CAN0 and CAN1 accessible
> USB devices.  We don’t want to have to add a P9 expansion header on the
> custom board for I2C and we have specific pins E17 and E18 we want to use
> that are designated as possible CAN1 pins on the BeagleBone Black
> schematic.
>
>
> These two pins for CAN1 are tstpt1 pin E17 and TP9 pin E18.  Just need to
> see if there is a pad name associated with these pins so I can use them for
> the pinmux file and device tree to make CAN1 available as a USB device for
> uboot and the kernel.  This is what I need.
>
>
> Looking through the pinmux files for any pad names associated with these
> two pins.
>
>
> Thx, Tracy
>
> On Oct 31, 2017, at 7:55 PM, William Hermans  wrote:
>
> SO what is it that you're trying to do ? I've read your posts, but am
> still mystified. Just sayin' . . . I've been working with this hardware for
> around 5 years now,  have written many device tree overlays for various
> hardware configurations. Including GPIO, I2C, UART, CAN, SPI, etc.
>
> I'm willing to give you some guidance, but need to understand what it is
> you're trying to do . . .
>
> I2C really isn't that hard to get working. Nor is most of it.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> 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/to
> pic/beagleboard/dE1bIym6rDg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/ms
> gid/beagleboard/CALHSORrdO87s1J7uKrJ%2BEvRKQRmKhahZBq%3DmtK1
> ktk4sChsbkA%40mail.gmail.com
> 
> .
> For more options, visit 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORoStvWHYsRVk_z_rE-pMNMvVv_MRviyEeH-FqJco1gfTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 5:44 AM, Tracy Smith  wrote:

> Hi William,
>
> Thanks for the email and here is what I’m trying to do.
>
> The CANUSB from Lawicel is a standard USB device that looks like a serial
> port since it can use the FTDI driver.
>
>
>
> On the MachineKit Debian Beagle the CANUSB is a dev/ttyUSB0 device.
>
>
> On our *custom* BeagleBone Black, we want both CAN0 and CAN1 accessible
> USB devices.  We don’t want to have to add a P9 expansion header on the
> custom board for I2C and we have specific pins E17 and E18 we want to use
> that are designated as possible CAN1 pins on the BeagleBone Black
> schematic.
>
>
> These two pins for CAN1 are tstpt1 pin E17 and TP9 pin E18.  Just need to
> see if there is a pad name associated with these pins so I can use them for
> the pinmux file and device tree to make CAN1 available as a USB device for
> uboot and the kernel.  This is what I need.
>
>
> Looking through the pinmux files for any pad names associated with these
> two pins.
>
>
> Thx, Tracy
>
> Just use the file I sent you, no worries about anything. If you NEED to
put it all into one large overlay file, you can pretty much just copy paste
what's in that file into your existing overlay. WIth some caveats of
course. You'll need to make sure the file is organized correctly.

Personally, I'd just leave the file as is, and load it standalone.

-- 
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/CALHSORrbMegBGyzk%3DhyY20mo8_TmakACzRQ68_tGOdZCwrQqqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 10:02 AM, Tracy Smith  wrote:

> Hi William,
>
> These overlays from Robert Nelson are associated with the P9 expansion
> header.  We don’t have a P9 expansion header on the custom BBB we are
> using. So we can’t use this overlay.
>
> Thx, Tracy
>

You're not making any sense. Just because you can mux pins, doesn't mean
you can also reassign pins to something they're not intended.

-- 
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/CALHSORq-n4tFUDB0JKcP80fA%3D_g7nvkcu-JQDBWYTq4S%3D5GNzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Tracy Smith]

We have no P9expansion header.  I’ve already discussed this with Robert Nelson. 
 We are using the AM3358 pins I sent previously.  Any can using the P9and this 
overlay will not work for our custom board.

Sent from my iPad

> On Nov 1, 2017, at 12:03 PM, William Hermans  wrote:
> 
> 
> 
>> On Wed, Nov 1, 2017 at 5:44 AM, Tracy Smith  wrote:
>> Hi William,
>> 
>> Thanks for the email and here is what I’m trying to do.
>> 
>> The CANUSB from Lawicel is a standard USB device that looks like a serial 
>> port since it can use the FTDI driver.
>>  
>> On the MachineKit Debian Beagle the CANUSB is a dev/ttyUSB0 device.
>> 
>> On our custom BeagleBone Black, we want both CAN0 and CAN1 accessible USB 
>> devices.  We don’t want to have to add a P9 expansion header on the custom 
>> board for I2C and we have specific pins E17 and E18 we want to use that are 
>> designated as possible CAN1 pins on the BeagleBone Black schematic. 
>> 
>> These two pins for CAN1 are tstpt1 pin E17 and TP9 pin E18.  Just need to 
>> see if there is a pad name associated with these pins so I can use them for 
>> the pinmux file and device tree to make CAN1 available as a USB device for 
>> uboot and the kernel.  This is what I need.
>> 
>> Looking through the pinmux files for any pad names associated with these two 
>> pins.  
>> 
>> Thx, Tracy
>> 
> Just use the file I sent you, no worries about anything. If you NEED to put 
> it all into one large overlay file, you can pretty much just copy paste 
> what's in that file into your existing overlay. WIth some caveats of course. 
> You'll need to make sure the file is organized correctly.  
> 
> Personally, I'd just leave the file as is, and load it standalone.

-- 
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/94E21FCA-DC0B-4F6A-8EC1-BDE937A5A1EF%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Robert Nelson]

On Wed, Nov 1, 2017 at 12:05 PM, Tracy Smith  wrote:
> We have no P9expansion header.  I’ve already discussed this with Robert
> Nelson.  We are using the AM3358 pins I sent previously.  Any can using the
> P9and this overlay will not work for our custom board.

Ah, i should just ignore you then, for some reason i keep thinking you
have a BeagleBone Black..

So route the pins you need, implement all the pimux's in u-boot and
the base dtb's..

You have no reason to use overlays at all..

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/CAOCHtYhZgWEZWB8uJbcBd5zVuXfdYhJpToVBXmkHN10c1tYbVg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 10:12 AM, William Hermans  wrote:

>
>
> On Wed, Nov 1, 2017 at 10:05 AM, Tracy Smith 
> wrote:
>
>> We have no P9expansion header.  I’ve already discussed this with Robert
>> Nelson.  We are using the AM3358 pins I sent previously.  Any can using the
>> P9and this overlay will not work for our custom board.
>>
>
> Ok, good, that doesn't make a bit of difference at all. Those pin names in
> the overlay are just variables used by the file, and initially by cape
> manager. cape manager translates those variable names into addresses when
> the overlay file is compiled.
>
> Passed that, the software that is provided could stll use the Px header
> designation for the pins, and it'll still work fine if you're using
> something like universal IO + config-pin, so long as you all have not done
> something drastically different in your layout. I do recall that some
> devices can be done using multiple pin configurations, and one in fact is
> still like that with the beaglebone design as is.
>
> Anyway, I do not remember if CAN1 has the potential to be on different
> pins or not. Out of the processor. But working with the file I sent you a
> link to all that can easily be changed.
>

Well technically, I'm not 100% positive on this. There could be hooks, etc
I'm not aware of, and I have not done this hands on personally. But so long
as you're using the same pins the bealgebone is using. It should work.

Are you, or are you not using he same pins as the beaglebone for CAN1 ?

-- 
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/CALHSORp-bX_T6k8mmy73MAkENFBQ3Boggy7-o%2BLoOCaCwja5nQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 10:17 AM, William Hermans  wrote:

>
>
> On Wed, Nov 1, 2017 at 10:12 AM, William Hermans 
> wrote:
>
>>
>>
>> On Wed, Nov 1, 2017 at 10:05 AM, Tracy Smith 
>> wrote:
>>
>>> We have no P9expansion header.  I’ve already discussed this with Robert
>>> Nelson.  We are using the AM3358 pins I sent previously.  Any can using the
>>> P9and this overlay will not work for our custom board.
>>>
>>
>> Ok, good, that doesn't make a bit of difference at all. Those pin names
>> in the overlay are just variables used by the file, and initially by cape
>> manager. cape manager translates those variable names into addresses when
>> the overlay file is compiled.
>>
>> Passed that, the software that is provided could stll use the Px header
>> designation for the pins, and it'll still work fine if you're using
>> something like universal IO + config-pin, so long as you all have not done
>> something drastically different in your layout. I do recall that some
>> devices can be done using multiple pin configurations, and one in fact is
>> still like that with the beaglebone design as is.
>>
>> Anyway, I do not remember if CAN1 has the potential to be on different
>> pins or not. Out of the processor. But working with the file I sent you a
>> link to all that can easily be changed.
>>
>
> Well technically, I'm not 100% positive on this. There could be hooks, etc
> I'm not aware of, and I have not done this hands on personally. But so long
> as you're using the same pins the bealgebone is using. It should work.
>
> Are you, or are you not using he same pins as the beaglebone for CAN1 ?
>

Another thing I did not consider is that it sounds like you could be using
a completely different board file overlay for your hardware, at which point
all bets are off.

-- 
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/CALHSORpUw6vhmD7CtNRhA1R1aL2zhkVcpXaELo%3DS%2BS%3DAL3057g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cannot get BBB to flash new OS image

[William Hermans]

Long story short.

When the eMMC has the first, and second stage bootloader installed on it.
The board will always load these from the eMMC, and then load the rest from
the sdcard when one is inserted.

The result is that one can be put into a non working state, because there
would be a MLO / uboot / kernel conflict.

There are two ways to solve this, Robert already mentioned one. The other
would be to press, and continue to hold the boot button on the board so
that it loads MLO, and uboot form teh sdcard instead. I've heard mention of
some people having difficulties with this, and instead short the boot
button. BUt I've not done that personally.

In the end, it would probably be easier to do as Robert suggests above.

-- 
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/CALHSORpxXW4kJAXA6HMfJO7fbZsU9kw3vtNqGHxz3DOd-6%3DpoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 11:01 AM, Tracy Smith  wrote:

> Ok look this custom board is based on the BeagleBone Black. For all
> intense and purposes it is the BBB. The pins for the AM3358 are the same.
> The primary difference is no P9 expansion header. What you are suggesting
> below is exactly what I’m doing and why I have the questions I do because
> your CAN support will not work on our custom BeagleBone Black.
>
> Customers will use the BBB as a reference platform and will actually have
> to do pinmuxing. When I do mention custom board, you do ignore me. But you
> shouldn’t because not all companies that use the BBB as a reference
> platform will use the P9 expansion and they will want to have CAN support
> in the kernel even without the P9 expansion header. You don’t have to use
> the P9 and the overlay being used to support CAN0 and CAN1
>
> You seem to be limiting CAN support to those using the P9 expansion
> header?  Why is that? Does it allow for four or more CANS?
>
> Really appreciate the assistance and it has been and continues to be
> extremely helpful.
>
> What limitations or constraints are causing you to have to use the P9
> expansion header for CAN?  Knowing this help justify adding an expansion
> header to the design.
>
> I need to look closer at the overlay. But knowing these constraints could
> justify adding the P9 expansion header to our custom BBB board.
>
> Thx, Tracy
>

First, I am not affiliated with beagleboard.org, cicuitco or any other
organization related directly to the beaglebone, or beagleboard products.
Or anyone who sells said products. I am just your average community member,
whose been using the beaglebone products since it's release date

Second, I never said I was ignoring anyone.

Third, you're delving into territory that myself, and most others have not
gone into. So if someone does say they're ignoring you, it could very well
be that they have not done what you're doing, and do not want to give you
incorrect information.

Lastly, be more verbose with your information. Just saying "wont work for
us" doesn't tell us what the underlying problem is, or how to help you
solve your issue.

So . .. tell us EXACTLY what you've done, and EXACTLY the errors your
experiencing. Then perhaps, if you're verbose enough, someone on this list
can help you.

-- 
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/CALHSORr5DDcmH2O5VydO9b8%3DWX4yKhtW9jm5q4PqaFnzrSc8%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Tracy Smith]

E17 and E18 we want to use that are designated as possible CAN1 pins on the 
BeagleBone Black schematic. 

Not using a different overlay, using the existing 4.14 kernel and 2017 I boot 
that Robert Nelson suggests using for the BBB. But we need to pinmux for E17 
and E18 because the TI pinmuxing tool finds no conflict with these two pins on 
our custom board. I’ll go back and check the CAN1 but prior to Roberts changes 
last week that did not use the P9 expansion header, the unit pinmux used 
different pins CAN1 I believe.  With the P9 expansion header, can’t use Roberts 
overlay because there is no P9 expansion header on our BBB board. I’ll go back 
look at the pins for CAN1 prior to then P9 overlay changes from last week by 
Robert.

This is just basic pinmuxing.  And looking for E17 and E18 pons since these are 
supposed to support CAN1 on the AM33xx.

Thx



Sent from my iPhone

> On Nov 1, 2017, at 12:21 PM, William Hermans  wrote:
> 
> 
> 
>> On Wed, Nov 1, 2017 at 10:17 AM, William Hermans  wrote:
>> 
>> 
>>> On Wed, Nov 1, 2017 at 10:12 AM, William Hermans  wrote:
>>> 
>>> 
 On Wed, Nov 1, 2017 at 10:05 AM, Tracy Smith  wrote:
 We have no P9expansion header.  I’ve already discussed this with Robert 
 Nelson.  We are using the AM3358 pins I sent previously.  Any can using 
 the P9and this overlay will not work for our custom board.
>>> 
>>> Ok, good, that doesn't make a bit of difference at all. Those pin names in 
>>> the overlay are just variables used by the file, and initially by cape 
>>> manager. cape manager translates those variable names into addresses when 
>>> the overlay file is compiled. 
>>> 
>>> Passed that, the software that is provided could stll use the Px header 
>>> designation for the pins, and it'll still work fine if you're using 
>>> something like universal IO + config-pin, so long as you all have not done 
>>> something drastically different in your layout. I do recall that some 
>>> devices can be done using multiple pin configurations, and one in fact is 
>>> still like that with the beaglebone design as is.
>>> 
>>> Anyway, I do not remember if CAN1 has the potential to be on different pins 
>>> or not. Out of the processor. But working with the file I sent you a link 
>>> to all that can easily be changed.
>> 
>> Well technically, I'm not 100% positive on this. There could be hooks, etc 
>> I'm not aware of, and I have not done this hands on personally. But so long 
>> as you're using the same pins the bealgebone is using. It should work. 
>> 
>> Are you, or are you not using he same pins as the beaglebone for CAN1 ?
> 
> Another thing I did not consider is that it sounds like you could be using a 
> completely different board file overlay for your hardware, at which point all 
> bets are off. 
> 

-- 
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/09758031-8B06-438A-B9F7-304F33BEBA98%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Robert Nelson]

On Wed, Nov 1, 2017 at 1:14 PM, Tracy Smith  wrote:
> E17 and E18 we want to use that are designated as possible CAN1 pins on the
> BeagleBone Black schematic.
>
> Not using a different overlay, using the existing 4.14 kernel and 2017 I
> boot that Robert Nelson suggests using for the BBB. But we need to pinmux
> for E17 and E18 because the TI pinmuxing tool finds no conflict with these
> two pins on our custom board. I’ll go back and check the CAN1 but prior to
> Roberts changes last week that did not use the P9 expansion header, the unit
> pinmux used different pins CAN1 I believe.  With the P9 expansion header,
> can’t use Roberts overlay because there is no P9 expansion header on our BBB
> board. I’ll go back look at the pins for CAN1 prior to then P9 overlay
> changes from last week by Robert.

What i suggested, assumed you were using a BBB.  Thus since you have a
custom board, it's all null and void..

Use TI's pinmux tool and properly route your can signals.

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/CAOCHtYjL7P4v%3DVaF9ZQ%2BV7%3DE2EvCzUZzZt1d_zY-w52XQfDu1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Tracy Smith]

These comments were a reply to Robert,!but threads are getting confused a bit 
for everyone especially for me.

Let me look at this more and see if I can find the pinmux pins I need in i-boot 
and the kernel. Even if they don’t exist in u-boot, they should in the kernel. 
Then I can do as Robert indicates, change the pinmux U-Boot file and dts.

If I go into any more detail, it’s going to take too much time and I’m already 
behind on this.  Robert understands the concerns and what I need. I simply need 
to pinmux pins E18 and E19.


> On Nov 1, 2017, at 1:09 PM, William Hermans  wrote:
> 
> 
> 
>> On Wed, Nov 1, 2017 at 11:01 AM, Tracy Smith  wrote:
>> Ok look this custom board is based on the BeagleBone Black. For all intense 
>> and purposes it is the BBB. The pins for the AM3358 are the same. The 
>> primary difference is no P9 expansion header. What you are suggesting below 
>> is exactly what I’m doing and why I have the questions I do because your CAN 
>> support will not work on our custom BeagleBone Black.
>> 
>> Customers will use the BBB as a reference platform and will actually have to 
>> do pinmuxing. When I do mention custom board, you do ignore me. But you 
>> shouldn’t because not all companies that use the BBB as a reference platform 
>> will use the P9 expansion and they will want to have CAN support in the 
>> kernel even without the P9 expansion header. You don’t have to use the P9 
>> and the overlay being used to support CAN0 and CAN1
>> 
>> You seem to be limiting CAN support to those using the P9 expansion header?  
>> Why is that? Does it allow for four or more CANS?  
>> 
>> Really appreciate the assistance and it has been and continues to be 
>> extremely helpful. 
>> 
>> What limitations or constraints are causing you to have to use the P9 
>> expansion header for CAN?  Knowing this help justify adding an expansion 
>> header to the design. 
>> 
>> I need to look closer at the overlay. But knowing these constraints could 
>> justify adding the P9 expansion header to our custom BBB board.
>> 
>> Thx, Tracy
> 
> First, I am not affiliated with beagleboard.org, cicuitco or any other 
> organization related directly to the beaglebone, or beagleboard products. Or 
> anyone who sells said products. I am just your average community member, 
> whose been using the beaglebone products since it's release date
> 
> Second, I never said I was ignoring anyone.
> 
> Third, you're delving into territory that myself, and most others have not 
> gone into. So if someone does say they're ignoring you, it could very well be 
> that they have not done what you're doing, and do not want to give you 
> incorrect information.
> 
> Lastly, be more verbose with your information. Just saying "wont work for us" 
> doesn't tell us what the underlying problem is, or how to help you solve your 
> issue.
> 
> So . .. tell us EXACTLY what you've done, and EXACTLY the errors your 
> experiencing. Then perhaps, if you're verbose enough, someone on this list 
> can help you.
> 

-- 
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/DE388E17-0772-445D-92F5-2B6F87DF0734%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Tracy Smith]

The signals are all routed just need to pinmux E18 and E19 which are the same 
for the BBB.

Sent from my iPhone

> On Nov 1, 2017, at 1:19 PM, Robert Nelson  wrote:
> 
>> On Wed, Nov 1, 2017 at 1:14 PM, Tracy Smith  wrote:
>> E17 and E18 we want to use that are designated as possible CAN1 pins on the
>> BeagleBone Black schematic.
>> 
>> Not using a different overlay, using the existing 4.14 kernel and 2017 I
>> boot that Robert Nelson suggests using for the BBB. But we need to pinmux
>> for E17 and E18 because the TI pinmuxing tool finds no conflict with these
>> two pins on our custom board. I’ll go back and check the CAN1 but prior to
>> Roberts changes last week that did not use the P9 expansion header, the unit
>> pinmux used different pins CAN1 I believe.  With the P9 expansion header,
>> can’t use Roberts overlay because there is no P9 expansion header on our BBB
>> board. I’ll go back look at the pins for CAN1 prior to then P9 overlay
>> changes from last week by Robert.
> 
> What i suggested, assumed you were using a BBB.  Thus since you have a
> custom board, it's all null and void..
> 
> Use TI's pinmux tool and properly route your can signals.
> 
> 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/4780F9F7-D160-4C49-9715-4AA47E65FFF7%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Tracy Smith]

The need to use E18 and E19 For CAN1 comes from the TI pinmux tool.

Sent from my iPhone

> On Nov 1, 2017, at 1:19 PM, Robert Nelson  wrote:
> 
>> On Wed, Nov 1, 2017 at 1:14 PM, Tracy Smith  wrote:
>> E17 and E18 we want to use that are designated as possible CAN1 pins on the
>> BeagleBone Black schematic.
>> 
>> Not using a different overlay, using the existing 4.14 kernel and 2017 I
>> boot that Robert Nelson suggests using for the BBB. But we need to pinmux
>> for E17 and E18 because the TI pinmuxing tool finds no conflict with these
>> two pins on our custom board. I’ll go back and check the CAN1 but prior to
>> Roberts changes last week that did not use the P9 expansion header, the unit
>> pinmux used different pins CAN1 I believe.  With the P9 expansion header,
>> can’t use Roberts overlay because there is no P9 expansion header on our BBB
>> board. I’ll go back look at the pins for CAN1 prior to then P9 overlay
>> changes from last week by Robert.
> 
> What i suggested, assumed you were using a BBB.  Thus since you have a
> custom board, it's all null and void..
> 
> Use TI's pinmux tool and properly route your can signals.
> 
> 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/57260CA6-814D-4F21-8D3A-43A47490B236%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 11:19 AM, Robert Nelson 
wrote:

> On Wed, Nov 1, 2017 at 1:14 PM, Tracy Smith  wrote:
> > E17 and E18 we want to use that are designated as possible CAN1 pins on
> the
> > BeagleBone Black schematic.
> >
> > Not using a different overlay, using the existing 4.14 kernel and 2017 I
> > boot that Robert Nelson suggests using for the BBB. But we need to pinmux
> > for E17 and E18 because the TI pinmuxing tool finds no conflict with
> these
> > two pins on our custom board. I’ll go back and check the CAN1 but prior
> to
> > Roberts changes last week that did not use the P9 expansion header, the
> unit
> > pinmux used different pins CAN1 I believe.  With the P9 expansion header,
> > can’t use Roberts overlay because there is no P9 expansion header on our
> BBB
> > board. I’ll go back look at the pins for CAN1 prior to then P9 overlay
> > changes from last week by Robert.
>
> What i suggested, assumed you were using a BBB.  Thus since you have a
> custom board, it's all null and void..
>
> Use TI's pinmux tool and properly route your can signals.
>

What Robert said, but in addition, it might be handy if you let us know
what hardware( everything ) you're using to help us, help you spot
potential hardware conflicts. I've worked on a project that did in fact use
one CAN interface a couple or three years ago. It works, but I only used
one bus. Not two. Additionally, I was using an older kernel, so I've not
the same on a current kernel. At some point I think I did test a semi
recent kernel, just to get the interface up and running, but I did not test
the C code I wrote a while back on that interface.

So how do you know it's not working. Just saying it doesn't work does not
give us the steps you taken to get where you are. or the error messages
you're getting, that could help us troubleshoot your issue for you. Nor
does it tell us if the driver for a given CAN interface is even loaded. You
see where I'm going ? There are many places for this process to go wrong.

-- 
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/CALHSORpKGh0pYiYL5AjJuDUXqLHTwunYGS_uCaYHXqwkz4xBMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Robert Nelson]

On Wed, Nov 1, 2017 at 1:24 PM, Tracy Smith  wrote:
> The need to use E18 and E19 For CAN1 comes from the TI pinmux tool.

Umm, on the ZCZ package used on the BBB

E18: dcan1_tx
E19: not available for can0/can1...

Want to try again?

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/CAOCHtYgjjHrTSNZxkUtBexWDR_em4P3O-aMSO8pn4N5W_efpbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Robert Nelson]

On Wed, Nov 1, 2017 at 1:28 PM, Robert Nelson  wrote:
> On Wed, Nov 1, 2017 at 1:24 PM, Tracy Smith  wrote:
>> The need to use E18 and E19 For CAN1 comes from the TI pinmux tool.
>
> Umm, on the ZCZ package used on the BBB
>
> E18: dcan1_tx
> E19: not available for can0/can1...
>
> Want to try again?

Ps, random "ti pinmux questions" should go to:

https://e2e.ti.com/

Specially when you have random hardware..

This is the Beagle Community. We don't get paid for support..

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/CAOCHtYj%3DdW1uW0gtFZForZWiHxjK4a%2Bv8eG7KAdBNnSkYgA%2BcA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 11:28 AM, Robert Nelson 
wrote:

> On Wed, Nov 1, 2017 at 1:24 PM, Tracy Smith  wrote:
> > The need to use E18 and E19 For CAN1 comes from the TI pinmux tool.
>
> Umm, on the ZCZ package used on the BBB
>
> E18: dcan1_tx
> E19: not available for can0/can1...
>
> Want to try again?
>

Yeah tx, and rx are staggered two pins apart in the pdf file I have here.
what are the Px header assignments, or gpioxx_yy nomenclature assignments ?

-- 
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/CALHSORr1%2BCMqyyCfh0p9-iXgviPGR49qbpjNKBiw5enGKARDGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[Tracy Smith]

Agreed. And the pins are E18 and E17 for DCAN1_RX/TX on the BBB schematic. 
These are the pins the TI pinmux tools says use. So, trying to use these two 
pins for CAN1 because we don’t have the P9 expansion header. 

That is just the first step in this CAN bring up process for a custom BBB board 
that doesn’t have a P9 expansion header.  So I agree.

I still have a question for Robert, why is the P9 expansion header being used 
for then CAN on the most recent release instead of the AM335X CAN0 and CAN1 
RX/TX pins D17/D18 and E17/E18?

Thx, Tracy

> On Nov 1, 2017, at 1:28 PM, William Hermans  wrote:
> 
> 
> 
>> On Wed, Nov 1, 2017 at 11:19 AM, Robert Nelson  
>> wrote:
>> On Wed, Nov 1, 2017 at 1:14 PM, Tracy Smith  wrote:
>> > E17 and E18 we want to use that are designated as possible CAN1 pins on the
>> > BeagleBone Black schematic.
>> >
>> > Not using a different overlay, using the existing 4.14 kernel and 2017 I
>> > boot that Robert Nelson suggests using for the BBB. But we need to pinmux
>> > for E17 and E18 because the TI pinmuxing tool finds no conflict with these
>> > two pins on our custom board. I’ll go back and check the CAN1 but prior to
>> > Roberts changes last week that did not use the P9 expansion header, the 
>> > unit
>> > pinmux used different pins CAN1 I believe.  With the P9 expansion header,
>> > can’t use Roberts overlay because there is no P9 expansion header on our 
>> > BBB
>> > board. I’ll go back look at the pins for CAN1 prior to then P9 overlay
>> > changes from last week by Robert.
>> 
>> What i suggested, assumed you were using a BBB.  Thus since you have a
>> custom board, it's all null and void..
>> 
>> Use TI's pinmux tool and properly route your can signals.
> 
> What Robert said, but in addition, it might be handy if you let us know what 
> hardware( everything ) you're using to help us, help you spot potential 
> hardware conflicts. I've worked on a project that did in fact use one CAN 
> interface a couple or three years ago. It works, but I only used one bus. Not 
> two. Additionally, I was using an older kernel, so I've not the same on a 
> current kernel. At some point I think I did test a semi recent kernel, just 
> to get the interface up and running, but I did not test the C code I wrote a 
> while back on that interface.
> 
> So how do you know it's not working. Just saying it doesn't work does not 
> give us the steps you taken to get where you are. or the error messages 
> you're getting, that could help us troubleshoot your issue for you. Nor does 
> it tell us if the driver for a given CAN interface is even loaded. You see 
> where I'm going ? There are many places for this process to go wrong.
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> 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/dE1bIym6rDg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/CALHSORpKGh0pYiYL5AjJuDUXqLHTwunYGS_uCaYHXqwkz4xBMg%40mail.gmail.com.
> For more options, visit 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8D713A70-D95F-455B-8CF4-74ABDA41866B%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cannot get BBB to flash new OS image

[geert . schrooten]

Thanks Robert & William, 

I also prefer erasing eMMC before soldering a switch to replace user boot 
button.

Thanks for clarifying that eMMC is always the first and SD never overrides 
eMMC as I wrongfully assumed.


Op woensdag 1 november 2017 18:31:32 UTC+1 schreef William Hermans:

> Long story short.
>
> When the eMMC has the first, and second stage bootloader installed on it. 
> The board will always load these from the eMMC, and then load the rest from 
> the sdcard when one is inserted.
>
> The result is that one can be put into a non working state, because there 
> would be a MLO / uboot / kernel conflict.
>
> There are two ways to solve this, Robert already mentioned one. The other 
> would be to press, and continue to hold the boot button on the board so 
> that it loads MLO, and uboot form teh sdcard instead. I've heard mention of 
> some people having difficulties with this, and instead short the boot 
> button. BUt I've not done that personally.
>
> In the end, it would probably be easier to do as Robert suggests above.
>

-- 
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/dd34e68f-3d5e-4e00-ba33-07eba634ab80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cannot get BBB to flash new OS image

[Robert Nelson]

On Wed, Nov 1, 2017 at 3:15 PM,   wrote:
> Thanks Robert & William,
>
> I also prefer erasing eMMC before soldering a switch to replace user boot
> button.

No reason to even solder, worse case you stick a wire bettween two
pins on the expansion header (the push button is routed to a pin on
the expansion header)..

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/CAOCHtYjADHfykAt0tUN9-QtyFGv0aXQV1wEj-zpXr9M5ScFN3A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] FCC Conducted Emissions Failure

[maxmike]

We need to do something similar and I'm trying to find a way to reduce the eth0 
/ wlan0 speed to 10 Mb, but it looks as though ethtool will not work in Debian 
on the Beaglebone Black. Is this a shortcoming of drivers or the hardware?

-- 
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/2ff986a6-6a3c-494b-a5b6-d1ab8467585c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] FCC Conducted Emissions Failure

[David Accadia]

Never tried reducing  the eth0 speed.

We where able to reduce the USB speed by making code changes to the linux 
kernel. (that was fun)   But in the end soldering the USB connectors and 
providing a better contact of the Ethernet port to the chassis fixed most 
issues. 

Also the beagle bone green was a lot quieter than the black. 

On Thursday, 2 November 2017 15:06:57 UTC+11, maxmike wrote:
>
> We need to do something similar and I'm trying to find a way to reduce the 
> eth0 / wlan0 speed to 10 Mb, but it looks as though ethtool will not work 
> in Debian on the Beaglebone Black. Is this a shortcoming of drivers or the 
> hardware?

-- 
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/68ca555f-61ff-471a-83fc-b742d35aa788%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.