Re: [beagleboard] /dev/i2c-1 missing on Pocket Beagle

[Mark A. Yoder]

I think I found by problem.  I was working on the Green Wireless and then 
transferred the SD card to the Pocket.  I forgot to restore /boot/uEnv.txt.

Thanks for the help...

--Mark

On Wednesday, October 31, 2018 at 4:57:43 PM UTC-4, Mark A. Yoder wrote:
>
> Is it normal for it to be missing on bootup?
>
> --Mark
>
> On Wednesday, October 31, 2018 at 4:48:57 PM UTC-4, RobertCNelson wrote:
>>
>> On Wed, Oct 31, 2018 at 3:21 PM Mark A. Yoder  
>> wrote: 
>> > 
>> > I fired up a Pocket Beagle today with the 2018-10-28 image and notice 
>> /dev/i2c-1 is missing. 
>> > 
>> > Here's what dmesg says: 
>> > 
>> > bone $ dmesg -H | grep i2c 
>> > [  +0.000852] omap_i2c 44e0b000.i2c: could not find pctldev for node 
>> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring 
>> probe 
>> > [  +0.63] omap_i2c 4802a000.i2c: could not find pctldev for node 
>> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_bb_i2c1_pins, deferring 
>> probe 
>> > [  +0.000937] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz 
>> > [  +0.001268] i2c /dev entries driver 
>> > [  +0.007484] input: tps65217_pwr_but as 
>> /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
>>  
>>
>> > [  +0.000108] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz 
>> > [  +0.000759] pinctrl-single 44e10800.pinmux: pin PIN97 already 
>> requested by ocp:P2_09_pinmux; cannot claim for 4802a000.i2c 
>> > [  +0.011333] pinctrl-single 44e10800.pinmux: pin-97 (4802a000.i2c) 
>> status -22 
>> > [  +0.007129] pinctrl-single 44e10800.pinmux: could not request pin 97 
>> (PIN97) from group pinmux_bb_i2c1_pins  on device pinctrl-single 
>> > [  +0.012083] omap_i2c 4802a000.i2c: Error applying setting, reverse 
>> things back 
>> > [  +0.007347] omap_i2c: probe of 4802a000.i2c failed with error -22 
>> > 
>> > And 
>> > 
>> > bone$ sudo /opt/scripts/tools/version.sh 
>> > git:/opt/scripts/:[e9bcff232834702c1c810710706ee815d77b080b] 
>> > eeprom:[A335PBGL00A21750EPB02572] 
>> > model:[TI_AM335x_PocketBeagle] 
>> > dogtag:[BeagleBoard.org Debian Image 2018-10-28] 
>> > bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot 
>> 2018.09-2-gd5b4c4b656]:[location: dd MBR] 
>> > kernel:[4.14.71-ti-r81] 
>> > nodejs:[v6.14.4] 
>> > uboot_overlay_options:[enable_uboot_overlays=1] 
>> > 
>> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1A-FAST-00A0.dtbo]
>>  
>>
>>
>> You need to use dtbo's with the "PB-" prefix..  there's a phandle name 
>> conflict in the above.. 
>>
>> 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/1fe606fc-c121-4011-bb47-5f6cd805109b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] /dev/i2c-1 missing on Pocket Beagle

[Mark A. Yoder]

Is it normal for it to be missing on bootup?

--Mark

On Wednesday, October 31, 2018 at 4:48:57 PM UTC-4, RobertCNelson wrote:
>
> On Wed, Oct 31, 2018 at 3:21 PM Mark A. Yoder  > wrote: 
> > 
> > I fired up a Pocket Beagle today with the 2018-10-28 image and notice 
> /dev/i2c-1 is missing. 
> > 
> > Here's what dmesg says: 
> > 
> > bone $ dmesg -H | grep i2c 
> > [  +0.000852] omap_i2c 44e0b000.i2c: could not find pctldev for node 
> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring 
> probe 
> > [  +0.63] omap_i2c 4802a000.i2c: could not find pctldev for node 
> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_bb_i2c1_pins, deferring 
> probe 
> > [  +0.000937] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz 
> > [  +0.001268] i2c /dev entries driver 
> > [  +0.007484] input: tps65217_pwr_but as 
> /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
>  
>
> > [  +0.000108] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz 
> > [  +0.000759] pinctrl-single 44e10800.pinmux: pin PIN97 already 
> requested by ocp:P2_09_pinmux; cannot claim for 4802a000.i2c 
> > [  +0.011333] pinctrl-single 44e10800.pinmux: pin-97 (4802a000.i2c) 
> status -22 
> > [  +0.007129] pinctrl-single 44e10800.pinmux: could not request pin 97 
> (PIN97) from group pinmux_bb_i2c1_pins  on device pinctrl-single 
> > [  +0.012083] omap_i2c 4802a000.i2c: Error applying setting, reverse 
> things back 
> > [  +0.007347] omap_i2c: probe of 4802a000.i2c failed with error -22 
> > 
> > And 
> > 
> > bone$ sudo /opt/scripts/tools/version.sh 
> > git:/opt/scripts/:[e9bcff232834702c1c810710706ee815d77b080b] 
> > eeprom:[A335PBGL00A21750EPB02572] 
> > model:[TI_AM335x_PocketBeagle] 
> > dogtag:[BeagleBoard.org Debian Image 2018-10-28] 
> > bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot 
> 2018.09-2-gd5b4c4b656]:[location: dd MBR] 
> > kernel:[4.14.71-ti-r81] 
> > nodejs:[v6.14.4] 
> > uboot_overlay_options:[enable_uboot_overlays=1] 
> > 
> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1A-FAST-00A0.dtbo]
>  
>
>
> You need to use dtbo's with the "PB-" prefix..  there's a phandle name 
> conflict in the above.. 
>
> 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/c50e0140-cbd4-4b88-bab7-6d6db48dff1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] /dev/i2c-1 missing on Pocket Beagle

[Robert Nelson]

