[beagleboard] Re: Does not detect RTC (ds1307)
Do you have pull-up resistors? --- Graham == On Monday, March 19, 2018 at 8:28:51 AM UTC-5, Paco Velasco wrote: > > When I connect the rtc it does not detect the 68 address (I2C Tool). > > I have test with 2 RTC diferent,and with the BBB I have no problem. > > Anybody knows what could be the problem? Thanks > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/57dfd39c-dde7-4a3f-a9d3-072f535c54d3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] SPI disappears when cape plugged in?
Thanks for the reply, I believe I've already gone into the uEnv.txt and tried to explicitly do things like disable HDMI and enable the two SPI ports, (if I remember right I added those to "enable_partno=" or whatever the syntax was). But when I boot with the cape plugged in it seems to have no effect. -- 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/93374048-9357-45b1-aaa8-a3faa3ae27c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: SPI disappears when cape plugged in?
OK, my possible understanding at this point is this: Cape EEPROM has a name string on it. BBB looks at that name string first and loads the matching file device tree. For some reason, no other device tree overlays are loaded. SPI is not a part of the overlay for this cape (confirmed by looking at their dts on github). I'm not really sure why it wouldn't let me go ahead and load the BB-SPIDEV overlays from user space once the OS is already booted, or totally ignore them in uEnv.txt. But it seems to me the possible solutions are: Add everything I need to the dts for this cape, recompile it and copy it into the right place on my BBB Or, just take the existing compiled cape-universal dtbo and copy it into the file named to match this cape, and let that be what gets loaded. Option #2 seems less tedious for a first crack... Any other thoughts and comments welcome. -- 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/742e49d5-bd08-4bec-800a-3513f48dbd60%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Reading encoder using PRU
Hi everyone, My project requires reading an encoder pulse (1,000,000+ counts/sec) and pulsing a laser (or not) in response to that count. I was wondering if anyone has a way to read in the encoder counts from the eQEP into the PRU in a manner that results in little latency. I am leaning towards using an interrupt associated eQEP0 but I am not quite sure how to implement this. Any help would be greatly appreciated. CJ -- 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/f6b94333-e9d4-4aff-bc04-544b1ff9830e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Beaglebone Black and LCD BB-CAPE-DISP-CT43 and Debian 9.3
Thanks Robert! I would never have guessed that the bootloader in the emmc would/could interfere with the bootloader on the SD card. I now have 9.3 running out of the box from the SD card! Thanks! Aaron -- 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/cb650953-d99b-4e00-9467-8938994b3626%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Cape Manager for U-Boot
"this might have broke something" --> do you mean the >> dtb=am335x-boneblack-overlay.dtb] line? We have ordered a serial cable, I'll get you the boot output as soon as it arrives. Thanks so much for your help and insight on this... On Tuesday, March 20, 2018 at 6:02:57 PM UTC-7, RobertCNelson wrote: > > On Tue, Mar 20, 2018 at 7:48 PM, > > wrote: > > Any ideas? Help is very much appreciated. We'd like to keep our dtbo > info > > in four files rather than one giant one... > > > > > > On Monday, March 19, 2018 at 9:45:03 AM UTC-7, lgil...@tethers.com > wrote: > >> > >> Thanks for responding! Sorry for the delay in my reply, I did not > have > >> access to my BBB over the weekend. > >> > >> One interesting note is that not only do our dts files work > individually, > >> but they also work when combined into one giant dts, so I don't believe > >> there is any issue with their formatting. It's only when we try to > load > >> them as four separate files that we run into problems. > >> > >> Here is the output of the version.sh script: > >> > >> [root@beaglebone]> ./version.sh > >> git:/opt/scripts/:[d36fe9a7be9ebfc872b10a470e904ab4c61c4516] > >> eeprom:[A335BNLT00C00515BBBK0825] > >> dogtag:[BeagleBoard.org Debian Image 2017-10-10] > >> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot > >> 2018.01-2-g9aa111a004] > >> kernel:[4.4.91-ti-r133] > >> nodejs:[v6.11.4] > >> device-tree-override:[dtb= > >> dtb=am335x-boneblack-overlay.dtb] > > This might have broke something.. > > >> uboot_overlay_options:[enable_uboot_overlays=1] > >> > >> > uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/maps_bbb_pwm-00A0.dtbo] > > > >> > uboot_overlay_options:[uboot_overlay_addr5=/lib/firmware/maps_bbb_eqep-00A0.dtbo] > > > >> > uboot_overlay_options:[uboot_overlay_addr6=/lib/firmware/maps_bbb_i2c-00A0.dtbo] > > > >> > uboot_overlay_options:[uboot_overlay_addr7=/lib/firmware/maps_bbb_gpio-00A0.dtbo] > > > > any chance do you have a usb serial adapter you can plug into j1, so > we can what u-boot tires to do with these 4 overlay? > > 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/2fc5da0b-5db2-4aab-a3a2-892a81832821%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: Custom Brd Kern. Boot - Get "Unable to handle kernel paging request at virtual..." Occasionaly
Hi Robert,
We've copied the 572x EVM, reva3 schematic as closely as possible, but then
added some peripherals.
Our custom board is utilizing 4, Micron, MT41K256 512 MiB DDR3 chips for
DDR3. I believe this is on Gerald's BOM for the BB-X15.
Right now our EEPROM is blank. My strategy, for the time being, has been to
ignore the blank EEPROM for now and fool/hard-code the test of the board
type to always return true for our custom board.
Then I added extra conditionals, where board type is tested, to all/most of
the routines in board.c.
When the routines in board.c test positive for our custom board type, we
"mostly" follow the same path that was followed for the BB-X15 in an "older
version" of the 2017.01 u-boot/u-boot-spl. The major difference is we're
loading our own arrays for pad configuration and iodelay in
recalibrate_iodelay in board.c. These arrays were obtained from the TI
pinmux tool and pinmux design for our board.
I have not tuned the IOdelay values from the pinmux tool to account for any
differences in timing between the address and data lines to the DDR3 on the
BB-X15 vs. our custom board.
void emif_get_dmm_regs(const struct dmm_lisa_map_regs **dmm_lisa_regs)
{
.
.
if ( board_is_am572x_custom() )
*dmm_lisa_regs = &beagle_x15_lisa_regs;
.
.
}
Thanks!!
On Tuesday, March 20, 2018 at 8:03:55 PM UTC-5, RobertCNelson wrote:
>
> On Tue, Mar 20, 2018 at 7:23 PM, Jeff Andich > wrote:
> > I cross posted in the TI E2E thread referenced below, since someone else
> > encountered this issue.
> >
> > One thing which comes to mind is, even though our custom board is based
> on
> > the BB-X15/572xEVM, I have not yet "tuned"/re-computed the IO delays for
> > u-boot-spl for our custom board. Rather, I'm re-using the default IO
> delays
> > from the TI pinmux tool (or from the u-boot for the BB-X15).
> >
> > The TI support engineer indicated that "weird things could happen, in
> > certain cases if you don't tune the IO delay values for your custom
> board."
> >
> > Wonder if this is the next, best place to look???
>
> Hi Jeff,
>
> What eeprom value did you program? and did you mirror the memory from
> teh x15 design?
>
> 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/0e932f51-d955-47f8-bcfc-f8f0ada7ca27%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: i2c bus speed
On Wed, Mar 21, 2018 at 12:47 AM, wrote: > I am having the same issue with my BBB. Modifying the device tree with > values that should run the I2C clock to 400 kHz does not seem to change the > speed upon rebooting. I validated that the .dtb was modified by unpacking it > into a .dts again to check if the value was 400 kHz. > > Is this method of modifying the device tree not effective anymore in the > latest images of Debian? Check your serial boot log, are you booting what you expect? 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/CAOCHtYiHuv6JsiO5z%3DL6HBB6MhMU7qdPX%2BxQaAkYonRM03j84g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: i2c bus speed
I am having the same issue with my BBB. Modifying the device tree with values that should run the I2C clock to 400 kHz does not seem to change the speed upon rebooting. I validated that the .dtb was modified by unpacking it into a .dts again to check if the value was 400 kHz. Is this method of modifying the device tree not effective anymore in the latest images of Debian? -- 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/307175c1-931e-492f-aeea-9e8353f5cc84%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: How to get A gui on my beagle bone
On 21/03/18 17:19, Kakarla Srinivas wrote:
> Please check the log and provide the solution.
> Temporary failure resolving 'repos.rcn-ee.com'
In other words, your BeagleBone is unable to reach your nameserver, so
doesn't know who on earth 'repos.rcn-ee.com' is. The solution is to
troubleshoot your Internet connection.
Check:
1. Physical connections, i.e. if using Ethernet, that both ends of the
Ethernet cable indicate a successfully negotiated Ethernet link. I have
no idea looking at this post what you are using whether it be Ethernet,
USB, WiFi or avian carrier, so perhaps in future you might want to
include this information.
2. IP addresses on the BeagleBone. Run `ip addr show` and see what
addresses are assigned. I'm not sure what the BeagleBone's ethernet
connection is called; but assuming it is named `eth0`, try `dhclient
eth0` if you're using DHCP or `ip addr add ${CIDR} dev eth0` for static
IP (${CIDR} is your IP address and prefix length; e.g. 192.168.255.224/24).
3. Routes, if using DHCP, that should be taken care of, but double check
with `ip route show`. If your default route is not there; try `ip route
add default via ${ROUTER_IP}`.
4. Nameserver. `cat /etc/resolv.conf` and have a look. Maybe try
running `echo nameserver 8.8.8.8 > /etc/resolv.conf` and see if you fare
better.
Regards,
--
Stuart Longland (aka Redhatter, VK4MSL)
I haven't lost my mind...
...it's backed up on a tape somewhere.
--
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/2a665eed-22f0-b007-3cc5-2d74957e7a05%40longlandclan.id.au.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Re: How to get A gui on my beagle bone
Hi , I want to install desktop environment on begale bone balck compiled kernel. I tried the script file provide by you.It is not working here is the error message. Please check the log and provide the solution. [sudo] password for debian: Err:1 http://repos.rcn-ee.com/debian stretch InRelease Temporary failure resolving 'repos.rcn-ee.com' Err:2 http://deb.debian.org/debian stretch InRelease Temporary failure resolving 'deb.debian.org' Err:3 http://deb.debian.org/debian stretch-updates InRelease Temporary failure resolving 'deb.debian.org' Err:4 http://deb.debian.org/debian-security stretch/updates InRelease Temporary failure resolving 'deb.debian.org - I tried the below things manually,But not working for me. we are following these steps (https://eewiki.net/display/linuxonarm/BeagleBone ,Deboan 9.3 rootfs and kernel am33x-v4.15 ( stable) ) sudo apt-get install ubuntu-desktop Gnome 3 installation: sudo apt-get install gnome-shell KDE see Kubuntu installation: sudo apt-get install kubuntu-desktop XFCE installation: sudo apt-get install xfce4 LXDE installation: sudo apt-get install lxde Openbox installation: sudo apt-get install openbox Regards, Sree On Sunday, December 22, 2013 at 8:56:42 PM UTC+5:30, RobertCNelson wrote: > > On Sun, Dec 22, 2013 at 9:23 AM, Amalinda J' Gamage > > wrote: > > I have the same problem. some softwares freeze the Ubuntu GUI. Is there > any > > criterian to chose softwares such a way the BBB doest freeze? > > anything libgtk/gnome.. > > Like i said in another thread... Someone needs to debug this, get a > trace right before the system goes down. Something is locking up the > core.. > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a3276c23-8093-43e6-9680-229230990e0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
