[beagleboard] Re: MCP2515 SPI CAN

2016-12-23 Thread rickyc8888
Hi Travis,

Thanks for the reply. 

The problem was with the driver, the MCP251x drivers that came 
with 4.4.30-ti-r64 kernel are not compatible. I got a new driver and now I 
can bring the CAN bus online. But other problems now came up. Whenever I 
tried to send with cansend, I got a TXWAR/EP error and the link went 
down(it didn't say it went down but it's not responsive to cansend commands 
afterwards). And if I tried to receive using candump, when the other device 
send a frame, I got RXWAR/EP errors. I've tried sending with the Canbus 
connected or disconnected it's still the same. Do you have any idea what 
might be causing this problem?

Thanks,

Ricky


On Thursday, December 22, 2016 at 7:15:34 AM UTC+8, Travis Lytle wrote:
>
> On the console do: lsmod
>
> You should see something like:
>
> can_raw 7618  3
> can31379  1 can_raw
> mcp2515 8341  0
> mcp251x12797  0
> c_can_platform  7581  0
> c_can  12220  1 c_can_platform
> can_dev14358  3 c_can,mcp2515,mcp251x
>
> If mcp251x is there the driver is loaded.  You can do an ifconfig -a to 
> show if active too.
>
> To bring up the interface you can check here: 
> http://elinux.org/Bringing_CAN_interface_up
>
> Travis
>
> On Tuesday, November 29, 2016 at 6:20:59 AM UTC-5, ricky...@gmail.com 
> wrote:
>>
>> Hi,
>>
>> I am trying to get an MCP2515 running on SPI1.0. I can successfully load 
>> the .dtbo,  found the device under /sys/bus/spi/devices/spi1.0, but 
>> couldn't seem to get the CAN bus running. Does anyone know if the driver is 
>> already compiled into the kernel? Or if I need to do something to activate 
>> it?
>>
>> Thanks for the help!
>>
>> Regards,
>>
>> Ricky Chang
>>
>

-- 
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/0371907a-1d27-4c9b-af57-31ab9a4f099a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Boot stopped at "A start job is running for dev-mmcb...\xc2\xa0.device"

2016-12-07 Thread rickyc8888
On Wednesday, December 7, 2016 at 10:57:00 PM UTC+8, RobertCNelson wrote:
> On Wed, Dec 7, 2016 at 8:49 AM,   wrote:
> > Hi,
> >
> > I built the kernel "4.8.12-bone2" using Mr Nelson's source and scripts and
> > downloaded it to the Sdcard together with the file system
> > "debian-8.6-bare-armhf-2016-09-17", following the instructions on
> > "https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot;.
> > When the system booted it got stuck at "A start job is running for
> > dev-mmcb...\xc2\xa0.device", and after the timeout the system seemed to go
> > in a loop and cannot finish booting. Could someone please tell me what this
> > message means and what I might have done wrong?
> 
> Probably the wrong mmc name in /etc/fstab
> 
> Regards,
> 
> -- 
> Robert Nelson
> https://rcn-ee.com/

I copied the fstab line from the instruction webpage, the device was 
/dev/mmcblk0p1. Is this the correct device? If not what should I put 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/425c09d8-827d-4b86-a1e5-ab705e951637%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Boot stopped at "A start job is running for dev-mmcb...\xc2\xa0.device"

2016-12-07 Thread rickyc8888
Hi,

I built the kernel "4.8.12-bone2" using Mr Nelson's source and scripts and 
downloaded it to the Sdcard together with the file system 
"debian-8.6-bare-armhf-2016-09-17", following the instructions on
"https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot;.
 
When the system booted it got stuck at "A start job is running for 
dev-mmcb...\xc2\xa0.device", and after the timeout the system seemed to go 
in a loop and cannot finish booting. Could someone please tell me what this 
message means and what I might have done wrong?

Thank you very much.

Ricky

-- 
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/4e8f3e12-25fe-4ccb-b7bf-5e5f7d211078%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Startup Scripts

2016-12-01 Thread rickyc8888
Hi Peter,

Thanks for the template!


On Wednesday, November 30, 2016 at 12:36:37 PM UTC+8, Peter Lawler wrote:
>
>
>
> On 28/11/16 22:43, ricky...@gmail.com  wrote: 
> > Hi, 
> > 
> > I am trying to run some simple startup shell scripts when the system 
> boots. 
>
> Hi, 
> If you're after a simple 'single shot' startup, you can use this as a 
> template. I wrote this one because the flashing LEDs seemed to ... 
> distract ... the pets at night... 
>
>
> https://github.com/PeteLawler/starnix-recipes/blob/master/etc/systemd/system/bb-leds-off.service
>  
>
> Instructions on how to install it are in the comments. 
>
> I believe there are ways to have your old style SysV init scripts work 
> with systemd, but I'd suggest for future proofing sake you may be better 
> off just going with the flow. 
>
> Cheers, 
>
> Pete. 
>

