Re: [beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Tarmo Kuuse]

On 12.07.19 07:50, Megha Bhirade wrote:
I tried by connecting LAN cable from router to board Ethernet port, but 
for ping command i am getting :


acufore@acufore-H110M-S2:~$ ping beaglebone.local
ping: unknown host beaglebone.local

acufore@acufore-H110M-S2:~$ avahi-resolve -n beaglebone.local
Failed to resolve host name 'beaglebone.local': Timeout reached


Your computer can't reach the beaglebone. I'm out of simple advice. 
Assuming your LAN setup is OK, it's rather suspicious that neither USB 
nor Ethernet gives you access to it.


The USB connection also creates a virtual serial port through which a 
serial console is available (which is nearly is as good as an ssh 
connection). On my machine it appears as device /dev/ttyACM0. I use it 
by installing the package "screen" and running:


$ screen /dev/ttyACM0 115200

Pressing Enter causes a login prompt to appear, where you can log in 
using the default credentials (debian/debian, IIRC). If this doesn't 
work, I would try re-flashing the board. Follow the instructions here:

https://beagleboard.org/Support/BoneScript/updates/

Note that you're debugging it blindly which makes everything more 
difficult. If you attach a USB-Serial adapter to the debug header, 
you'll get the bootloader debug output and a serial console. If you 
don't have one at hand, search aliexpress for "FTDI USB to TTL" and get 
the first thing that pops up.


--
Kind regards
Tarmo

--
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/e717d54a-4a91-c975-d7ce-794f66b00521%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Megha Bhirade]

I checked in to network settings, it is showing 2 connections..

one is system network connection-which is connected and providing ip 
address.
second connection for BBB - it is showing disconnected..

why it is showing disconnected?? anything i am missing here?

-- 
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/b5cc9e5a-2db0-4317-afe9-5f56c2f1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Megha Bhirade]

Hi,

I tried by connecting LAN cable from router to board Ethernet port, but for 
ping command i am getting :

acufore@acufore-H110M-S2:~$ ping beaglebone.local
ping: unknown host beaglebone.local

acufore@acufore-H110M-S2:~$ avahi-resolve -n beaglebone.local
Failed to resolve host name 'beaglebone.local': Timeout reached

please help me resolve..

-- 
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/d1cec1c5-d88c-4cf2-a5b7-5c203b3a854f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Megha Bhirade]

Hii,
 yes , you are true i am going to login to the board using ssh command and 
trying with one simple hello world program.
once that is fine means i am  going to load new Debian image in to 
board.after that same steps as earlier

 

-- 
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/8c60d5fc-5bb9-4e4b-b630-f4cfb35fc465%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Cloud9 disconnect and restart bug

[Austin Carter]

Was working in a Beagle Bone Blue workshop trying to do some apt installs.
Hosted WiFi off of PC as a pass through to bridge Blue to network.

Commands run
sudo apt update
sudo apt install -y lsb-release

While commands were running in terminal, copied and pasted a python 3 file
into an existing .py file. Cloud 9 crashed for a few min before restarting.
Python file did not save. Tried to paste again cause a Cloud 9 disconnect
for a few seconds before it recovered.

Was told to report some of the journalctl.