On Wed, Oct 31, 2018 at 3:21 PM Mark A. Yoder  wrote:
>
> I fired up a Pocket Beagle today with the 2018-10-28 image and notice 
> /dev/i2c-1 is missing.
>
> Here's what dmesg says:
>
> bone $ dmesg -H | grep i2c
> [  +0.000852] omap_i2c 44e0b000.i2c: could not find pctldev for node 
> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring probe
> [  +0.63] omap_i2c 4802a000.i2c: could not find pctldev for node 
> /ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_bb_i2c1_pins, deferring 
> probe
> [  +0.000937] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
> [  +0.001268] i2c /dev entries driver
> [  +0.007484] input: tps65217_pwr_but as 
> /devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
> [  +0.000108] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
> [  +0.000759] pinctrl-single 44e10800.pinmux: pin PIN97 already requested by 
> ocp:P2_09_pinmux; cannot claim for 4802a000.i2c
> [  +0.011333] pinctrl-single 44e10800.pinmux: pin-97 (4802a000.i2c) status -22
> [  +0.007129] pinctrl-single 44e10800.pinmux: could not request pin 97 
> (PIN97) from group pinmux_bb_i2c1_pins  on device pinctrl-single
> [  +0.012083] omap_i2c 4802a000.i2c: Error applying setting, reverse things 
> back
> [  +0.007347] omap_i2c: probe of 4802a000.i2c failed with error -22
>
> And
>
> bone$ sudo /opt/scripts/tools/version.sh
> git:/opt/scripts/:[e9bcff232834702c1c810710706ee815d77b080b]
> eeprom:[A335PBGL00A21750EPB02572]
> model:[TI_AM335x_PocketBeagle]
> dogtag:[BeagleBoard.org Debian Image 2018-10-28]
> bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot 
> 2018.09-2-gd5b4c4b656]:[location: dd MBR]
> kernel:[4.14.71-ti-r81]
> nodejs:[v6.14.4]
> uboot_overlay_options:[enable_uboot_overlays=1]
> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1A-FAST-00A0.dtbo]

You need to use dtbo's with the "PB-" prefix..  there's a phandle name
conflict in the above..

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/CAOCHtYg5nZnzrH1s7M%3DHG%3DJK3SpGi19-B-mCGRmq%3DjKLORNh-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Setting i2c bus 2 speed

[Mark A. Yoder]

It's working.  i2c1 is now at 400kHz.

Thanks...

--Mark

-- 
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/2bdb6bee-0bdd-4a66-a3cb-ca239c142cc1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] /dev/i2c-1 missing on Pocket Beagle

[Mark A. Yoder]

I fired up a Pocket Beagle today with the 2018-10-28 image and notice 
/dev/i2c-1 is missing.  

Here's what dmesg says:

bone $ *dmesg -H | grep i2c*
[  +0.000852] omap_i2c 44e0b000.i2c: could not find pctldev for node 
/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_i2c0_pins, deferring 
probe
[  +0.63] omap_i2c 4802a000.i2c: could not find pctldev for node 
/ocp/l4_wkup@44c0/scm@21/pinmux@800/pinmux_bb_i2c1_pins, deferring 
probe
[  +0.000937] omap_i2c 4819c000.i2c: bus 2 rev0.11 at 400 kHz
[  +0.001268] i2c /dev entries driver
[  +0.007484] input: tps65217_pwr_but as 
/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024/tps65217-pwrbutton/input/input0
[  +0.000108] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[  +0.000759] pinctrl-single 44e10800.pinmux: pin PIN97 already requested 
by ocp:P2_09_pinmux; cannot claim for 4802a000.i2c
[  +0.011333] pinctrl-single 44e10800.pinmux: pin-97 (4802a000.i2c) status 
-22
[  +0.007129] pinctrl-single 44e10800.pinmux: could not request pin 97 
(PIN97) from group pinmux_bb_i2c1_pins  on device pinctrl-single
[  +0.012083] omap_i2c 4802a000.i2c: Error applying setting, reverse things 
back
[  +0.007347] omap_i2c: probe of 4802a000.i2c failed with error -22

And 

bone$ *sudo /opt/scripts/tools/version.sh* 
git:/opt/scripts/:[e9bcff232834702c1c810710706ee815d77b080b]
eeprom:[A335PBGL00A21750EPB02572]
model:[TI_AM335x_PocketBeagle]
dogtag:[BeagleBoard.org Debian Image 2018-10-28]
bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot 
2018.09-2-gd5b4c4b656]:[location: dd MBR]
kernel:[4.14.71-ti-r81]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C1A-FAST-00A0.dtbo]
uboot_overlay_options:[disable_uboot_overlay_video=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]
pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
]
pkg:[bb-cape-overlays]:[4.4.20181019.0-0rcnee0~stretch+20181019]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[kmod]:[23-2rcnee1~stretch+20171005]
pkg:[librobotcontrol]:[1.0.3-git20181009.0-0rcnee0~stretch+20181010]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep 
admin spi tisdk weston-launch xenomai]
cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M 
net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[1.106310] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 
568
[1.381858] pinctrl-single 44e10800.pinmux: pin PIN97 already requested 
by ocp:P2_09_pinmux; cannot claim for 4802a000.i2c
[1.393191] pinctrl-single 44e10800.pinmux: pin-97 (4802a000.i2c) status 
-22
[1.400320] pinctrl-single 44e10800.pinmux: could not request pin 97 
(PIN97) from group pinmux_bb_i2c1_pins  on device pinctrl-single
dmesg | grep gpio-of-helper
[1.114738] gpio-of-helper ocp:cape-universal: ready
END


What's up?

--Mark

p.s.  Switching to i2c2 I was able to get my SparkFun IRArray working!

-- 
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/4a445f18-707a-48df-a126-ebf3a550dadb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Change Debug Port From UART0 to USB0

[Jason Kridner]

I did some parts of the task, but not complete. 

http://youtu.be/9CxfKfjykz4
https://elinux.org/images/b/b2/Netconsole.pdf 



> On Oct 30, 2018, at 10:49 AM, Robert Nelson  wrote:
> 
>> On Tue, Oct 30, 2018 at 9:10 AM  wrote:
>> 
>> Hello:
>> 
>> Thanks for the valuable response.
>> 
>> In my case I had created only BOOT partition on my SD Card and I copied the 
>> MLO, U-boot.img and uEnv.txt files.
>> 
>> the content in the uEnv.txt is as follows:
>> 
>> 
>> uenvcmd=setenv bootargs console=ttyUSB0,115200n8 console=${console}
>> echo *** Booting To Baremetal_1 ***
>> 
>> 
>> Before applying USB power to BBB, SD card is inserted and I pressed and hold 
>> the Switch-2 to boot from SD Card.
>> 
>> But there is no response from the board at USB0 port.
>> 
>> 
>> Is it problem with uEnv.txt file.?
>> 
>> Are there required for any changes.?
> 
> Plug in a usb serial adapter into the j1 debug port.. did u-boot
> actually do what you expected?
> 
> 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/CAOCHtYiY%2BY-4iUyu%2BbVkQC4RRMyOysThmV6dmJghF9ON-u98wQ%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

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

Re: [beagleboard] Re: Falcon Christmas Pocket Beagle Wifi Issue