-- 
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/fff0c445-0c38-48ea-a08f-58cc8a10f548%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] MCP2515 SPI CAN

2016-11-29 Thread rickyc8888
Hi,

I am trying to get an MCP2515 running on SPI1.0. I can successfully load 
the .dtbo,  found the device under /sys/bus/spi/devices/spi1.0, but 
couldn't seem to get the CAN bus running. Does anyone know if the driver is 
already compiled into the kernel? Or if I need to do something to activate 
it?

Thanks for the help!

Regards,

Ricky Chang

-- 
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/e1b40cbc-8557-4cea-a3bb-974b754dcae9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Re: Startup Scripts

2016-11-29 Thread rickyc8888
Hi Stephane, 

Yes crontab will work. I've also found that rc.local did run only for some 
reasons it couldn't execute my scripts, I'd look into that further. Thanks 
for the help!


On Tuesday, November 29, 2016 at 2:15:34 AM UTC+8, Stephane Charette wrote:
>
> I am trying to run some simple startup shell scripts when the system boots.
>>
>
> One thing I tend to use is the @reboot keyword in cron.  For example:
>
> *cat /etc/cron.d/startup_scripts*
> MAILTO=""
> PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>
> @reboot root /home/stephane/scripts/check_for_upgrade.sh
> @reboot root /home/stephane/scripts/startup_commands.sh
>
> Stéphane
>
>

-- 
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/4f0807b1-7a88-4ab5-b48f-ee5cf70abac4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] Startup Scripts

2016-11-28 Thread rickyc8888
Hi,

I am trying to run some simple startup shell scripts when the system boots. 
It used to be an easy task by putting the script in /etc/init.d. But now 
with systemd I have no idea how this can be done. I've tried to put them in 
etc/rc.local, etc/init.d, but the scripts don't seem to run. I've seen some 
tutorials to put the scripts in a service with systemctl, which I haven't 
yet tried. But there must be some other ways?

Kernel version:
Linux beaglebone 4.4.34-ti-r69 #1 SMP Wed Nov 23 20:01:14 UTC 2016 armv7l 
GNU/Linux


Thanks for the help!

Best Regards,

Ricky Chang

-- 
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/3d4f4130-1bb6-4ec9-8744-f444ad731a95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[beagleboard] dtc syntax error

2016-11-26 Thread rickyc8888
Dear all,

I am using the latest version of Debian on the Black:
"Linux beaglebone 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l 
GNU/Linux"

My dtc version is  "DTC 1.4.1-g1e75ebc9"

I am using the "misc cape" board from WaveShare. They have provided several 
.dts files for the overlays. One of them is for enabling the I2C and is 
called " DVK531-I2C1-01-00A0.dts". The file can be compiled with no error 
and the .dtbo was copied to the /lib/firmware directory. I enable this 
overlay by editing the /boot/uEnv.txt file adding the 
line:"cape_enable=bone_capemgr.enable_partno=DVK531-I2C1-01". But during 
boot up it shows the error message : "[3.554491] bone_capemgr 
bone_capemgr: loader: failed to load slot-4 DVK531-I2C1-01:00A0 (prio 0)".

Thinking I might have done something incorrectly, I then tried to load the 
BB-I2C1-00A0.dtbo from the repo of bb.org-overlays and it can be loaded 
correctly. I then examined the contents of the two .dts and found that 
there are not much difference except two lines of include files: "#include 
" and 
"#include ". I therefore added the two lines 
to the DVK531 .dts and try to compile but then I get the error : "Error: 
DVK531-I2C1-01-00A0.dts:13.1-9 syntax error
FATAL ERROR: Unable to parse input tree". I tried that on the I2C dts from 
the repo and get the same error. Can someone please tell me what was wrong 
and why the dtbo wouldn't load?

The .dts from WaveShare:

/*
 * Copyright (C) 2013 CircuitCo
 *
 * Virtual cape for I2C1 on connector pins P9.17 P9.18
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License version 2 as
 * published by the Free Software Foundation.
 */
/dts-v1/;
/plugin/;

/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";

/* identification */
part-number = "DVK551-I2C1-01";
version = "00A0";

/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P9.18", /* i2c1_sda */
"P9.17", /* i2c1_scl */
/* the hardware ip uses */
"i2c1";