Jul 11 15:03:45 beaglebone dnsmasq-dhcp[4267]: DHCPREQUEST(usb0)
192.168.7.1 50:65:83:68:c0:48
Jul 11 15:03:45 beaglebone dnsmasq-dhcp[4267]: DHCPACK(usb0) 192.168.7.1
50:65:83:68:c0:48 Austin-PC
Jul 11 15:04:38 beaglebone wpa_supplicant[417]: wlan0:
CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-50 noise= txrate=52000
Jul 11 15:04:41 beaglebone dnsmasq-dhcp[4267]: DHCPREQUEST(usb0)
192.168.7.1 50:65:83:68:c0:48
Jul 11 15:04:41 beaglebone dnsmasq-dhcp[4267]: DHCPACK(usb0) 192.168.7.1
50:65:83:68:c0:48 Austin-PC
Jul 11 15:05:36 beaglebone dnsmasq-dhcp[4267]: DHCPREQUEST(usb0)
192.168.7.1 50:65:83:68:c0:48
Jul 11 15:05:36 beaglebone dnsmasq-dhcp[4267]: DHCPACK(usb0) 192.168.7.1
50:65:83:68:c0:48 Austin-PC
Jul 11 15:06:32 beaglebone dnsmasq-dhcp[4267]: DHCPREQUEST(usb0)
192.168.7.1 50:65:83:68:c0:48
Jul 11 15:06:32 beaglebone dnsmasq-dhcp[4267]: DHCPACK(usb0) 192.168.7.1
50:65:83:68:c0:48 Austin-PC
Jul 11 15:06:52 beaglebone cloud9ide[4307]: cache
/opt/cloud9/build/standalonebuild/build/standalone/modules/ace/mode/python.js
Jul 11 15:06:52 beaglebone cloud9ide[4307]: cache hit
/opt/cloud9/build/standalonebuild/build/standalone/modules/ace/mode/python.js
Jul 11 15:06:52 beaglebone cloud9ide[4307]: cache
/opt/cloud9/build/standalonebuild/build/standalone/modules/ace/snippets/text.js
Jul 11 15:06:52 beaglebone cloud9ide[4307]: cache hit
/opt/cloud9/build/standalonebuild/build/standalone/modules/ace/snippets/text.js
Jul 11 15:06:53 beaglebone cloud9ide[4307]: cache
/opt/cloud9/build/standalonebuild/build/standalone/modules/ace/snippets/python.js
Jul 11 15:06:53 beaglebone cloud9ide[4307]: cache hit
/opt/cloud9/build/standalonebuild/build/standalone/modules/ace/snippets/python.js
Jul 11 15:06:53 beaglebone cloud9ide[4307]: VFS Exception in function
'readfile':
Jul 11 15:06:53 beaglebone cloud9ide[4307]:  TypeError
[ERR_INVALID_CALLBACK]: Callback must be a function
Jul 11 15:06:53 beaglebone cloud9ide[4307]: at makeCallback
(fs.js:137:11)
Jul 11 15:06:53 beaglebone cloud9ide[4307]: at Object.close
(fs.js:395:20)
Jul 11 15:06:53 beaglebone cloud9ide[4307]: at
/opt/cloud9/build/standalonebuild/node_modules/vfs-local/localfs.js:543:20
Jul 11 15:06:53 beaglebone cloud9ide[4307]: at
/opt/cloud9/build/standalonebuild/node_modules/vfs-local/localfs.js:365:21
Jul 11 15:06:53 beaglebone cloud9ide[4307]: at FSReqWrap.oncomplete
(fs.js:155:5)
Jul 11 15:06:53 beaglebone cloud9ide[4307]: Scheduling process exit
Jul 11 15:06:55 beaglebone cloud9ide[4307]: Exiting after uncaught
exception in 'readfile':
Jul 11 15:06:55 beaglebone cloud9ide[4307]:  TypeError
[ERR_INVALID_CALLBACK]: Callback must be a function
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at makeCallback
(fs.js:137:11)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at Object.close
(fs.js:395:20)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at
/opt/cloud9/build/standalonebuild/node_modules/vfs-local/localfs.js:543:20
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at
/opt/cloud9/build/standalonebuild/node_modules/vfs-local/localfs.js:365:21
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at FSReqWrap.oncomplete
(fs.js:155:5)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: Error: EDISCONNECT: Agent
disconnected
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at Parent.Agent.disconnect
(/opt/cloud9/build/standalonebuild/node_modules/smith/smith.js:414:16)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at Parent.disconnect
(/opt/cloud9/build/standalonebuild/node_modules/vfs-child/parent.js:64:39)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at Transport.emit
(events.js:189:13)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at Socket.onDisconnect
(/opt/cloud9/build/standalonebuild/node_modules/smith/smith.js:126:14)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at Socket.emit
(events.js:194:15)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at endReadableNT
(_stream_readable.js:1103:12)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: at process._tickCallback
(internal/process/next_tick.js:63:19)
Jul 11 15:06:55 beaglebone cloud9ide[4307]: destroying because of error
undefined
Jul 11 15:07:14 beaglebone cloud9ide[4307]: User saving
/BeagleBone/tamulinkcon.py
Jul 11 15:07:14 beaglebone cloud9ide[4307]: Successfully saved
/BeagleBone/tamulinkcon.py

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

[beagleboard] Need recommendations for BB Blue camera for smart dog door product

[Steve Meinschein]

I'm looking for recommendations for an inexpensive USB "spy camera" (day 
and IR night-vision capability) hardware that is BB Blue compatible -- and 
includes a microphone and speaker for two-way communications.

My current smart dog door design uses a mini speaker 

 
& microphone connected to the BB Blue USB port -- and an Arducam mini camera 

 
connected to the BB Blue SPI and I2C interfaces. 