[devonadair96]

Thanks for the update! I ordered some of the suggested adapters and will 
update this thread if i have success!

On Wednesday, October 31, 2018 at 6:19:07 AM UTC-4, Daniel Kulp wrote:
>
>
>
> On Oct 31, 2018, at 12:01 AM, devona...@gmail.com  wrote:
>
> What wifi adapter were you successfully using? i have tried them all that 
> i have and none of them work. :/ I will hopefully end up getting the one 
> you go to work and try that.
>
>
> In general, non of the “dual band” wifi adapters will work very well, if 
> at all.  There are drivers for a couple of them, but most don’t work at 
> all. 
>
> For the most part, we recommend the Edimax 150MBit adapters.   They seem 
> to work the most reliably.   I personally use the EDUP 300Mbit adapters, 
> but I cannot find them anymore.  :(For the most part, if you go to 
> Amazon and search for “Raspberry Pi Wifi”, what comes up should work.
>
>
> I tried the linux driver option and none of them came up with wlan0. I 
> also tried lsusb and none of them showed up as a device.
>
> Is there a way to install the drivers/ enable them on falcon??
>
>
> Yea, if you can find drivers.  The script that we use to install drivers 
> on the image is at:
> https://github.com/FalconChristmas/fpp/blob/master/SD/FPP-Wifi-Drivers.sh
>
> So you can likely use that as a starting point to see what you need to do. 
>   As I said, though, the issue is actually finding drivers for the 
> appropriate chipset.  
>
> Dan
>
>
>
>
> On Tuesday, October 30, 2018 at 9:06:29 AM UTC-4, Daniel Kulp wrote:
>>
>>
>>
>> On Oct 29, 2018, at 10:16 PM, devona...@gmail.com wrote:
>> Thanks for sending me those projects! I will take a look over those 
>> tomorrow during class!
>>
>> The project i am doing is a graduation cap led matrix for a class I am 
>> in. More info here: 
>> https://elinux.org/ECE497_Project_-_LED_Matrix_Graduation_Cap. The page 
>> isn't complete yet but has a link of what we are trying to do. Feel free to 
>> follow our progress if you want.
>>
>> The adapter is Realtek RTL8188CUS i think. How do i see what drivers are 
>> installed and how to install them if i need to? 
>>
>>
>> rtl8188cus is not one of them.  :( 
>>
>> Two options:
>> 1) Use a different adapter if you have one available.
>>
>> 2) Flip to the kernel adapters and hope it works for your use case.   
>> With FPP 2.0/2.1 images, the setting was on the FPP Setting page.  With 2.2 
>> and 2.3, the setting is on the Network settings page.  
>>
>>
>> I will try the Linux drivers option tomorrow. Where on the network page 
>> can i find the network name/ password? Is that under the tether? 
>>
>>
>> No.  Once you get it to recognize the wlan0 device, you would select it 
>> from the list box of devices and then the SSID and password fields will 
>> appear.   Your need to get wlan0 found first though.
>>
>> Dan
>>
>>
>>
>>
>> I was looking for explanation of these options but was unsuccessful in 
>> finding them.
>>
>> Thanks,
>>
>> Devon
>>
>> On Monday, October 29, 2018 at 9:56:57 PM UTC-4, Daniel Kulp wrote:
>>>
>>>
>>>
>>> On Oct 29, 2018, at 9:15 PM, devona...@gmail.com wrote:
>>> The board is being powered off the micro USB port from my computer at 
>>> the moment. 
>>>
>>> The voltage from VI is 5 Volts and VB is 0 Volts. ID is about .8 Volts. 
>>> I do have 5 Volts on the USB.
>>>
>>> I would be interested in seeing those KiCad projects if possible!
>>>
>>>
>>>
>>> PocketScroller:
>>> https://www.dropbox.com/sh/6xks5tl5l4vr8cm/AAD10ftxImjgVQZbDLvcBRhMa?dl=0
>>>
>>> F8-PB:
>>> https://www.dropbox.com/sh/evuux5o7ogv2j50/AABsyxNA2QenPpanllb5lZ5Ha?dl=0
>>>
>>>
>>> Just recently updated them to KiCad 5 so hopefully they work.   Not sure 
>>> I got all the components re-mapped.
>>>
>>> Couple more questions:
>>> What WIFI adapter?  By default, FPP blacklists the kernel drivers as 
>>> they, in general, suck for our use.   I have a bunch of the various Realtek 
>>> blob drivers installed, but by no means all of them.   On the network page, 
>>> you could try flipping to using the Kernel drivers and see if that helps.   
>>>
>>> BTW:  can I ask what you are trying to do?  What kind of thing are you 
>>> trying to design?  
>>>
>>> Dan
>>>
>>>
>>>
>>> Falcon doesn't seem to be seeing the adapter.
>>>
>>> Thanks,
>>>
>>> Devon
>>>
>>> On Monday, October 29, 2018 at 2:26:13 PM UTC-4, devona...@gmail.com 
>>> wrote:

 Hello Everyone!

 I am currently working on a project with Falcon Christmas on the Pocket 
 Beagle. I have a USB WIFI dongle to add WIFI to the pocket beagle.

 I was following this guide to add the USB type A to it: 
 https://www.teachmemicro.com/pocketbeagle-wifi/.

 I am sure that it is wired properly but it doesn't show up on Falcon as 
 a device when i do "ifconfig". 
 The USB however doesn't seem to be on because the LED on the dongle 
 isn't lighting up even though there is 5 volts to the USB.

 I have made sure that the USB pins are not being 

Re: [beagleboard] Re: Set up Cape's EEPROM i2c-2 BeagleBoneBlack Rev-C

[Graham Haddock]

Detailed discussion on Apr 17 2017.

--- Graham

==

On Wed, Oct 31, 2018 at 10:15 AM Graham Haddock 
wrote:

> I think there is a detailed discussion as to what is supposed to be inside
> the cape EEPROMs in the
> "BeagleBone Black System Reference Manual"
>
> It looks like there is a live Wiki version at
>
> https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual
>
> But since that address has already been reserved by the kernel, for the
> cape manager,
> you will not be able to read/write it from user space.
>
> If you want to access that address from user space on a BBB, you need to
> stop the cape manager.
> Google "BBB without reserved I2C addresses" on this forum.
> and look at "am335x-bone-common-no-capemgr.dtsi"
>
> --- Graham
>
> ==
>
>
> On Wed, Oct 31, 2018 at 10:01 AM MG  wrote:
>
>> @Graham I do have a cape with EEPROM at address 0x57 but the EEPROM is
>> wiped with nothing on it so I guess that is why the board doesn't populate
>> that address by default. How can I fix that?
>>
>> On Tuesday, October 30, 2018 at 11:14:50 PM UTC-4, gra...@flex-radio.com
>> wrote:
>>>
>>> Those addresses at 0x54-0x57 are reserved by the kernel driver.
>>>
>>> Unless you have some capes with those EEPROMS populated, there is
>>> nothing actually there.
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>> On Tuesday, October 30, 2018 at 7:01:27 PM UTC-5, MG wrote:

 The BeagleBoneBlack comes with an "internal" EEPROM connected to i2c-0
 line. I can see that clearly when I do i2cdetect:

 debian@beaglebone:~$ i2cdetect -y -r 0
  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 70: UU -- -- -- -- -- -- --

 It is showing under address 0x50. When I try to do ahexdump I get the
 following values with no issue:

 sudo hexdump -C /sys/class/i2c-dev/i2c-0/device/0-0050/eeprom |
 head -5
   aa 55 33 ee 41 33 33 35  42 4e 4c 54 30 30 30 43
 |.U3.A335BNLT000C|
 0010  31 38 33 37 42 42 42 47  30 36 32 32 ff ff ff ff
 |1837BBBG0622|
 0020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
 ||
 *
 1000  aa 55 33 ee 41 33 33 35  42 4e 4c 54 30 30 30 43
 |.U3.A335BNLT000C|

 Now I want to add another EEPROM (with cape) on i2c-2 line which is
 supported according to [BBB SRM](
 https://cdn-shop.adafruit.com/datasheets/BBB_SRM.pdf) section 8.2. It
 is the CAT24C256 as mentioned in the SRM. The allowable address range for
 the expansion cards is 0x54-0x57. When I do i2cdetect I can see the
 following:

 debian@beaglebone:~$ i2cdetect -r -y 2
  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
 70: -- -- -- -- -- -- -- --

 I can see the addresses 0x54-0x57 showing, but when I try hex dump I
 get an error:

   hexdump: /sys/class/i2c-dev/i2c-2/device/2-0054/eeprom:
 Connection timed out

 Questions:

 1. Why are they showing as U's not actual address numbers? I know U
 stands for used resource?
 2. Why am I failing to read from that EEPROM? I have tried all addreses
 from 0x54-0x57 with no luck. I can confirm that those addresses are showing
 in /sys/class/i2c-dev/i2c-2/device and the each dir has the following in 
 it:

  debian@beaglebone:~$ ls
 /sys/class/i2c-dev/i2c-2/device/2-0054/ -la
  total 0
  drwxr-xr-x 4 root root 0 Oct 26 19:46 .
  drwxr-xr-x 8 root root 0 Oct 26 19:46 ..
  drwxr-xr-x 3 root root 0 Oct 26 19:47 2-00540
  lrwxrwxrwx 1 root root 0 Oct 26 19:47 driver ->
 ../../../../../../bus/i2c/drivers/at24
  -rw--- 1 root root 32768 Oct 26 19:47 eeprom
  -r--r--r-- 1 root root  4096 Oct 26 19:47 modalias
  -r--r--r-- 1 root root  4096 Oct 26 19:47 name
  lrwxrwxrwx 1 root root 0 Oct 26 19:47 of_node ->
 ../../../../../../firmware/devicetree/base/ocp/i2c@4819c000
 /cape_eeprom0@54
  drwxr-xr-x 2 root root 0 Oct 26 19:47 

Re: [beagleboard] Re: Set up Cape's EEPROM i2c-2 BeagleBoneBlack Rev-C

[Graham Haddock]

I think there is a detailed discussion as to what is supposed to be inside
the cape EEPROMs in the
"BeagleBone Black System Reference Manual"

It looks like there is a live Wiki version at
https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual

But since that address has already been reserved by the kernel, for the
cape manager,
you will not be able to read/write it from user space.

If you want to access that address from user space on a BBB, you need to
stop the cape manager.
Google "BBB without reserved I2C addresses" on this forum.
and look at "am335x-bone-common-no-capemgr.dtsi"

--- Graham

==


On Wed, Oct 31, 2018 at 10:01 AM MG  wrote:

> @Graham I do have a cape with EEPROM at address 0x57 but the EEPROM is
> wiped with nothing on it so I guess that is why the board doesn't populate
> that address by default. How can I fix that?
>
> On Tuesday, October 30, 2018 at 11:14:50 PM UTC-4, gra...@flex-radio.com
> wrote:
>>
>> Those addresses at 0x54-0x57 are reserved by the kernel driver.
>>
>> Unless you have some capes with those EEPROMS populated, there is nothing
>> actually there.
>>
>> --- Graham
>>
>> ==
>>
>> On Tuesday, October 30, 2018 at 7:01:27 PM UTC-5, MG wrote:
>>>
>>> The BeagleBoneBlack comes with an "internal" EEPROM connected to i2c-0
>>> line. I can see that clearly when I do i2cdetect:
>>>
>>> debian@beaglebone:~$ i2cdetect -y -r 0
>>>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>>> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
>>> 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- --
>>> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 70: UU -- -- -- -- -- -- --
>>>
>>> It is showing under address 0x50. When I try to do ahexdump I get the
>>> following values with no issue:
>>>
>>> sudo hexdump -C /sys/class/i2c-dev/i2c-0/device/0-0050/eeprom | head
>>> -5
>>>   aa 55 33 ee 41 33 33 35  42 4e 4c 54 30 30 30 43
>>> |.U3.A335BNLT000C|
>>> 0010  31 38 33 37 42 42 42 47  30 36 32 32 ff ff ff ff
>>> |1837BBBG0622|
>>> 0020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff
>>> ||
>>> *
>>> 1000  aa 55 33 ee 41 33 33 35  42 4e 4c 54 30 30 30 43
>>> |.U3.A335BNLT000C|
>>>
>>> Now I want to add another EEPROM (with cape) on i2c-2 line which is
>>> supported according to [BBB SRM](
>>> https://cdn-shop.adafruit.com/datasheets/BBB_SRM.pdf) section 8.2. It
>>> is the CAT24C256 as mentioned in the SRM. The allowable address range for
>>> the expansion cards is 0x54-0x57. When I do i2cdetect I can see the
>>> following:
>>>
>>> debian@beaglebone:~$ i2cdetect -r -y 2
>>>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>>> 00:  -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
>>> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>>> 70: -- -- -- -- -- -- -- --
>>>
>>> I can see the addresses 0x54-0x57 showing, but when I try hex dump I get
>>> an error:
>>>
>>>   hexdump: /sys/class/i2c-dev/i2c-2/device/2-0054/eeprom: Connection
>>> timed out
>>>
>>> Questions:
>>>
>>> 1. Why are they showing as U's not actual address numbers? I know U
>>> stands for used resource?
>>> 2. Why am I failing to read from that EEPROM? I have tried all addreses
>>> from 0x54-0x57 with no luck. I can confirm that those addresses are showing
>>> in /sys/class/i2c-dev/i2c-2/device and the each dir has the following in it:
>>>
>>>  debian@beaglebone:~$ ls
>>> /sys/class/i2c-dev/i2c-2/device/2-0054/ -la
>>>  total 0
>>>  drwxr-xr-x 4 root root 0 Oct 26 19:46 .
>>>  drwxr-xr-x 8 root root 0 Oct 26 19:46 ..
>>>  drwxr-xr-x 3 root root 0 Oct 26 19:47 2-00540
>>>  lrwxrwxrwx 1 root root 0 Oct 26 19:47 driver ->
>>> ../../../../../../bus/i2c/drivers/at24
>>>  -rw--- 1 root root 32768 Oct 26 19:47 eeprom
>>>  -r--r--r-- 1 root root  4096 Oct 26 19:47 modalias
>>>  -r--r--r-- 1 root root  4096 Oct 26 19:47 name
>>>  lrwxrwxrwx 1 root root 0 Oct 26 19:47 of_node ->
>>> ../../../../../../firmware/devicetree/base/ocp/i2c@4819c000
>>> /cape_eeprom0@54
>>>  drwxr-xr-x 2 root root 0 Oct 26 19:47 power
>>>  lrwxrwxrwx 1 root root 0 Oct 26 19:47 subsystem ->
>>> ../../../../../../bus/i2c
>>>  -rw-r--r-- 1 root root  4096 Oct 26 19:47 uevent
>>>
>>> I can see the addresses mapping into the kernel but when I try to
>>> 

[beagleboard] Re: Set up Cape's EEPROM i2c-2 BeagleBoneBlack Rev-C

[MG]

@Graham I do have a cape with EEPROM at address 0x57 but the EEPROM is 
wiped with nothing on it so I guess that is why the board doesn't populate 
that address by default. How can I fix that?

On Tuesday, October 30, 2018 at 11:14:50 PM UTC-4, gra...@flex-radio.com 
wrote:
>
> Those addresses at 0x54-0x57 are reserved by the kernel driver.
>
> Unless you have some capes with those EEPROMS populated, there is nothing 
> actually there.
>
> --- Graham
>
> ==
>
> On Tuesday, October 30, 2018 at 7:01:27 PM UTC-5, MG wrote:
>>
>> The BeagleBoneBlack comes with an "internal" EEPROM connected to i2c-0 
>> line. I can see that clearly when I do i2cdetect:
>>
>> debian@beaglebone:~$ i2cdetect -y -r 0
>>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> 00:  -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 
>> 30: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 
>> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 70: UU -- -- -- -- -- -- -- 
>>
>> It is showing under address 0x50. When I try to do ahexdump I get the 
>> following values with no issue:
>>
>> sudo hexdump -C /sys/class/i2c-dev/i2c-0/device/0-0050/eeprom | head 
>> -5
>>   aa 55 33 ee 41 33 33 35  42 4e 4c 54 30 30 30 43  
>> |.U3.A335BNLT000C|
>> 0010  31 38 33 37 42 42 42 47  30 36 32 32 ff ff ff ff  
>> |1837BBBG0622|
>> 0020  ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff  
>> ||
>> *
>> 1000  aa 55 33 ee 41 33 33 35  42 4e 4c 54 30 30 30 43  
>> |.U3.A335BNLT000C|
>>
>> Now I want to add another EEPROM (with cape) on i2c-2 line which is 
>> supported according to [BBB SRM](
>> https://cdn-shop.adafruit.com/datasheets/BBB_SRM.pdf) section 8.2. It is 
>> the CAT24C256 as mentioned in the SRM. The allowable address range for the 
>> expansion cards is 0x54-0x57. When I do i2cdetect I can see the following:
>>
>> debian@beaglebone:~$ i2cdetect -r -y 2
>>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> 00:  -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 
>> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>> 70: -- -- -- -- -- -- -- --   
>>
>> I can see the addresses 0x54-0x57 showing, but when I try hex dump I get 
>> an error:
>>
>>   hexdump: /sys/class/i2c-dev/i2c-2/device/2-0054/eeprom: Connection 
>> timed out
>>
>> Questions:
>>
>> 1. Why are they showing as U's not actual address numbers? I know U 
>> stands for used resource?
>> 2. Why am I failing to read from that EEPROM? I have tried all addreses 
>> from 0x54-0x57 with no luck. I can confirm that those addresses are showing 
>> in /sys/class/i2c-dev/i2c-2/device and the each dir has the following in it:
>>
>>  debian@beaglebone:~$ ls /sys/class/i2c-dev/i2c-2/device/2-0054/ 
>> -la
>>  total 0
>>  drwxr-xr-x 4 root root 0 Oct 26 19:46 .
>>  drwxr-xr-x 8 root root 0 Oct 26 19:46 ..
>>  drwxr-xr-x 3 root root 0 Oct 26 19:47 2-00540
>>  lrwxrwxrwx 1 root root 0 Oct 26 19:47 driver -> 
>> ../../../../../../bus/i2c/drivers/at24
>>  -rw--- 1 root root 32768 Oct 26 19:47 eeprom
>>  -r--r--r-- 1 root root  4096 Oct 26 19:47 modalias
>>  -r--r--r-- 1 root root  4096 Oct 26 19:47 name
>>  lrwxrwxrwx 1 root root 0 Oct 26 19:47 of_node -> 
>> ../../../../../../firmware/devicetree/base/ocp/i2c@4819c000/cape_eeprom0@54
>>  drwxr-xr-x 2 root root 0 Oct 26 19:47 power
>>  lrwxrwxrwx 1 root root 0 Oct 26 19:47 subsystem -> 
>> ../../../../../../bus/i2c
>>  -rw-r--r-- 1 root root  4096 Oct 26 19:47 uevent 
>>
>> I can see the addresses mapping into the kernel but when I try to hexdump 
>> eeprom it doesn't work at all. I though this was supposed to be setup by 
>> kernel since it is mentioned in BeagleBone SRM. Am I going to need an 
>> overlay to add to uboot for this? It doesn't make sense since i2c-2 is 
>> already set up by  default i.e. when I connect another device at address 
>> aside from 0x54-0x57 it shows up fine and I'm able to interface to it?
>>
>> All I'm trying to do is read from the EEPROM like I did with the 
>> "internal" one to confirm it is working. What am I doing wrong?
>>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails 

[beagleboard] Re: How to deactivate automatic cape detection to free addresses on I2C-2

[MG]

@Beagle Boner If you can please post how you managed to move past this that 
would be very helpful. I have the same issue and I need to disable i2c-2 
line to use 0x57 address. I tried disbling the universal_cape in 
uboot/uEnv.txt but no luck. Based on your post I managed to go and get 
/boot/dts/4.14.67-ti-r73/am335x-boneblack.dtb. decompile it, comment out 
the i2c2 in the following places:

```
aliases {
i2c0 = "/ocp/i2c@44e0b000";
i2c1 = "/ocp/i2c@4802a000";
//i2c2 = "/ocp/i2c@4819c000";
serial0 = "/ocp/serial@44e09000";
serial1 = "/ocp/serial@48022000";
serial2 = "/ocp/serial@48024000";
serial3 = "/ocp/serial@481a6000";
serial4 = "/ocp/serial@481a8000";
serial5 = "/ocp/serial@481aa000";
d_can0 = "/ocp/can@481cc000";
d_can1 = "/ocp/can@481d";
usb0 = "/ocp/usb@4740/usb@47401000";
usb1 = "/ocp/usb@4740/usb@47401800";
phy0 = "/ocp/usb@4740/usb-phy@47401300";
phy1 = "/ocp/usb@4740/usb-phy@47401b00";
ethernet0 = "/ocp/ethernet@4a10/slave@4a100200";
ethernet1 = "/ocp/ethernet@4a10/slave@4a100300";
spi1 = "/ocp/spi@4803";
spi2 = "/ocp/spi@481a";
phandle = <0x70>;
};
...

//i2c@4802a000 {
//  compatible = "ti,omap4-i2c";
//  #address-cells = <0x1>;
//  #size-cells = <0x0>;
//  ti,hwmods = "i2c2";
//  reg = <0x4802a000 0x1000>;
//  interrupts = <0x47>;
//  status = "disabled";
//  phandle = <0xb4>;
//};

...

i2c1 = "/ocp/i2c@4802a000";
//i2c2 = "/ocp/i2c@4819c000";
cape_eeprom0 = "/ocp/i2c@4819c000/cape_eeprom0@54";
cape0_data = 
"/ocp/i2c@4819c000/cape_eeprom0@54/cape_data@0";
cape_eeprom1 = "/ocp/i2c@4819c000/cape_eeprom1@55";

```
but still no luck, when I boot I can still see U under i2c2 addresses of 
0x54-0x57. Please share your solution

-- 
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/92a447d0-873d-473d-bf10-ef0b0f2e9aef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: GPIO toggle Kernel Module for Beaglebone

[Rudy Misek]

Thank you guys!! Have a great rest of the week ✌

On Tue, Oct 30, 2018 at 1:12 AM Bill Bitner  wrote:

> Hi Rudy!   I'm not sure where the link was supposed to point to but I
> found the following an
> excellent guide to experimenting the PRU's using the 4.14 series kernel.
> (you would have to
> update for this to apply)
>  (https://github.com/MarkAYoder/PRUCookbook)
>
>
> Bill Bitner
>
> On Thu, Oct 25, 2018 at 7:41 PM  wrote:
>
>> Hi Wesley,
>>
>> I'm interested in checking this out!
>>
>> The download links are broken, are you able to post new links?
>>
>> Hope you're having a top day :D
>>
>> -Rudy.
>>
>> On Friday, August 31, 2012 at 7:04:39 AM UTC+10, Wesley wrote:
>>>
>>> Hey,
>>>
>>> So I tested to see how fast the GPIO toggle rate of the Beaglebone could
>>> get when using a kernel module. When using user space it was only about 4-5
>>> MHz and once I did the kernel module it got up to 25 MHz. Since I had a
>>> difficult time getting the kernel source tree on the beaglebone and
>>> compiling everything here is some documentation and code for those who want
>>> to build kernel modules/device drivers on the beaglebone and also user
>>> program interaction with the kernel module.
>>>
>>> gpio.c is the kernel code
>>> gpio.h is the header file for both gpio.c and ioctl.c
>>> ioctl.c is the user code
>>>
>>> Here is my Makefile in case you want it also
>>>
>>> ~
>>> obj-m := gpio.o
>>>
>>> KERNELDIR := /usr/src/linux-3.2.23
>>>
>>> default:
>>> $(MAKE) -C $(KERNELDIR) M=$(PWD) modules
>>> ~
>>>
>>> Also, the websites that I used that helped me get here were mainly these:
>>>
>>> https://groups.google.com/forum/#!msg/beagleboard/BKnNkP3qzQs/PNloua3737MJ
>>> http://www.cemetech.net/forum/viewtopic.php?t=7814
>>> and the Linux Device Drivers book
>>>
>>> ~Wesley
>>>
>>> --
>> 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/a282b742-f1db-4fc6-afa9-2c15599c5f59%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/dyuax5415dc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAOYP4dhSp%3Dnbnq7BwYKb2vhpmKVCapfNyRPayC7q2nvDWvNN7A%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] Change Debug Port From UART0 to USB0

[subbu3881]

Hello Robert:

What you said is normal connection like using USB to TTL cable connecting 
to J1 Header.

>
>Plug in a usb serial adapter into the j1 debug port.. did u-boot 
>actually do what you expected?
>

It is working properly.


Normally, when the board is completely up and Linux Login prompt is only 
showing in the USB0 port of the board.
But, I am trying to achieve the same on USB0 port on the board, i.e., I wan 
to see the Uboot debug information on USB0 port.

the following is the uboot log information coming on the UART0 port (J1 
Connector)


*U-Boot SPL 2011.09-2-gd0e52e5 (Apr 14 2012 - 22:13:07)
Texas Instruments Revision detection unimplemented
No AC power, disabling frequency switch
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img


U-Boot 2011.09-2-gd0e52e5 (Apr 14 2012 - 22:13:07)

I2C:   ready
DRAM:  256 MiB
WARNING: Caches not enabled
No daughter card present
NAND:  HW ECC Hamming Code selected
No NAND device found!!!
0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

Net:   cpsw
Hit any key to stop autoboot:  3 ��� 2 ��� 1 ��� 0 
SD/MMC found on device 0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
reading uImage

3132976 bytes read
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.1.0-00010-g66bfbd2
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:3132912 Bytes = 3 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   XIP Kernel Image ... OK
OK

Starting kernel ...*


Is it possible to see the same on USB0 port with any proper modifications.?

Thanks and Regards,
Siva Prakash Reddy.


On Tuesday, October 30, 2018 at 8:19:42 PM UTC+5:30, RobertCNelson wrote:
>
> On Tue, Oct 30, 2018 at 9:10 AM > wrote: 
> > 
> > Hello: 
> > 
> > Thanks for the valuable response. 
> > 
> > In my case I had created only BOOT partition on my SD Card and I copied 
> the MLO, U-boot.img and uEnv.txt files. 
> > 
> > the content in the uEnv.txt is as follows: 
> > 
> > 
> > uenvcmd=setenv bootargs console=ttyUSB0,115200n8 console=${console} 
> > echo *** Booting To Baremetal_1 *** 
> > 
> > 
> > Before applying USB power to BBB, SD card is inserted and I pressed and 
> hold the Switch-2 to boot from SD Card. 
> > 
> > But there is no response from the board at USB0 port. 
> > 
> > 
> > Is it problem with uEnv.txt file.? 
> > 
> > Are there required for any changes.? 
>
> Plug in a usb serial adapter into the j1 debug port.. did u-boot 
> actually do what you expected? 
>
> 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/8db602d6-4638-4377-9e55-8180fcf8723d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Accessing uEnv.txt

[subbu3881]

 

Hi Robert:



In my case I had created only BOOT partition on my SD Card and I copied the 
MLO, U-boot.img and uEnv.txt files.

the content in the uEnv.txt is as follows:


*uenvcmd=setenv bootargs console=ttyUSB0,115200n8 console=${console}*

*run **uenvcmd*
*echo *** Booting To Baremetal_1 


Before applying USB power to BBB, SD card is inserted and I pressed and 
hold the Switch-2 to boot from SD Card.

But there is no response from the board at USB0 port.


Is it problem with uEnv.txt file.?

Are there required for any changes.?


Thanks And Regards,

Siva Prakash Reddy




On Monday, October 29, 2018 at 7:44:20 PM UTC+5:30, RobertCNelson wrote:
>
> On Mon, Oct 29, 2018 at 7:00 AM > wrote: 
> > 
> > Hello: 
> > 
> > I am currently working on Beagle Bone Black (BBB) board. 
> > 
> > I am having uSD card and both ROOT and BOOT partitions are created with 
> ext4 and FAT32 filesystems respectively. 
> > 
> > I copied the MLO, uboot.img, .dtb and kernel image into BOOT partition. 
> Now, I created on uEnv.txt file to set some boot arguments and save. 
> > 
> > 1. Where can I place the uEnv.txt file whether in BOOT partition or ROOT 
> partition.? 
> > 2. How Can I change the Debug Console from UART0 to USB0 from uEnv.txt.? 
>
> console=ttyUSB0,115200n8 
>
> 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/29adb586-df4e-47bb-b67e-53dcd5c0f4ab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Falcon Christmas Pocket Beagle Wifi Issue

[Daniel Kulp]

> On Oct 31, 2018, at 12:01 AM, devonadai...@gmail.com wrote:
> 
> What wifi adapter were you successfully using? i have tried them all that i 
> have and none of them work. :/ I will hopefully end up getting the one you go 
> to work and try that.

In general, non of the “dual band” wifi adapters will work very well, if at 
all.  There are drivers for a couple of them, but most don’t work at all. 

For the most part, we recommend the Edimax 150MBit adapters.   They seem to 
work the most reliably.   I personally use the EDUP 300Mbit adapters, but I 
cannot find them anymore.  :(For the most part, if you go to Amazon and 
search for “Raspberry Pi Wifi”, what comes up should work.


> I tried the linux driver option and none of them came up with wlan0. I also 
> tried lsusb and none of them showed up as a device.
> 
> Is there a way to install the drivers/ enable them on falcon??

Yea, if you can find drivers.  The script that we use to install drivers on the 
image is at:
https://github.com/FalconChristmas/fpp/blob/master/SD/FPP-Wifi-Drivers.sh 


So you can likely use that as a starting point to see what you need to do.   As 
I said, though, the issue is actually finding drivers for the appropriate 
chipset.  

Dan


> 
> 
> On Tuesday, October 30, 2018 at 9:06:29 AM UTC-4, Daniel Kulp wrote:
> 
> 
>> On Oct 29, 2018, at 10:16 PM, devona...@gmail.com <> wrote:
>> Thanks for sending me those projects! I will take a look over those tomorrow 
>> during class!
>> 
>> The project i am doing is a graduation cap led matrix for a class I am in. 
>> More info here: 
>> https://elinux.org/ECE497_Project_-_LED_Matrix_Graduation_Cap 
>> . The page 
>> isn't complete yet but has a link of what we are trying to do. Feel free to 
>> follow our progress if you want.
>> 
>> The adapter is Realtek RTL8188CUS i think. How do i see what drivers are 
>> installed and how to install them if i need to? 
> 
> rtl8188cus is not one of them.  :( 
> 
> Two options:
> 1) Use a different adapter if you have one available.
> 
> 2) Flip to the kernel adapters and hope it works for your use case.   With 
> FPP 2.0/2.1 images, the setting was on the FPP Setting page.  With 2.2 and 
> 2.3, the setting is on the Network settings page.  
> 
> 
>> I will try the Linux drivers option tomorrow. Where on the network page can 
>> i find the network name/ password? Is that under the tether? 
> 
> No.  Once you get it to recognize the wlan0 device, you would select it from 
> the list box of devices and then the SSID and password fields will appear.   
> Your need to get wlan0 found first though.
> 
> Dan
> 
> 
> 
>> 
>> I was looking for explanation of these options but was unsuccessful in 
>> finding them.
>> 
>> Thanks,
>> 
>> Devon
>> 
>> On Monday, October 29, 2018 at 9:56:57 PM UTC-4, Daniel Kulp wrote:
>> 
>> 
>>> On Oct 29, 2018, at 9:15 PM, devona...@gmail.com <> wrote:
>>> The board is being powered off the micro USB port from my computer at the 
>>> moment. 
>>> 
>>> The voltage from VI is 5 Volts and VB is 0 Volts. ID is about .8 Volts. I 
>>> do have 5 Volts on the USB.
>>> 
>>> I would be interested in seeing those KiCad projects if possible!
>> 
>> 
>> PocketScroller:
>> https://www.dropbox.com/sh/6xks5tl5l4vr8cm/AAD10ftxImjgVQZbDLvcBRhMa?dl=0 
>> 
>> 
>> F8-PB:
>> https://www.dropbox.com/sh/evuux5o7ogv2j50/AABsyxNA2QenPpanllb5lZ5Ha?dl=0 
>> 
>> 
>> 
>> Just recently updated them to KiCad 5 so hopefully they work.   Not sure I 
>> got all the components re-mapped.
>> 
>> Couple more questions:
>> What WIFI adapter?  By default, FPP blacklists the kernel drivers as they, 
>> in general, suck for our use.   I have a bunch of the various Realtek blob 
>> drivers installed, but by no means all of them.   On the network page, you 
>> could try flipping to using the Kernel drivers and see if that helps.   
>> 
>> BTW:  can I ask what you are trying to do?  What kind of thing are you 
>> trying to design?  
>> 
>> Dan
>> 
>> 
>>> 
>>> Falcon doesn't seem to be seeing the adapter.
>>> 
>>> Thanks,
>>> 
>>> Devon
>>> 
>>> On Monday, October 29, 2018 at 2:26:13 PM UTC-4, devona...@gmail.com 
>>>  wrote:
>>> Hello Everyone!
>>> 
>>> I am currently working on a project with Falcon Christmas on the Pocket 
>>> Beagle. I have a USB WIFI dongle to add WIFI to the pocket beagle.
>>> 
>>> I was following this guide to add the USB type A to it: 
>>> https://www.teachmemicro.com/pocketbeagle-wifi/ 
>>> .
>>> 
>>> I am sure that it is wired properly but it doesn't show up on Falcon as a 
>>> device when i do "ifconfig". 
>>> The USB however doesn't seem to be on because the LED on the dongle 

Re: [beagleboard] Re: BBB Bare Metal Ethernet

['dd' via BeagleBoard]

Hi Jason.  I tried several times to create a project and failed.  
I do not know why you are hosted by the google monster, 
or why they cannot rip a decent forum host application.  

In any event, please create a project on my behalf, 
just copy and paste my post of Feb 7.

thanks, hack on brothers...dd

On Wednesday, February 7, 2018 at 9:21:52 PM UTC+2, Jason Kridner wrote:
>
> Can I encourage you to create a project entry via 
> https://beagleboard.org/p ? 
>
> On Wed, Feb 7, 2018 at 8:21 AM dschm12s via BeagleBoard <
> beagl...@googlegroups.com > wrote:
>
>> Hi dd,
>>
>> I already found a solution for my problem. I just set the physical 
>> address to 2 that it fits the condition and I used static ip now instead of 
>> dhcp. Now I can ping to the beagle and get a response. Before 
>> "CPSW0_PORT_1_PHY_ADDR" was set to zero. It is not explained anywhere why I 
>> needed to set it to 2. I was just try and error by myself.
>>
>> Snippet of "cpswif.h":
>>
>> #define CPSW0_PORT_1_PHY_ADDR   2
>> #define CPSW0_PORT_1_PHY_GIGABITFALSE
>>
>> regards,
>>
>> DS
>>
>>
>>
>> On Wednesday, February 7, 2018 at 2:05:34 PM UTC+1, 
>> dsch...@googlemail.com wrote:
>>>
>>> Hi dd,
>>>
>>> First I want to thank you for your contribution in efficient bare metal 
>>> programming. I am programming the beaglebone black in bearmetal as well at 
>>> the moment and I use Starterware 02.00.01.01 as a basis. I tried executing 
>>> the enetEcho example but I always run into an issue on initialization. I 
>>> didn't change anything and run the project with DHCP enabled. In function 
>>> "cpswif_phylink_config" of "cpswif.c" from the LWIP Stack the issue occurs 
>>> (No PHY found at address 0 for Port 0. MDIOSLAVE register value is "4". Do 
>>> you have any hints? Is perhaps my gel file already enabling the PHY? 
>>> Problem is I found no way of disabling the GEL Files in Code Composer 
>>> Studio. When I remove or comment the files, the IDE ignores that.
>>>
>>> Code Snippet:
>>>
>>> static err_t
>>> cpswif_phylink_config(struct cpswportif * cpswif, u32_t slv_port_num) {
>>>   struct cpswinst *cpswinst = _inst_data[cpswif->inst_num];
>>>   err_t err;
>>>
>>>   /* Check if ethernet PHY is present or not */
>>>   if(0 == (MDIOPhyAliveStatusGet(cpswinst->mdio_base)
>>> & (1 << cpswinst->port[slv_port_num - 1].phy_addr))){
>>> LWIP_PRINTF("\n\rNo PHY found at address %d for  Port %d of Instance 
>>> %d.",
>>> cpswinst->port[slv_port_num - 1].phy_addr, slv_port_num,
>>> cpswif->inst_num);
>>> return ERR_CONN;
>>>   }
>>>
>>> With kind regards,
>>>
>>> DS
>>>
>>>
>>> ---
>>>
>>> On Tuesday, February 6, 2018 at 10:44:51 AM UTC+1, dd wrote:

 Hi all.  I sort-of finished the Ethernet driver port from 
 Starterware.   It employs the full FAT32 filesystem by Elm-Chan and lwIP 
 by 
 Adam Dunkels.  The all the code, makefile stuff, bootloader etc... 
 required 
 to build an image with interrupts, MMC, TCP, UDP, DMA, Cache, MMU, IRQ, 
 RTC, httpserver and other peripherals.  Now you can use the BeagleBone to 
 control IoT projects, your own tight server or whatever.  Written under 
 GNU/GCC, for the serious noob.  Sink your teeth into ARM Bare Metal, FAT32 
  
 and Internet Protocol here.  The Bone' is very fast and economical when 
 running without the burden of an insecure Operating Systemdd

 PS  it runs but it needs more streamlining, and I need more help!
 www.github.com/ddlawrencewww.baremetal.tech

 I am an old engineer/programmer that is very tired of running on 
 dumbed-down blackbox and otherwise limiting operating systems.  Linux is 
 not the answer.  It should be, but it is too big/complicated. It really 
 has 
 not improved in 15 years.  It is much more intricate than the ARM hardware 
 it is running on.  Linus refuses to migrate to microKernel.  So do not get 
 old and obsolete like me, watching corporations fuddle with fickle tools, 
 capitalizing Net Neutrality and restricting your freedom as a programmer.  
 Learn the basics and build upward, on software that YOU know and own.  The 
 'Bone has unchallenged speed and I/O.  This is a worthwhile platform to 
 invest your effort.  The attached zipfile will give you a big head start.  

>>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/4bd7330a-92bb-4fe6-a998-50ebaff09644%40googlegroups.com
>>  
>>