[beagleboard] Re: Wiznet W5500 ethernet module driver can't install

On Tuesday, 16 January 2018 22:21:39 UTC+5:30, santosh aiwale wrote: > > The Wiznet W5500 is working on SPI with BBB. > I am working on pocket beagle bone using Linux beaglebone 4.4.91-ti-r133. > here is the driver link https://github.com/borg42/w5x00. > also kernel module build not available. >

[beagleboard] Which kernel is better for stretch? 4.4.x or 4.9.x?

Downloading the Stretch IoT (non-GUI) from beagleboard.org[1] yields an image with kernel 4.4.91-ti-r133. A Stretch IOT image from Robert Nelson[2] has kernel 4.9.74-ti-r90. My question specifically is: why the difference, and is one preferable over the other? Thanks [1] 

Re: [beagleboard] Wiznet W5500 ethernet module driver can't install

On Tuesday, 16 January 2018 23:31:48 UTC+5:30, RobertCNelson wrote: > > On Mon, Jan 15, 2018 at 10:59 PM, santosh aiwale > wrote: > > The Wiznet W5500 is working on SPI with BBB. > > I am working on pocket beagle bone using Linux beaglebone > 4.4.91-ti-r133. > > here

[beagleboard] uart performance flaky with BB 9.1 OS, works great with 7.11 version, same HW

I am connecting 2 bb blacks via serial uart, /dev/ttyO1. or /dev/ttyS1. they are symlinked. I need to use them at the fastest speeds, i.e. B300 or more. When i use the older 7.11 image (straight off beagleboard downloads site), the BB's communicate rock solid, no losses. When i upgrade the

Re: [beagleboard] Re: X15 Boot via USB

https://groups.google.com/forum/#!searchin/beagleboard-x15/BeagleBoard-X15$20esata%7Csort:date/beagleboard-x15/2psyUbULTwc/81KWBokQBgAJhttps://groups.google.com/forum/#!searchin/beagleboard-x15/BeagleBoard-X15$20esata%7Csort:date/beagleboard-x15/2psyUbULTwc/81KWBokQBgAJ Regards, John > On Jan

Re: [beagleboard] Re: X15 Boot via USB

Here is the discussion I read about this issue. https://groups.google.com/forum/#!topic/beagleboard-x15/FarRcmkeAI8 Regards, John > On Jan 16, 2018, at 4:30 AM, marc bellazzini wrote: > > Hello

Re: [beagleboard] Re: X15 Boot via USB

I read that someone did manage to get the X15 to boot from esata when using a powered esata interface. Apparently the power to the esata connector isn’t available during uboot and hence the need for a powered esata interface. I haven’t tried this myself, but I do recall someone on the ARM Linux

Re: [beagleboard] Default debian image not booting

Hey, thanks at first for the quick reply. The mentioned Images look a lot more promising, but both of them won't show anything on hdmi after the orange starting screen and will crash after some time with those messages: [ 79.053771] INFO: rcu_sched detected stalls on CPUs/tasks: [

[beagleboard] Re: JTAG or OpenOCD

https://elinux.org/BeagleBoardJTAG >From looking at a picture of the JTAG connector on the pocket beagle ( http://uk.farnell.com/beagleboard/bb-pocket/pocket-beagle-board-arm-cortex/dp/2806159 ) , it looks like there are 7 JTAG connectors signals which appear to follow the TI signals as

[beagleboard] Connection to Android tablet

I am collecting data from an ADC chip and saving the data to a file on the Beaglebone Black. Currently the commands are sent through PuTTY on a PC using ssh and then sftp sends the file back which is manually loaded and displayed in a Qt program. My desire is to be able to send a command to the

Re: [beagleboard] Out of space

On 16/01/18 21:19, 'Bernard Champion' via BeagleBoard wrote: > This email message and any accompanying attachments may contain > information that is confidential and is subject to legal privilege. We're not allowed to see your email because it might contain privileged or confidential material. --

[beagleboard] Re: JTAG or OpenOCD

Hi, (Here's a newbie answer so take that for what it's worth). Have only done limited JTAG debugging on the BB-X15 with CCS 7.x - when bringing up the SPL on a custom board with the same Sitara SOC as on the BB-X15. I THINK I recall that only a hand full of the 20 pins (like 7 maybe?)

Re: [beagleboard] Wiznet W5500 ethernet module driver can't install

On Mon, Jan 15, 2018 at 10:59 PM, santosh aiwale wrote: > The Wiznet W5500 is working on SPI with BBB. > I am working on pocket beagle bone using Linux beaglebone 4.4.91-ti-r133. > here is the driver link https://github.com/borg42/w5x00. > also kernel module build not

Re: [beagleboard] Flashing old image with kernel 3.8 on new board

On Tue, Jan 16, 2018 at 10:57 AM, wrote: > We got new BeagleBone Black cards, and when try to flash image I got an > error, > Error: [/dev/mmcblk1] does not exist. > > I sure, it possible. > The question how? Your new BBB contains a newer model of eMMC, this model is not

[beagleboard] Flashing old image with kernel 3.8 on new board

We got new BeagleBone Black cards, and when try to flash image I got an error, Error: [/dev/mmcblk1] does not exist. I sure, it possible. The question how? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