So, in essence, I'm trying to simplify my smart dog door design and reduce 
cost by getting two birds (video & audio) for the price of one (BB Blue USB 
port).   

-- 
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/25004d38-a30b-4462-9e35-ea4f1a3b4fd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Tarmo Kuuse]

On 11.07.19 15:48, Megha Bhirade wrote:

Thanks for reply. for second  option -connecting LAN cable to BBB .

i connected LAN cable from router with DHCP server, where i can see 
:beaglebone.local..


can u explain the basic connection :
i followed like ,
1.connected board(BBB) to PC using USB cable
2. router with DHCP server
3. one LAN cable from the router to board ethernet port


Well, there's nothing to "see" as such. Hopefully the BBB is now 
reachable via your local network. Your next steps depend on what are you 
planning to do with it, and this only you know. I assumed you wanted to 
log into it via ssh and hack away.


You can perform some basic network diagnostics using your PC (it must be 
connected to the same LAN, obviously).


To check if name resolution works (returns the IPv4 or IPv6 address of 
the BBB):

$ avahi-resolve -n beaglebone.local

To check if the BBB is reachable from your computer
$ ping beaglebone.local

--
Kind regards
Tarmo

--
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/ce8c9bd6-2452-02f4-c18e-607785ebe181%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Megha Bhirade]

Hii,

Thanks for reply. for second  option -connecting LAN cable to BBB .

i connected LAN cable from router with DHCP server, where i can see 
:beaglebone.local..

can u explain the basic connection :
i followed like , 
1.connected board(BBB) to PC using USB cable 
2. router with DHCP server
3. one LAN cable from the router to board ethernet port

-- 
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/5f53fcd3-2169-4cca-aa89-125ae7c8bf9a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Tarmo Kuuse]

On Thursday, 11 July 2019 14:34:48 UTC+3, Megha Bhirade wrote:
>
>
>
>> Hi tarmo,
>>
>i am using a PC with Linux Ubuntu and version is 16.04LTS (64-bit) 
> Ubuntu as a native operating system.
>
> As u suggested  i used *tail -n 100 /var/log/syslog *in to command 
> line(terminal). i got much data not able to understand and i stored the 
> data in to one file please check it i am attaching the same data..
>
> one more thing u told about the local LAN can u explain it once??
>
 
OK. I have no experience using Ubuntu 16.04LTS, but I'd assume it contains 
all necessary drivers for BBB out of the box.

The 2 minute log snippet does not contain anything which I would recognize 
as a BBB being plugged into USB. Perhaps you did it earlier?

