[beagleboard] Re: fsck fails to start on writable partition at boot/startup

[mindentropy]

Hi Dave,

 I too have a similar problem but not have worked directly on the problem. 
This is in medical devices where the instruments power is pulled off 
abruptly without shutting down. Also the wear and tear of the eMMC and 
detection of errors etc. The problems become much more serious and I cannot 
boot the instrument if the complete system is not working at 100%.  Also 
the problem of run time monitoring to detect any problems in the system and 
alert the user or shutdown the system.

 I have been thinking of evaluating datalight filesystem solutions for this 
problem. If your problem is mission critical I am interested in knowing 
your solutions.

Thanks,
Gautam.

On Friday, December 8, 2017 at 7:31:03 AM UTC+5:30, Dave Barndt wrote:
>
> Hi Gautam,
>
> The filesystem is ext4; the O/S is debian 8/jessie, the image is the 
> "officially released" BBB image from last spring 
> (bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz). To date we have not 
> modified any of the kernel startup scripts, save for setting a serial port 
> baud rate in /etc/rc.local.
>
> I wish I could tell you the power event that caused this to happen - it 
> was a unit in field test and folks there have been pretty much just killing 
> the power to it at various times. We had discussed putting the circuitry in 
> to allow a more graceful shutdown, but are only able to get to it now. That 
> said, power has been shutdown abruptly (power simply removed) literally 
> thousands of times on dozens of BBBs, but we've only seen a couple 
> corruptions. (Separately, we've also seen "bad block" corruptions 
> occasionally, presumably from wear (many, many writes over time).)
>
> Dave
>

-- 
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/e2f8c3a8-6201-4fed-a09d-69d1c8a31a8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Latest (bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz) node-red-node-beaglebone not working on BBW

[wkulecz]

I'd like to give it a try, but I'm kind of lost as to exactly how.  

There is no .node-red directory in the /home/debian directory, does that 
mean bone-debian was setup with a global node-red install?  There is a 
/root/.node-red directory but its node_modules directory is empty.

In /usr/local/lib/node_modules there is:
root@bbWhite:/usr/local/lib/node_modules# ls -l
total 28
drwxr-sr-x 5 debian debian 4096 Jun  6  2017 async
drwxr-sr-x 8 debian debian 4096 Apr  7  2017 bonescript
drwxr-sr-x 9 debian debian 4096 Aug 16 15:45 node-red
drwxr-sr-x 4 debian debian 4096 Aug 16 15:54 node-red-node-beaglebone
drwxr-sr-x 4 debian debian 4096 Aug 16 15:55 node-red-node-mongodb
drwxr-sr-x 4 debian debian 4096 Jun  6  2017 sensortag
drwxr-sr-x 5 nobody ssh4096 Oct 10 07:04 winston


in /usr/local/lib/node_modules/node-red-node-beaglebone/package.json there 
is:

 "dependencies": {
"octalbonescript": 
"https://github.com/rcn-ee/octalbonescript/tarball/uboot-overlays;
  },
 

Do I change it to read: 
https://github.com/rcn-ee/octalbonescript/tree/uboot-overlays 

 ?

Then what do I do?

The README.md in the github link says:
After adding this line, you should run npm install command from that 
project directory to install OBS. Another method is to directly cd to 
project directory and run npm install octalbonescript command. 

Is the project directory the one with the package.json file?  Maybe I'm 
dense, but I've found bone-debian to be rather fragile in the past.

If you tell me exactly what  to do I'll do it and I'll get back to you as 
to if it worked or not.