[beagleboard] Re: How to Erase the eMMC

Is there a way to permanently boot from SD without physical access to the board? this means without pressing the boot button, grounding P8.43 or similar. as far as I have tested all the described methods ( remove boot flag, overwrite boot partition) are working only if they are executed from a

[beagleboard] JTAG or OpenOCD

Has anyone had any success with JTAG emulation on the pocket beagle yet? I have both Segger and NI debuggers as well as a variety of adaptors for Other demo boards from tag-connect and others, though I can’t get any of them to work, either because the pads are not aligned or because the

Re: [beagleboard] Re: X15 Boot via USB

Hello Angel, Mine is still collecting dust after my failed attempt at booting off the eSATA and making the modifications you have also done. Very disappointing since it was an expensive purchase. I am also awaiting a solution. The directions on booting from eSATA were not very clear. Good luck!

[beagleboard] Out of space

Hi, I am very new at this. I was copying a project from Robotics Cape and 1/2 way through was told "out of space"? I would like to erase the currently loaded program and start afresh. How do I erase the program and all files off the eMMC? I am using Python3 on Putty and connected via the

Re: [beagleboard] How to make the customer am335x board both wired and wireless network work simultaneously ?

Hi Robert Nelson I figured it out. Due to the uart3 conflict with the eth0. The uart3 section should be removed from BB-BBGW-WL1835-00A0.dts. I removed the line 36 and line 143-148 "fragment@2" and line 178-186 "fragment@4" and made the new dtbo file. It works well. Thank you very much.

[beagleboard] Wiznet W5500 ethernet module driver can't install

The Wiznet W5500 is working on SPI with BBB. I am working on pocket beagle bone using Linux beaglebone 4.4.91-ti-r133. here is the driver link https://github.com/borg42/w5x00. also kernel module build not available. -- For more options, visit http://beagleboard.org/discuss --- You received this

Re: [beagleboard] pru_rproc on latest Stretch IoT image

On Tuesday, 16 January 2018 15:52:23 UTC, RobertCNelson wrote: > > > Gotcha - here is the output after correcting /boot/uEnv.txt: > > > > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > > [sudo] password for debian: > > git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516]

Re: [beagleboard] pru_rproc on latest Stretch IoT image

> Gotcha - here is the output after correcting /boot/uEnv.txt: > > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > [sudo] password for debian: > git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516] > eeprom:[A335BNLT00C03816BBBK190D] > dogtag:[BeagleBoard.org Debian Image

Re: [beagleboard] pru_rproc on latest Stretch IoT image

On Tuesday, 16 January 2018 15:08:51 UTC, RobertCNelson wrote: > > > debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > > > kernel:[4.4.91-ti-r133] > > > > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-9-TI-00A0.dtbo] > > > > > I edited this line: > > >

Re: [beagleboard] pru_rproc on latest Stretch IoT image

> debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh > kernel:[4.4.91-ti-r133] > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-9-TI-00A0.dtbo] > I edited this line: > > uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-9-TI-00A0.dtbo] > >

Re: [beagleboard] pru_rproc on latest Stretch IoT image

On Tuesday, 16 January 2018 14:56:03 UTC, RobertCNelson wrote: > > On Tue, Jan 16, 2018 at 8:12 AM, Hugh Frater > wrote: > > I broke my installation (screwed up node.js and bonescript versions, > stuff > > went bad) so re-flashed my test hardware with the latest Stretch

Re: [beagleboard] pru_rproc on latest Stretch IoT image

On Tue, Jan 16, 2018 at 8:12 AM, Hugh Frater wrote: > I broke my installation (screwed up node.js and bonescript versions, stuff > went bad) so re-flashed my test hardware with the latest Stretch IoT > image... I'm now figuring out how U-Boot overlays work, which seem

[beagleboard] Re: Enabling I2C1 on Beaglebone black

Hello. Did U solve this issue? среда, 28 декабря 2016 г., 9:09:55 UTC+2 пользователь Madhu K написал: > > Hi All, > > I am trying to enable the I2C1 on beaglebone black board. I have written > overlay to enable the i2c1, please verify below snippet and correct me if > anything wrong in that.

[beagleboard] pru_rproc on latest Stretch IoT image

I broke my installation (screwed up node.js and bonescript versions, stuff went bad) so re-flashed my test hardware with the latest Stretch IoT image... I'm now figuring out how U-Boot overlays work, which seem pretty straightforward, just a few changes in uEnv.txt... How the heck do I get

[beagleboard] Re: Beaglebone Black Wireless PRU's (Getting Started)

As you say the problems probably arise because the example on righto.com is for an older debian distribution. If you are using the last Debian release 4.4.91-ti-r133 from 5. Oct. 2017 and you would also accept to write the code for the PRU in C this actual example perhaps can help you.

Re: [beagleboard] Trouble building a configfs for HID device on BBBW

Did you ever get an answer for this. I followed the directions at: https://wiki.tizen.org/USB/Linux_USB_Layers/Configfs_Composite_Gadget/Usage_eq._to_g_hid.ko And am now bumping into the same problem: root@beaglebone:/home/debian/cfg/usb_gadget/g1# pwd /home/debian/cfg/usb_gadget/g1