Anyway, your computer appears to try getting an IP from the BBB-s DHCP 
server, but there's no response. No idea why. Usually my computer gets a 
192.168.6.1 or 192.168.7.1 (actually both, on two separate virtual 
interfaces) address from the BBB (as described in 
https://beagleboard.org/static/beaglebone/latest/README.htm).

The BBB has an Ethernet port. Connect it to your LAN (a router with a DHCP 
server and other standard services is required, obviously). Then you can 
connect to it from the same LAN. It should respond to name 
"beaglebone.local" by default. If this name doesn't resolve then install 
avahi packages in Ubuntu. Then use your favourite ssh client to connect. 
Not much more to explain there.

--
Kind regards,
Tarmo

-- 
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/a282ace5-5e32-4ec7-bd5c-dbe57921cf06%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Unable to SSH into BeagleBone enhanced

[Djing]

I'm posting here as there for the BBE as there doesn't seem to be a Forum 
for it and BBB probably the closest thing to it.

So I'm trying to SSH into the BBE and I keep Getting the Connection Timed 
Out error. The BBE is flashed with Debian 9.4 and when I use my BBB with 
the same flash and USB cable I have no issues connecting via SSH. 
I am also able to connect serially into the BBE and the IP address I am 
using is definitely correct (should be 192.168.7.2 but i did double check 
this via ifconfig). I have also had no luck after I've disabled the ufw 
firewall, created a static IP address. 
Might also be noteworthy that I am unable to connect to the IP address over 
my browser. But this also works fine when trying it with the BBB. 

Any other ideas as to what could be the issue? 

-- 
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/e07b1301-238e-4be5-a147-fc18e849b289%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Need Help with Camera Port on BeagleBoard-xM RevC

[hhami . 2040]

hello 
i need adv7403.c and adv7403_regs.h ,adv7403linux driver
you can send me??
thanks

On Thursday, May 17, 2012 at 10:08:26 PM UTC-7, shravan kulkarni wrote:
>
> Hi,
>  I have a Beagleboard-xM RevC to which DVSDK-4.01 is ported and runs 
> Linux Angstrom on it. To this board i have to interface a custom made board 
> built using ADV7403. ADV7403 interact with the Beagleboard via the camera 
> connector port which is there on the beagleboard.
>
> Input to ADV7403 is a RGB signal and the output of ADV7403 is 4:2:2 10-bit 
> YCbCr. now the beagleboard has to process this YCbCr and store into a 
> digital format.
>
> ADV7403 is programmed via I2C and im able to configure ADV7403 to my 
> requirement using i2cget and i2cset commands from the terminal. Now i have 
> the YCbCr signals at the 
> camera port of the Beagleboard but Beagleboard is not able to detect these 
> signals. when i check the devices detected for video it lists out 
> /dev/video1 and /dev/video2. but these are listed even when i dont connect 
> my ADV7403. This leads to the conclusion that ADV7403 might not be getting 
> detected by the Beagleboard.
>
> 1. How do i make the beagleboard to detect my adv7403 which is connected 
> to its camera connector.
>
> 2. As i can configure the ADV7403 to process RGB signal and give out 
> YCbCr, can i make the beagleboard to process this YCbCr by using any 
> application or by using any command. If the answer is yes then how to do 
> it..??
>
> if i have missed out any information which is needed please mention it.
>
>
> thanking you,
> Shravan Kulkarni
>

-- 
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/06df9572-a3e2-420f-a217-09af0a5f4689%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Need Help with video device node creation

[hhami . 2040]

hello 
I am trying to read and write data on ADV7403 decoder IC on my designed 
board. I have been through almost all questions regarding I2C bus with 
ADV7403 but my problem still remains there.
You can send me  source code of ADV7403.c and adv7403_regs.h

On Friday, September 7, 2012 at 2:38:10 AM UTC-7, shravan kulkarni wrote:
>
> Hi,
>
> I have a custom board built with ADV7403 video decoder/encoder 
> ic which will be interfaced to Beagleboard-xM Rev.C. Im trying to write 
> linux device driver for ADV7403 to work with RGB input signals and output 
> of 10-bit 4:2:2 YCbCr. i have added the support of i2c into my device 
> drivers. now i have to integrate V4L2 into my device driver.
>
> I have pasted the code below on what is done so far on V4L2.
>
>
> v4l2_i2c_subdev_init(&state->subdev, client, &adv7403_ops);   // for 
> V4L2_subdev initialization
>
> //--code to create the device 
> node-//
>
> struct video_device *vfd;
>
> vfd = video_device_alloc();
> if(vfd == NULL)
> {
> return -ENOMEM;
> printk("failed to create /dev/video node\n");
> vfd->release = video_device_release;
> }
>
> err = video_register_device(vfd, VFL_TYPE_GRABBER, -1);
> if(err) {
> video_device_release(vfd);
> printk("failed to register the device node /dev/videoX\n");
> return err;
> }
>
> //code to create the device 
> node-//
>
> v4l2_i2c_subdev_init() was included alone there was no error during 
> compilation and run time 
>
> then vfd = video_device_alloc(); was included and here also there was no 
> error
>
> but on the next part... i.e., 
>
> err = video_register_device(vfd, VFL_TYPE_GRABBER, -1);
>
> i had a run time error which is pasted below..
>
>
> //error--//
>
> root@beagleboard-dvsdk:/lib/modules/2.6.32/kernel/drivers/media/video# 
> insmod ad
> v7403.ko 
> [ 82.966735] adv7403 2-0021: chip found @ 0x42 (OMAP I2C adapter)
> [ 82.990478] adv7403: Detected ADV7403 @ 25
> [ 82.994598] Memory is allocated 
> [ 82.997863] [ cut here ]
> [ 83.021789] WARNING: at drivers/media/video/v4l2-dev.c:421 
> __video_register_device+0x44/0x3ec()
> [ 83.045166] Modules linked in: adv7403(+) sdmak lpm_omap3530 
>  dsplinkk cmemk ipv6 rtc_twl rtc_core
> [ 83.068572] [] (unwind_backtrace+0x0/0xdc) from [] 
> (warn_slowpath_common+0x48/0x60)
> [ 83.086395] [] (warn_slowpath_common+0x48/0x60) from 
> [] (__video_register_device+0x44/0x3ec)
> [ 83.097015] [] (__video_register_device+0x44/0x3ec) from 
> [] (adv7403_probe+0x178/0x2ec [adv7403])
> [ 83.107940] [] (adv7403_probe+0x178/0x2ec [adv7403]) from 
> [] (i2c_device_probe+0x74/0x8c)
> [ 83.118133] [] (i2c_device_probe+0x74/0x8c) from [] 
> (driver_probe_device+0xc0/0x178)
> [ 83.127868] [] (driver_probe_device+0xc0/0x178) from 
> [] (bus_for_each_drv+0x44/0x80)
> [ 83.137603] [] (bus_for_each_drv+0x44/0x80) from [] 
> (device_attach+0x68/0x8c)
> [ 83.147003] [] (device_attach+0x68/0x8c) from [] 
> (bus_probe_device+0x24/0x40)
> [ 83.156097] [] (bus_probe_device+0x24/0x40) from [] 
> (device_add+0x31c/0x490)
> [ 83.165100] [] (device_add+0x31c/0x490) from [] 
> (i2c_new_device+0x154/0x1b0)
> [ 83.174133] [] (i2c_new_device+0x154/0x1b0) from [] 
> (adv7403_mod_init+0x70/0x94 [adv7403])
> [ 83.184356] [] (adv7403_mod_init+0x70/0x94 [adv7403]) from 
> [] (do_one_initcall+0x5c/0x1b4)
> [ 83.194915] [] (do_one_initcall+0x5c/0x1b4) from [] 
> (sys_init_module+0xb0/0x1dc)
> [ 83.204345] [] (sys_init_module+0xb0/0x1dc) from [] 
> (ret_fast_syscall+0x0/0x2c)
> [ 83.213653] ---[ end trace 09559d2558e8a7e2 ]---
> [ 83.218444] failed to register the device node /dev/videoX
> [ 83.223999] adv7403: probe of 2-0021 failed with error -22
> root@beagleboard-dvsdk:/lib/modules/2.6.32/kernel/drivers/media/video#
>
>
> //error---//
>
>
> Q1. regarding v4l2_subdev
>
> during v4l2_i2c_subdev_int() only support for v4l2_subdev_core_ops(i.e., 
> g_chip_ident) but these functions are not accessed during run time is 
> there any manual where i can get the details on the manner in which these 
> functions are accessed.. or the reason why these functions are triggered..
>
> (these functions were added by referring the device drivers of ADV7180, 
> TVP514x)
>
> Q2. regarding device node creation
>
> errno -22 represents INVALID ARGUMENT (reference: 
> http://www-numi.fnal.gov/offline_software/srt_public_context/WebDocs/Errors/unix_system_errors.html
>  )
>
> is it because i didnt fill the fields of structure video_device in my 
> device driver?? if it is because of this then how do i fill the parameters 
> of video_device... 
>
> how do i solve this problem??
>
>
> thanking you,
>
> Shravan Kulkarni
>
>
> P.S :-
>
> Host machine configuration:-
>
> Intel Core 2 Duo 2.4Ghz,
>
> 2GB 

Re: [beagleboard] Re: Loading the .out file (executable file) on to BBB and running

[Megha Bhirade]

Hi jim,

from the processer SDK i can get GCC compiler only, can i compile the 
simple code printing hello word on terminal using GCC compiler and execute 
the file ??

Ex : vi test.c(simple hello world program).
gcc test.c -o test.o
./test.o
like this once i login to beagle bone black???

-- 
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/797db949-6642-4a1f-b008-071b3c12d6dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Megha Bhirade]