fragment@0 {
target = <_pinmux>;
__overlay__ {
bb_i2c1_pins: pinmux_bb_i2c1_pins {
pinctrl-single,pins = <
0x158 0x72 /* spi0_d1.i2c1_sda, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
0x15c 0x72 /* spi0_cs0.i2c1_scl, SLEWCTRL_SLOW | INPUT_PULLUP | MODE2 */
>;
};
};
};

fragment@1 {
target = <>; /* i2c1 is numbered correctly */
__overlay__ {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <_i2c1_pins>;

/* this is the configuration part */
clock-frequency = <10>; 

#address-cells = <1>;
#size-cells = <0>;
/* 
cape_eeprom0: cape_eeprom0@54 {
compatible = "at,24c256";
reg = <0x54>;
};*/
};
};
};


Thank you for your help!


Ricky






-- 
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/3fb461e9-d232-4aa4-8c9b-be19402065bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Where is the MLO and u-boot.img

2014-12-11 Thread rickyc8888
Hi Robert. Thanks for your info.

When you make partitions using sfdisk, where is the info written? Would the 
info overwrite the memory area of MLO or boot.img?

I have a problem when using this image. At boot I always get this message :

[   10.379089] libphy: PHY 4a101000.mdio:01 not found
[   10.384157] net eth0: phy 4a101000.mdio:01 not found on slave 1


whether or not I have a cable plugged in. But if I have the ethernet cable 
plugged in, the system booted up relatively quickly with the log in prompt, 
otherwise it will take about 100 seconds before the log in prompt appeared. 
And if I plug in a cable after booting up, it will take a long while before 
the cable is detected and even longer before an IP is assigned by the DHCP 
server. I tried changing the settings in dhclient.conf without any 
effect. What can I do to fix these problems? In the stock kernel that came 
with the board(Rev C), the same message appears but only after the log in 
prompt, and it doesn't block the other operations.

I also read from the forum that the cape manager is gone in this kernel 
version(so soon!), so does that mean I have to put the capes I need in the 
am335x-boneblack.dts file and load everything at boot time? And how can I 
know what capes are loaded now without the  /sys/devices/bone_capemgr.*/
slots?

Thanks again for your help!








On Tuesday, December 9, 2014 12:13:22 AM UTC+8, RobertCNelson wrote:

 On Sat, Dec 6, 2014 at 1:24 AM,  ricky...@gmail.com javascript: 
 wrote: 
  Yes, a lot of things on Linux looks like voodoo magic, and so many 
  mysterious codes lying everywhere :) 
  
  That said, can you point me to the place where I can learn how that was 
  done, and the complete boot mechanism of the BBB? I am trying to learn 
 the 
  boot process(among other things) of the BBB but there are just so much 
 info 
  lying around, some are outdated and some are conflicting. Also does that 
  mean I can no longer access or see these two files? Is there a place 
 where I 
  could download the source for the image? 

 Page 4934 (mmc raw mode) 

 http://www.ti.com/lit/ug/spruh73k/spruh73k.pdf 

  I read your instructions at: 
  
  
 https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSD/SDcard
  
  
  and saw that you have only made one partition on the SDcard with both 
 the 
  kernel and file system, and before you format the card you've dd'ed both 
 the 
  MLO and u-boot.img to it. Is this how that was done? And I thought that 
 was 
  a mistake, silly me :) 

 Do you you notice how we create a 1Mb hole on the front of the drive 
 via sfdisk?  After that point, the order of dd'ing the bootloader or 
 mkfs.ext4 the partition doesn't really matter.. 

  I have learned a lot from what you have posted on the web, thank you for 
  your work and I look forward to seeing more Products from you. Too bad 
  there is not a centralized location where we can learn all these for the 
  BBB. 

 Well there is this mailing list. 

 Regards, 

 -- 
 Robert Nelson 
 http://www.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.
For more options, visit https://groups.google.com/d/optout.


Re: [beagleboard] Where is the MLO and u-boot.img

2014-12-08 Thread rickyc8888
Yes, a lot of things on Linux looks like voodoo magic, and so many 
mysterious codes lying everywhere :)

That said, can you point me to the place where I can learn how that was 
done, and the complete boot mechanism of the BBB? I am trying to learn the 
boot process(among other things) of the BBB but there are just so much info 
lying around, some are outdated and some are conflicting. Also does that 
mean I can no longer access or see these two files? Is there a place where 
I could download the source for the image?

I read your instructions at:

https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSD/SDcard
 

and saw that you have only made one partition on the SDcard with both the 
kernel and file system, and before you format the card you've dd'ed both 
the MLO and u-boot.img to it. Is this how that was done? And I thought that 
was a mistake, silly me :)

I have learned a lot from what you have posted on the web, thank you for 
your work and I look forward to seeing more Products from you. Too bad 
there is not a centralized location where we can learn all these for the 
BBB.


Best Regards,

Ricky Chang


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