On Thursday, December 7, 2017 at 12:04:49 PM UTC-6, RobertCNelson wrote:
>
> On Thu, Dec 7, 2017 at 11:55 AM,   wrote: 
> > I've installed the latest, 
> bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz 
> > to and SD card and have been playing with it on my three Beaglebones 
> > Original Beaglebone "white" Rev A6, Beaglebone Black Rev A5A, and 
> Beaglebone 
> > Green. 
> > 
> > I've not changed anything in /boot/uEnv.txt, I've just moved the SD card 
> > among the three systems and booted.  All seem to work fine so far except 
> ... 
> > 
> > Connecting to the node-red server at beaglebone:1880 I see the 
> > node-red-node-beaglebone nodes in the palette on the BBB & BBG, but on 
> the 
> > BBW they are not there.  They show up in the palette manager but can't 
> be 
> > enabled. 
> > 
> > Any hardware  reason for this?  Is there a way I can correct it? 
> > 
> > I didn't see any comments in /boot/uEnv.txt that looked relevant to the 
> > issue, but its a lot different from a couple of years ago when I last 
> did 
> > anything with the Beaglebones, best initial bootup experience yet for 
> the 
> > Beaglebones except for this issue.  I don't think the BBW is even being 
> sold 
> > anymore, but hopefully there would be some support for what is still out 
> > there,  Mine has a broken "power" switch and can't be rebooted after a 
> > shutdown without removing 5V power and re-powering, but otherwise seems 
> OK. 
>
> Sounds like a bug in the octalbonescript package: 
>
> Here is our local fork with a u-boot overlay change.. 
>
> https://github.com/rcn-ee/octalbonescript/tree/uboot-overlays 
>
> 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/24c9512e-eda0-48c7-852d-d0d5dd6a4a2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: fsck fails to start on writable partition at boot/startup

[Dave Barndt]

Hi Gautam,

The filesystem is ext4; the O/S is debian 8/jessie, the image is the 
"officially released" BBB image from last spring 
(bone-debian-8.7-iot-armhf-2017-03-19-4gb.img.xz). To date we have not 
modified any of the kernel startup scripts, save for setting a serial port 
baud rate in /etc/rc.local.

I wish I could tell you the power event that caused this to happen - it was 
a unit in field test and folks there have been pretty much just killing the 
power to it at various times. We had discussed putting the circuitry in to 
allow a more graceful shutdown, but are only able to get to it now. That 
said, power has been shutdown abruptly (power simply removed) literally 
thousands of times on dozens of BBBs, but we've only seen a couple 
corruptions. (Separately, we've also seen "bad block" corruptions 
occasionally, presumably from wear (many, many writes over time).)

Dave

-- 
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/ca201ed2-162c-41ce-9593-e1bc73f23fc0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Vibration Rating

[Robert Nelson]

On Thu, Dec 7, 2017 at 12:41 PM,   wrote:
> Has anyone done vibration testing on the X15?

You should run those tests and share it with the group..

Ps, you haven't asked about temp, high altitude, and radiation.

and remember, it's a "community" board, if you "really" need all those
details, you really should pick up the the TI AM57xx EVM, and ti.com
will support you! ;)

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

[beagleboard] Vibration Rating

[rjdyk]

Has anyone done vibration testing on the X15?

-- 
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/76280d93-918b-4271-adf5-8d3fc4abdd5d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BeagleBoard X15 Weight

[rjdyk]

Update: The board is 105g

On Tuesday, December 5, 2017 at 4:55:14 PM UTC-5, rj...@umich.edu wrote:
>
> Does anyone know the weight of the X15 board?
> It's not available on any of the forums I've checked and when I contacted 
> a supplier they didn't have any information on the weight.
>
> Thanks
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/dbdade88-e1b0-467d-be9f-d330251c879c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Latest (bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz) node-red-node-beaglebone not working on BBW

[Robert Nelson]

On Thu, Dec 7, 2017 at 11:55 AM,   wrote:
> I've installed the latest, bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz
> to and SD card and have been playing with it on my three Beaglebones
> Original Beaglebone "white" Rev A6, Beaglebone Black Rev A5A, and Beaglebone
> Green.
>
> I've not changed anything in /boot/uEnv.txt, I've just moved the SD card
> among the three systems and booted.  All seem to work fine so far except ...
>
> Connecting to the node-red server at beaglebone:1880 I see the
> node-red-node-beaglebone nodes in the palette on the BBB & BBG, but on the
> BBW they are not there.  They show up in the palette manager but can't be
> enabled.
>
> Any hardware  reason for this?  Is there a way I can correct it?
>
> I didn't see any comments in /boot/uEnv.txt that looked relevant to the
> issue, but its a lot different from a couple of years ago when I last did
> anything with the Beaglebones, best initial bootup experience yet for the
> Beaglebones except for this issue.  I don't think the BBW is even being sold
> anymore, but hopefully there would be some support for what is still out
> there,  Mine has a broken "power" switch and can't be rebooted after a
> shutdown without removing 5V power and re-powering, but otherwise seems OK.