>
> Hi tarmo,
>
   i am using a PC with Linux Ubuntu and version is 16.04LTS (64-bit) 
Ubuntu as a native operating system.

As u suggested  i used *tail -n 100 /var/log/syslog *in to command 
line(terminal). i got much data not able to understand and i stored the 
data in to one file please check it i am attaching the same data..

one more thing u told about the local LAN can u explain it once??
 

-- 
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/24436e71-c4c1-4414-b002-5761e6f00606%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Jul 11 16:49:29 acufore-H110M-S2 dhclient[3436]: DHCPDISCOVER on 
enx3403de92aa91 to 255.255.255.255 port 67 interval 10 (xid=0xb48cfc2a)
Jul 11 16:49:39 acufore-H110M-S2 gnome-session[1636]: (nautilus:1800): 
Gtk-CRITICAL **: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER 
(revealer)' failed
Jul 11 16:49:39 acufore-H110M-S2 dhclient[3436]: DHCPDISCOVER on 
enx3403de92aa91 to 255.255.255.255 port 67 interval 12 (xid=0xb48cfc2a)
Jul 11 16:49:51 acufore-H110M-S2 dhclient[3436]: DHCPDISCOVER on 
enx3403de92aa91 to 255.255.255.255 port 67 interval 13 (xid=0xb48cfc2a)
Jul 11 16:50:04 acufore-H110M-S2 dhclient[3436]: DHCPDISCOVER on 
enx3403de92aa91 to 255.255.255.255 port 67 interval 16 (xid=0xb48cfc2a)
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7051] 
dhcp4 (enx3403de92aa91): request timed out
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7052] 
dhcp4 (enx3403de92aa91): state changed unknown -> timeout
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7218] 
dhcp4 (enx3403de92aa91): canceled DHCP transaction, DHCP client pid 3436
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7219] 
dhcp4 (enx3403de92aa91): state changed timeout -> done
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7223] 
device (enx3403de92aa91): state change: ip-config -> failed (reason 
'ip-config-unavailable') [70 120 5]
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7229] 
device (enx3403de92aa91): Activation: failed for connection 'Wired connection 2'
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7237] 
device (enx3403de92aa91): state change: failed -> disconnected (reason 'none') 
[120 30 0]
Jul 11 16:50:06 acufore-H110M-S2 avahi-daemon[720]: Withdrawing address record 
for fe80::64e5:40af:aaa7:542c on enx3403de92aa91.
Jul 11 16:50:06 acufore-H110M-S2 avahi-daemon[720]: Leaving mDNS multicast 
group on interface enx3403de92aa91.IPv6 with address fe80::64e5:40af:aaa7:542c.
Jul 11 16:50:06 acufore-H110M-S2 avahi-daemon[720]: Interface 
enx3403de92aa91.IPv6 no longer relevant for mDNS.
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7284] 
policy: auto-activating connection 'Wired connection 2'
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7298] 
device (enx3403de92aa91): Activation: starting connection 'Wired connection 2' 
(aa579bc5-b95b-308a-8301-de30d92995c4)
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7303] 
device (enx3403de92aa91): state change: disconnected -> prepare (reason 'none') 
[30 40 0]
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7308] 
device (enx3403de92aa91): state change: prepare -> config (reason 'none') [40 
50 0]
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7312] 
device (enx3403de92aa91): state change: config -> ip-config (reason 'none') [50 
70 0]
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7315] 
dhcp4 (enx3403de92aa91): activation: beginning transaction (timeout in 45 
seconds)
Jul 11 16:50:06 acufore-H110M-S2 NetworkManager[784]:   [1562844006.7340] 
dhcp4 (enx3403de92aa91): dhclient started with pid 3457
Jul 11 16:50:06 acufore-H110M-S2 dhclient[3457]: DHCPDISCOVER on 
enx3403de92aa91 to 255.255.255.255 port 67 interval 3 (xid=0x7d946b7e)
Jul 11 16:50:08 acufore-H110M-S2 avahi-daemon[720]: Joining mDNS multicast 
group on interface enx3403de92aa91.IPv6 with address fe80::64e5:40af:aaa7:542c.
Jul 11 16:50:08 acufore-H110M-S2 avahi-daemon[720]: New relevant interface 
enx3403de92aa91.IPv6 for mDNS.
Jul 11 16:50:08 acufore-H110M-S2 avahi-daemon[720]: Registering new address 
record for fe80::64e5:40af:aaa7:542c on enx3403de92aa91.*.
Jul 11 16:50:09 acufore-H110M-S2 dhclient[3457]: DHCPDISCOVER on 
enx3403de92aa91 to 255.255.255.255 port 67 interval 7 (xid=0x7d946b7e)
Jul 11 16:50:12 acufore-H110M-S2 kernel: [ 2945.492477] [ cut here 
]
Jul 11 16:50:12 acufore-H110M-S2 kernel: [ 2945.492492] WARNING: CPU: 0 PID: 0 

[beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Megha Bhirade]

On Thursday, July 11, 2019 at 12:39:25 PM UTC+5:30, Megha Bhirade wrote:
>
> Hi,
>
> i am new to beagle bone black board. just after getting new board i 
> connected that board to my PC using USB cable and checked it is showing 
> BEAGLE BONE like mass storage drive on system(linux ubuntu), i clicked and 
> entered in to drive and got one START.HMT file clicked on it, it went to 
> website and showed next step install drivers..
>
> i downloaded the mkudevrule.sh file and run it by using chmod + x(for 
> permission) , sudo command  , it completed...
>
> i got 73-beagle bone.rules  file is created in /etc/udev/rules.d/... after 
> this i concluded drivers are installed properly..
>
> i am trying to get ip address of BBB , but not able to get?? please 
> suggest me what is problem:
>
>
> acufore@acufore-H110M-S2:~$ cd /etc/udev/rules.d/
> acufore@acufore-H110M-S2:/etc/udev/rules.d$ ls
> 73-beaglebone.rules
> acufore@acufore-H110M-S2:/etc/udev/rules.d$ cd
> acufore@acufore-H110M-S2:~$ ifconfig
> enp2s0Link encap:Ethernet  HWaddr e0:d5:5e:11:5d:65  
>   inet addr:192.168.4.59  Bcast:192.168.4.255  Mask:255.255.255.0
>   inet6 addr: fe80::4508:cbb4:d574:e0c1/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:30922 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:13579 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:16593168 (16.5 MB)  TX bytes:1669767 (1.6 MB)
>
> enx3403de92aa91 Link encap:Ethernet  HWaddr 34:03:de:92:aa:91  
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:41 errors:3 dropped:0 overruns:0 frame:3
>   TX packets:2 errors:58 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:10411 (10.4 KB)  TX bytes:520 (520.0 B)
>
> loLink encap:Local Loopback  
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:3169 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:3169 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1 
>   RX bytes:324659 (324.6 KB)  TX bytes:324659 (324.6 KB)
>
> acufore@acufore-H110M-S2:~$ ^C
> acufore@acufore-H110M-S2:~$ 
>  
> like this i am getting how can i proceed for 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/476ef30e-64a1-4034-bcae-96fc7c35c5e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Cape GPIO usage -- are there reserved pins?