Sounds like a bug in the octalbonescript package:

Here is our local fork with a u-boot overlay change..

https://github.com/rcn-ee/octalbonescript/tree/uboot-overlays

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

[beagleboard] Latest (bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz) node-red-node-beaglebone not working on BBW

[wkulecz]

I've installed the latest, bone-debian-9.2-iot-armhf-2017-10-10-4gb.img.xz 
to and SD card and have been playing with it on my three Beaglebones
Original Beaglebone "white" Rev A6, Beaglebone Black Rev A5A, and 
Beaglebone Green.

I've not changed anything in /boot/uEnv.txt, I've just moved the SD card 
among the three systems and booted.  All seem to work fine so far except ...

Connecting to the node-red server at beaglebone:1880 I see the 
node-red-node-beaglebone nodes in the palette on the BBB & BBG, but on the 
BBW they are not there.  They show up in the palette manager but can't be 
enabled.

Any hardware  reason for this?  Is there a way I can correct it?

I didn't see any comments in /boot/uEnv.txt that looked relevant to the 
issue, but its a lot different from a couple of years ago when I last did 
anything with the Beaglebones, best initial bootup experience yet for the 
Beaglebones except for this issue.  I don't think the BBW is even being 
sold anymore, but hopefully there would be some support for what is still 
out there,  Mine has a broken "power" switch and can't be rebooted after a 
shutdown without removing 5V power and re-powering, but otherwise seems OK.


-- 
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/b3dd069d-27ee-4fce-ac9c-c703619a30de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to locate package linux-headers-4.4.91-ti-r133

[RoSchmi]

Yes, it was my mistake.
Thanks for the help.

>
>
> -- 
> 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/b4686890-1235-4967-bcbb-1f275fe74f26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Beaglebone Blue compass not working in DMP mode

[D Sellers]

Perfect.  Thanks.

On Thursday, December 7, 2017 at 12:34:05 AM UTC-5, sharma.r...@gmail.com 
wrote:
>
> Hi, Did you check this?-
> https://github.com/StrawsonDesign/Robotics_Cape_Installer/issues/53
>
>
> On Sunday, November 26, 2017 at 8:02:18 PM UTC+5:30, D Sellers wrote:
>>
>> Same issue here.  Raw readings seem to be correct, but the DMP mode of 
>> the API  the heading (raw and filtered) just drift.
>>
>> On Saturday, October 14, 2017 at 12:29:44 PM UTC-4, Pierce Nichols wrote:
>>>
>>> Hi all, 
>>>
>>> I already posted this to the Beaglebone group, but I noticed there's 
>>> lots of traffic here about the Beaglebone Blue as well, so I'm cross 
>>> posting in hopes of finding an answer. 
>>>
>>> I'm having trouble getting the compass heading to work correctly in 
>>> DMP mode on my Beaglebone Blue. I'm running with the default 
>>> roboticscape overlay. 
>>>
>>> -- I calibrated the magnetometer and gyroscope as directed here: 
>>> http://www.strawsondesign.com/#!manual-imu 
>>>
>>> -- I ran the rc_test_imu program and confirmed that the magnetometer 
>>> is working correctly. 
>>>
>>> -- I ran rc_test_dmp -m -c -t. When I did this, I noticed that the raw 
>>> compass was stuck near either 0, +180, or -180 degrees, jumping 
>>> between those points as I rotated the Blue around the Z axis. When 
>>> left still, the filtered compass always converged to the value of the 
>>> raw. I also tested to make sure the pitch and roll angles were sane, 
>>> and they were. 
>>>
>>> I tried rotating it around the X and Y axes as well as using the -o 
>>> option to switch the IMU orientation. This did not materially change 
>>> the compass behavior. Trying it without the -m or -c switches produced 
>>> no change in behavior. 
>>>
>>> It behaves as if the magnetometer was simply not being turned on in 
>>> DMP mode. I double-checked the source code of rc_test_dmp and 
>>> recompiled it to see if the bug was there, and got the same results. 
>>>
>>> Any suggestions for what I can try next? My application is such I can 
>>> get away with processing the raw values to get a compass heading, but 
>>> it would be nice to be able to use the sensor fusion. I filed a github 
>>> issue as well. 
>>>
>>> -- 
>>> Pierce Nichols 
>>> Principal Engineer 
>>> Logos Electromechanical, LLC 
>>>
>>