[Tarmo Kuuse]

Hi Robert,

On Wednesday, 10 July 2019 05:32:06 UTC+3, Robert Heller wrote:
>
> OK, I have designed a cape, a Quad Stallmotor controller with/sense, which 
> uses 8 GPIO lines: four as outputs to drive a "stallmotor" type of switch 
> motor for model railroad turnouts [switch tracks] and four inputs to sense 
> the current state of the stallmotor (the state of the switches). 
>
> The I/O pins I am using are: 
>
> // GPIO0_7: P9-42 
> // GPIO1_6: P8-3 
> // GPIO1_28: P9-12 
> // GPIO1_7: P8-4 
>
>
> // GPIO1_16: P9-15 
> // GPIO1_17: P9-23 
> // GPIO3_21: P9-25 
> // GPIO3_19: P9-27 
>
> I am testing the cape and I having some issues and wanted to check if 
> there 
> are problems with using these pins, partitularly GPIO1_6 on P8-3 and 
> GPIO1_7 
> on P8-4 and I am slightly confused about GPIO0_7 on P9-42 (P9-42 seems to 
> be 
> listed as P9-42a and P9-42b). 
>
> I am getting kernel error messages relating to mmcblk1 (I am not using 
> mmcblk1 
> and I have zeroed it).  I *think* this might be because what is "wired" to 
> P8-3 and P8-4. 
>
> Should I be looking at redesigning my cape to use other GPIO lines? 
>
> -- 
> Robert Heller -- 978-544-6933 
> Deepwoods Software-- Custom Software Services 
> http://www.deepsoft.com/  -- Linux Administration Services 
> hel...@deepsoft.com-- Webhosting Services 
>   


I recommend Derek Molloy's GPIO tables for figuring out which pin is used 
for what. Out of experience I would recommend not using for GPIO a pin 
which has anything written in the "Notes" column.

https://github.com/derekmolloy/boneDeviceTree/blob/master/docs/BeagleboneBlackP8HeaderTable.pdf
https://github.com/derekmolloy/boneDeviceTree/blob/master/docs/BeagleboneBlackP9HeaderTable.pdf
 

--
Kind regards,
Tarmo

-- 
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/1b015b3d-e82a-44e6-a00f-5cf90677a84c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Getting IP address of BBB on ubuntu terminal

[Tarmo Kuuse]

Hi Megha,

On Thursday, 11 July 2019 10:09:25 UTC+3, Megha Bhirade wrote:
>
> Hi,
>
> i am new to beagle bone black board. just after getting new board i 
> connected that board to my PC using USB cable and checked it is showing 
> BEAGLE BONE like mass storage drive on system(linux ubuntu), i clicked and 
> entered in to drive and got one START.HMT file clicked on it, it went to 
> website and showed next step install drivers..
>
> i downloaded the mkudevrule.sh file and run it by using chmod + x(for 
> permission) , sudo command  , it completed...
>
> i got 73-beagle bone.rules  file is created in /etc/udev/rules.d/... after 
> this i concluded drivers are installed properly..
>
> i am trying to get ip address of BBB , but not able to get?? please 
> suggest me what is problem:
>
>
> acufore@acufore-H110M-S2:~$ cd /etc/udev/rules.d/
> acufore@acufore-H110M-S2:/etc/udev/rules.d$ ls
> 73-beaglebone.rules
> acufore@acufore-H110M-S2:/etc/udev/rules.d$ cd
> acufore@acufore-H110M-S2:~$ ifconfig
> enp2s0Link encap:Ethernet  HWaddr e0:d5:5e:11:5d:65  
>   inet addr:192.168.4.59  Bcast:192.168.4.255  Mask:255.255.255.0
>   inet6 addr: fe80::4508:cbb4:d574:e0c1/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:30922 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:13579 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:16593168 (16.5 MB)  TX bytes:1669767 (1.6 MB)
>
> enx3403de92aa91 Link encap:Ethernet  HWaddr 34:03:de:92:aa:91  
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:41 errors:3 dropped:0 overruns:0 frame:3
>   TX packets:2 errors:58 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000 
>   RX bytes:10411 (10.4 KB)  TX bytes:520 (520.0 B)
>
> loLink encap:Local Loopback  
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:3169 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:3169 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1 
>   RX bytes:324659 (324.6 KB)  TX bytes:324659 (324.6 KB)
>
> acufore@acufore-H110M-S2:~$ ^C
> acufore@acufore-H110M-S2:~$ 
>  
> like this i am getting how can i proceed for next..? 
>

So you have a PC with Ubuntu? Which version? Are you running Ubuntu as a 
native operating system or from a virtual machine? 

Connect the BBB using USB, dump logs (e.g. using "tail -n 100 
/var/log/syslog") and post here for further analysis. 

In the mean time - as a quick workaround I would connect the BBB to your 
local LAN using Ethernet. Then you'd find it from your PC using the name 
beaglebone.local. E.g. "ssh debian@beaglebone.local".

--
Kind regards,
Tarmo

-- 
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/844fa60a-2f2e-497c-ab6b-c33115aeee19%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Getting IP address of BBB on ubuntu terminal

[Megha Bhirade]

Hi,

i am new to beagle bone black board. just after getting new board i 
connected that board to my PC using USB cable and checked it is showing 
BEAGLE BONE like mass storage drive on system(linux ubuntu), i clicked and 
entered in to drive and got one START.HMT file clicked on it, it went to 
website and showed next step install drivers..

i downloaded the mkudevrule.sh file and run it by using chmod + x(for 
permission) , sudo command  , it completed...

i got 73-beagle bone.rules  file is created in /etc/udev/rules.d/... after 
this i concluded drivers are installed properly..

i am trying to get ip address of BBB , but not able to get?? please suggest 
me what is problem:


acufore@acufore-H110M-S2:~$ cd /etc/udev/rules.d/
acufore@acufore-H110M-S2:/etc/udev/rules.d$ ls
73-beaglebone.rules
acufore@acufore-H110M-S2:/etc/udev/rules.d$ cd
acufore@acufore-H110M-S2:~$ ifconfig
enp2s0Link encap:Ethernet  HWaddr e0:d5:5e:11:5d:65  
  inet addr:192.168.4.59  Bcast:192.168.4.255  Mask:255.255.255.0
  inet6 addr: fe80::4508:cbb4:d574:e0c1/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:30922 errors:0 dropped:0 overruns:0 frame:0
  TX packets:13579 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:16593168 (16.5 MB)  TX bytes:1669767 (1.6 MB)

enx3403de92aa91 Link encap:Ethernet  HWaddr 34:03:de:92:aa:91  
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:41 errors:3 dropped:0 overruns:0 frame:3
  TX packets:2 errors:58 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:10411 (10.4 KB)  TX bytes:520 (520.0 B)

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:3169 errors:0 dropped:0 overruns:0 frame:0
  TX packets:3169 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1 
  RX bytes:324659 (324.6 KB)  TX bytes:324659 (324.6 KB)

acufore@acufore-H110M-S2:~$ ^C
acufore@acufore-H110M-S2:~$ 
 
like this i am getting how can i proceed for 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/6b6eec00-f5d4-49b7-9202-681f328f7199%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.