-- 
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/8efa7265-ee72-4dc7-a128-a8edbfcde1cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBGW - wlcore crashes during boot with USB audio card installed

[lofnakumari]

Hi,

Did you solve the issue.

Thanks,

On Thursday, July 21, 2016 at 12:33:25 AM UTC+5:30, Mike Erdahl wrote:
>
> Hi,
>
> I'm working on a project that requires audio input/ output, so using a 
> C-Media chipset based solution from Sabrent.
>
> With the latest BB.org kernel/ filesystem (Kernel 4.4.9, Debian 8.4), 
> wlcore driver crashes during kernel boot if my USB audio card is installed. 
>  Booting without the card installed, then installing after the kernel seems 
> to always work fine (WiFi throughput is normal, USB audio in/ out works as 
> expected).
>
> Occasionally I can poweroff, then back on, without removing USB audio 
> card, and wlcore is happy.  I would say this occurs < 10%.
>
> Below are snippets of my kernel logs in good vs bad case:
>
> debian@beaglebone:~$ uname -a 
> 
>
> Linux beaglebone 4.4.9-ti-r25 #1 SMP Thu May 5 23:08:13 UTC 2016 armv7l 
> GNU/Linux
>
> GOOD:
>
> [ 21.553728] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
>
> [ 21.727062] wlcore: loaded
> [ 22.635026] wlcore: PHY firmware version: Rev 8.2.0.0.233
> [ 22.982650] wlcore: firmware booted (Rev 8.9.0.1.55)
> [ 23.321899] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [ 24.678734] Bluetooth: Core ver 2.21
> [ 24.682608] NET: Registered protocol family 31
> [ 24.682627] Bluetooth: HCI device and connection manager initialized
> [ 24.682664] Bluetooth: HCI socket layer initialized
> [ 24.682681] Bluetooth: L2CAP socket layer initialized
> [ 24.682778] Bluetooth: SCO socket layer initialized
> [ 24.721944] Bluetooth: HCI UART driver ver 2.3
> [ 24.721973] Bluetooth: HCI UART protocol H4 registered
> [ 24.721981] Bluetooth: HCI UART protocol BCSP registered
> [ 24.721988] Bluetooth: HCI UART protocol LL registered
> [ 24.721995] Bluetooth: HCI UART protocol ATH3K registered
> [ 24.722002] Bluetooth: HCI UART protocol Three-wire (H5) registered
> [ 24.724095] Bluetooth: HCI UART protocol BCM registered
> [ 24.724115] Bluetooth: HCI UART protocol QCA registered
> [ 25.093927] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
> [ 25.093951] Bluetooth: BNEP filters: protocol multicast
> [ 25.093985] Bluetooth: BNEP socket layer initialized
>
> FAIL:
>
> [   22.313743] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
>
> [   22.480016] wlcore: loaded
>
> [   23.447478] wlcore: PHY firmware version: Rev 8.2.0.0.233
>
> [   23.856026] wlcore: firmware booted (Rev 8.9.0.1.55)
>
> [   24.185915] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
>
> [   25.025939] wlcore: ERROR ELP wakeup timeout!
>
> [   25.030401] [ cut here ]
>
> [   25.030673] WARNING: CPU: 0 PID: 451 at 
> drivers/net/wireless/ti/wlcore/main.c:797 
> wl12xx_queue_recovery_work.part.8+0x46/0x48 [wlcore]()
>
> [   25.030683] Modules linked in: arc4 wl18xx wlcore mac80211 pruss_intc 
> cfg80211 rfkill snd_soc_evm snd_soc_wilink8_bt pru_rproc omap_sham pruss 
> omap_aes_driver snd_usb_audio snd_hwdep snd_usbmidi_lib snd_rawmidi 
> snd_seq_device cm109 omap_rng rng_core snd_soc_davinci_mcasp snd_soc_edma 
> snd_soc_omap snd_soc_core usb_f_acm snd_pcm_dmaengine u_serial 
> usb_f_rndis g_multi usb_f_mass_storage u_ether libcomposite snd_pcm 
> wlcore_sdio snd_timer snd soundcore evdev uio_pdrv_genirq uio
>
> [   25.030817] CPU: 0 PID: 451 Comm: wpa_supplicant Not tainted 
> 4.4.9-ti-r25 #1
>
> [   25.030824] Hardware name: Generic AM33XX (Flattened Device Tree)
>
> [   25.030864] [] (unwind_backtrace) from [] 
> (show_stack+0x11/0x14)
>
> [   25.030891] [] (show_stack) from [] 
> (dump_stack+0x73/0x80)
>
> [   25.030920] [] (dump_stack) from [] 
> (warn_slowpath_common+0x6b/0x94)
>
> [   25.030936] [] (warn_slowpath_common) from [] 
> (warn_slowpath_null+0x17/0x1c)
>
> [   25.031043] [] (warn_slowpath_null) from [] 
> (wl12xx_queue_recovery_work.part.8+0x46/0x48 [wlcore])
>
> [   25.031221] [] (wl12xx_queue_recovery_work.part.8 [wlcore]) 
> from [] (wl12xx_queue_recovery_work+0x12/0x14 [wlcore])
>
> [   25.031365] [] (wl12xx_queue_recovery_work [wlcore]) from 
> [] (wl1271_ps_elp_wakeup+0x192/0x198 [wlcore])
>
> [   25.031507] [] (wl1271_ps_elp_wakeup [wlcore]) from 
> [] (wl1271_op_add_interface+0x78/0x774 [wlcore])
>
> [   25.032132] [] (wl1271_op_add_interface [wlcore]) from 
> [] (drv_add_interface+0x38/0x118 [mac80211])
>
> [   25.032592] [] (drv_add_interface [mac80211]) from 
> [] (ieee80211_do_open+0x2f4/0x668 [mac80211])
>
> [   25.032905] [] (ieee80211_do_open [mac80211]) from 
> [] (ieee80211_start_p2p_device+0x3e/0x44 [mac80211])
>
> [   25.033590] [] (ieee80211_start_p2p_device [mac80211]) from 
> [] (nl80211_start_p2p_device+0x50/0x120 [cfg80211])
>
> [   25.033868] [] (nl80211_start_p2p_device [cfg80211]) from 
> [] (genl_rcv_msg+0x1b5/0x2bc)
>
> [   25.033887] [] (genl_rcv_msg) from [] 
> (netlink_rcv_skb+0x75/0x84)
>
> [   25.033899] [] (netlink_rcv_skb) from [] 
> (genl_rcv+0x21/0x30)
>
> [   

[beagleboard] Re: Not able to ping through Beaglebone Black on laptop

[wnpw1997]

temporary close you window firewall or antivirus ( sometime u need to close 
firewall on your anti virus software like  McAfee LiveSafe)

On Monday, February 3, 2014 at 4:35:08 PM UTC+8, Vikas arora wrote:
>
> I have beaglebone black and I am trying to access internet over USB from 
> my laptop. I am using putty to ssh into beaglebone But the problem is that 
> when I try to ping my laptop using:* PING 192.168.7.1*. It fails. 
> Following is the message that shows up on the screen:
>
> PING 192.168.7.1 (192.168.7.1) 56(84) bytes of data.
>
> After this nothing happen. It stucks here and after aborting the process 
> using ctrl+C, it show up this message:
>
> 69 packets transmitted, 0 received, 100% packet loss, time 68019ms
>
> How should I ping back to my laptop. It is running windows 8 while 
> beaglebone is running angstrom. Please help...
>

-- 
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/e7574fa1-e825-4710-a84e-1fc89bc0ee31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SPI - SD card

[nimish . jain]

HI Alberto,
I am doing the same task on *B*eaglebone green wireless running on ubuntu 
16.04 image but failed to enable the spi. I was initailly doing that on 
debian and that's working fine , but need to do on unbuntu.
 Other things are working on ubuntu , like I enabled uart and i2c.
I even posted here and on stackoverflow .
If you can provide any help then it would be helpful to me .

Thanks,
Nimish  

On Tuesday, January 14, 2014 at 5:20:19 PM UTC+5:30, Alberto Potenza wrote:
>
> Dear all,
> I have a question about SPI and SD card. I've already seen a couple of 
> posts with a similar question but the answer is not fully clear to me.
> I have a beaglebone black.
> I am booting from SD card.
> I am using the GPMC bus.
>
> I would like to use the SPI1 lines to connect another SD card.
> I would like to know if there is a sort of driver which allows me to see 
> the second SD card as a common external memory.
>
> I already wrote a C program to talk with the SD card via SPI1 (simple 
> commands such as CMD0, CMD8 etc..etc) but I think (hope) that there is a 
> driver to have the SD card seen as an external memory.
>
> Thanks for your help.
>
> Regards.
>
> Alberto.
>

-- 
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/402ecae0-bea5-43aa-8ac6-bc1e27f58e65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to locate package linux-headers-4.4.91-ti-r133

[Robert Nelson]

On Thu, Dec 7, 2017 at 9:25 AM, RoSchmi  wrote:
> So... I got it!
> downloaded the headers from
> http://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/linux-headers-4.4.91-ti-r133_1stretch_armhf.deb
> installed the headers with
> sudo dpkg -i linux-headers-4.4.91-ti-r133_1stretch_armhf.deb
>
> sudo apt-get update did not work because the URLs
> #deb [arch=armhf] http://repos.rcn-ee.com/debian/ stretch main
> #deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ stretch main
> were outcommented in my /etc/apt/sources.list
> I'm not sure if it was outcommented from the download or if I did it myself

The first one is enabled by default on the uploaded images.

Otherwise, debootstrap can't pull in the kernel.. ;)

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

Re: [beagleboard] Unable to locate package linux-headers-4.4.91-ti-r133

[RoSchmi]

So... I got it!
downloaded the headers from
http://repos.rcn-ee.net/debian/pool/main/l/linux-upstream/linux-headers-4.4.91-ti-r133_1stretch_armhf.deb
installed the headers with
sudo dpkg -i linux-headers-4.4.91-ti-r133_1stretch_armhf.deb

sudo apt-get update did not work because the URLs
#deb [arch=armhf] http://repos.rcn-ee.com/debian/ stretch main
#deb-src [arch=armhf] http://repos.rcn-ee.com/debian/ stretch main
were outcommented in my /etc/apt/sources.list
I'm not sure if it was outcommented from the download or if I did it myself 
accidently
Thanks

>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4994b323-2f97-4136-ac88-ed27523cc25a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Unable to locate package linux-headers-4.4.91-ti-r133

[RoSchmi]

Thanks for your answer, but it didn't help.
I tried:
sudo apt update
sudo apt-get update
sudo apt-get upgrade

but still
The command: apt-cache search linux-headers 
shows only headers with the version: linux-headers-4.9.0-4
and
sudo apt install linux-headers-$(uname -r)
results in
Unable to locate package linux-headers-4.4.91-ti-r133 





Am Donnerstag, 7. Dezember 2017 02:13:32 UTC+1 schrieb RobertCNelson:

> On Wed, Dec 6, 2017 at 6:59 PM, RoSchmi  > wrote: 
> > Hi, 
> > I'm trying to foolow Derek Molloy's tutorial "Writing a Linux Kernel 
> Module" 
> > http://derekmolloy.ie/writing-a-linux-kernel-module-part-1-introduction/ 
> > According to the blog it is needed to install the linux-header files. 
> > I'm using debian 4.4.91-ti-r133. 
> > On the command: sudo apt-get install linux-headers-4.4.91-ti-r133 
> > I get the error message: 
> > Unable to locate package linux-headers-4.4.91-ti-r133 
> > The command: apt-cache search linux-headers 
> > shows only headers with the version: linux-headers-4.9.0-4 
> > Can anybody please give some advice how to proceed? 
> > Thanks in advance 
>
> Refresh your apt cache: 
>
> sudo apt update 
>
> then you can run: 
>
> sudo apt install linux-headers-`uname -r` 
>
> 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/cb02946c-b3e0-4790-93bb-82d09a5810c3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Stretch pwm difference

[Johan Henselmans]

I am trying to get p8_45 and p8_49 to run PWM2A and PWM2B signals. I am 
running 4.14.3-ti-r14 with 
enable_uboot_overlays=1
enable_uboot_cape_universal=1
disable_uboot_overlay_video=1


According to the SRM that is possible, When I do an export to 
echo 1 > /sys/class/pwm/pwmchip6/export
, I only get /sys/clas/pwm/pwm-6:1
With 
echo 1 > /sys/class/pwm/pwmchip3/export
, I get /sys/clas/pwm/pwm-3:0 and /sys/clas/pwm/pwm-3:1. 

Why is that? Should I do anything else?



On Friday, September 29, 2017 at 11:18:26 PM UTC+2, RobertCNelson wrote:
>
> On Fri, Sep 29, 2017 at 3:19 PM, William Hermans  > wrote: 
> > Robert, 
> > 
> > Ok I think I see what you mean now( fully ). With universal IO and the 
> > generic startup script enabled. I did see something similar to what you 
> were 
> > saying. However, if one disables both universal IO, and the generic 
> startup 
> > script, then writes their own custom overlay for all 3 of the PWM chips 
> that 
> > are dual channel. You get a structure like this: 
> > 
> > root@wgd:~# ls /sys/class/pwm/pwmchip*/ |grep pwm 
> > /sys/class/pwm/pwmchip0/: 
> > npwm 
> > /sys/class/pwm/pwmchip2/: 
> > npwm 
> > /sys/class/pwm/pwmchip4/: 
> > npwm 
> > 
> > This is consistent across multiple images on the same board. In this 
> case a 
> > 4G beaglebone black( rev C ). But at the same time as you can see from 
> the 
> > output above. The two PWM channels for each PWM chip are not enabled. In 
> > Jessie, these are populated automatically at boot. How can I make that 
> > happen in stretch ? I could write a script, but I think that is done 
> > automatically through cape_manager in Jessie ? 
>
> What's happening in v4.4.x, the pwm's are now in the correct order, if 
> you look at v4.4.x: (pwm came before ecap) 
>
> #4.4.88-ti-r129 
> pwmchip0 -> 
> ../../devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip0 
> pwmchip2 -> 
> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip2 
> pwmchip4 -> 
> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip4 
> pwmchip6 -> 
> ../../devices/platform/ocp/4830.epwmss/48300100.ecap/pwm/pwmchip6 
> pwmchip7 -> 
> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip7 
>
> In v4.9.x: (since ecap are considered pwm's) they are now in the order 
> of the register address: 
>
> pwmchip0 -> 
> ../../devices/platform/ocp/4830.epwmss/48300100.ecap/pwm/pwmchip0 
> pwmchip1 -> 
> ../../devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1 
> pwmchip3 -> 
> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip3 
> pwmchip5 -> 
> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip5 
> pwmchip6 -> 
> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip6 
>
> In your case, you only want the dual mode "pwm", (48300200.pwm, 
> 48302200.pwm, 48304200.pwm), you shouldn't blindly enable the 
> "pwmchip0,2,4" as they are dynamic.  You should grep the symlink 
> first. 
>
> Ps, watch out for v4.11.x too: 
>
> #v4.4.x/v4.9.x 
> /sys/class/pwm/pwmchip1/: 
> drwxr-xr-x 3 root root0 Sep 29 21:06 pwm0 
> drwxr-xr-x 3 root root0 Sep 29 21:06 pwm1 
>
> #v4.11.x+ 
>
> /sys/class/pwm/pwmchip1/: 
> drwxrwxr-x 3 root pwm 0 Sep 29 21:10 pwm-1:0 
> drwxrwxr-x 3 root pwm 0 Sep 29 21:10 pwm-1:1 
>
> (ps, this last change is good thing, notice that udev correctly added 
> the "root:pwm" rule.. ;) ) 
>
> 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/f352bae1-24f1-4172-9136-259ef870ee63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.