Re: [beagleboard] Re: Windows adb driver issue
Try this http://dl.sj.91.com/pcsuite/91update/91assistant_v3.3.12.1236.exe 2014/1/11 Vishveshwar vishveshwarb...@aim.com On Wednesday, January 8, 2014 9:57:40 PM UTC+5:30, Doug Nappier wrote: I am working with Android Jelly bean and am having some adb issues when it comes to Windows 7. I can not get windows 7 to recognize the device as an Android device and can not find it with adb. When I boot into my linux host machine I can use adb to find the beagleboard. I ran lsusb on the device in my linux host and got the following output: Bus 001 Device 011: ID 18d1:9018 Google Inc I read in the TI ADB install guidehttp://processors.wiki.ti.com/index.php/Android_ADB_Setup that you need to add the following lines to you the .inf file: %SingleAdbInterface% = USB_Install, USB\VID_18D1PID_9018 %CompositeAdbInterface% = USB_Install, USB\VID_18D1PID_9018MI_01 That guide is quite old and probably not up-to-date. Have you checked the information the the TI User Guide for the Android version you are using? I think the PIDs have changed. -Vishveshwar When I go to my device manager, where the device is mistakenly being established as a mass storage device, and attempt to point Windows at this new .inf file it gives me the error Windows could not find the driver software for your device Does anyone have any ideas how to fix this. -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Boot failure external abort on non-linefetch in cpsw_probe with any image after Wi-Fi install
Thanks for your comments @Loren. It's quite odd that the board boots fine with old kernels and not with now ones, isn't it?. I tried the images available at http://www.armhf.com/index.php/boards/beaglebone-black/: - Ubuntu Saucy 13.10http://www.armhf.com/index.php/boards/beaglebone-black/#saucy and - Ubuntu Precise 12.04.3 LTShttp://www.armhf.com/index.php/boards/beaglebone-black/#precise pretty much the same result as you get: ** *[2.477446] registered taskstats version 1* *[2.538597] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6* *[2.545147] davinci_mdio 4a101000.mdio: no live phy, scanning all* *[2.552441] davinci_mdio: probe of 4a101000.mdio failed with error -5* *[2.559885] Detected MACID = bc:6a:29:84:8d:3a* *[2.565340] Unhandled fault: external abort on non-linefetch (0x1008) at 0xd0894000* *[2.573651] Internal error: : 1008 [#1] SMP ARM* *[2.578448] Modules linked in:* *[2.581705] CPU: 0Not tainted (3.8.13-bone30 #1)* *[2.587076] PC is at cpsw_probe+0x528/0xbc8* *[2.591518] LR is at ioremap_page_range+0xd8/0x16c* *[2.596595] pc : [c03f23f4]lr : [c02e6168]psr: a113* *[2.596595] sp : cf05de38 ip : cf04d250 fp : cf42f298* *[2.608723] r10: 0001 r9 : cf42f540 r8 : d0894000* *[2.614252] r7 : cf113800 r6 : r5 : cf113810 r4 : cf42f000* *[2.621154] r3 : r2 : r1 : 4a100e13 r0 : d0894000* *[2.628061] Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment kernel* *[2.635788] Control: 10c5387d Table: 80004019 DAC: 0015* *[2.641865] Process swapper/0 (pid: 1, stack limit = 0xcf05c240)* *[2.648216] Stack: (0xcf05de38 to 0xcf05e000)* *[2.652831] de20: * *[2.661486] de40: cf447c08 cf42f540 c014c2f0 0020 cf447c88* *[2.670140] de60: cf447c08 cf447c08 0008 c014c1e0 cf447c08 cf112488 cf446d40* *[2.678794] de80: c014cba0 cf0474b8 c005e608 0003 cf112488 * *[2.687446] dea0: c0a171ec cf113810 cf113818 cf113810 cf113844 c0a171ec c098c5b4 c09a9dc0* *[2.696099] dec0: cf05c008 c037c480 cf113810 cf113844 c098c5b4* *[2.704751] dee0: c037c66c c098c5b4 c037c604 c037acbc cf047478 cf111c80* *[2.713405] df00: c098c5b4 cf446d40 c0981ff0 c037bc44 c07ee6aa c07ee6aa c098c5b4* *[2.722060] df20: c090ebe8 c09218d4 c0901ed4 c037cbb8 0007 c090ebe8 c09218d4 c0901ed4* *[2.730716] df40: c09a9dc0 c0008894 c0901ed4 f442 c0921900 0008 0007 c090ebe8* *[2.739369] df60: c09218d4 c09a9dc0 c09a9dc0 00f1 c090ebf0 c08dc918 0007 0007* *[2.748020] df80: c08dc270 c05fd740 * *[2.756672] dfa0: c05fd748 c000d478 * *[2.765323] dfc0: * *[2.773974] dfe0: 0013 ffeffae6 5fbf* *[2.782667] [c03f23f4] (cpsw_probe+0x528/0xbc8) from [c037c480] (driver_probe_device+0xa4/0x1e4)* *[2.792340] [c037c480] (driver_probe_device+0xa4/0x1e4) from [c037c66c] (__driver_attach+0x68/0x8c)* *[2.802304] [c037c66c] (__driver_attach+0x68/0x8c) from [c037acbc] (bus_for_each_dev+0x70/0x84)* *[2.811885] [c037acbc] (bus_for_each_dev+0x70/0x84) from [c037bc44] (bus_add_driver+0xdc/0x218)* *[2.821463] [c037bc44] (bus_add_driver+0xdc/0x218) from [c037cbb8] (driver_register+0x9c/0x124)* *[2.831044] [c037cbb8] (driver_register+0x9c/0x124) from [c0008894] (do_one_initcall+0x8c/0x150)* *[2.840729] [c0008894] (do_one_initcall+0x8c/0x150) from [c08dc918] (kernel_init_freeable+0x108/0x1cc)* *[2.850979] [c08dc918] (kernel_init_freeable+0x108/0x1cc) from [c05fd748] (kernel_init+0x8/0xe4)* *[2.860665] [c05fd748] (kernel_init+0x8/0xe4) from [c000d478] (ret_from_fork+0x14/0x3c)* *[2.869505] Code: e59f1650 ebfe1d58 ead1 e58485c0 (e5982000) * *[2.875956] ---[ end trace 85aa0dcf7be9c2ab ]---* *[2.881634] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b* I'll try to set compile the kernel myself and play a bit with the modules to see if there's something that can be done. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] debian: test images (2014-01-10)
On 01/10/2014 04:11 PM, Robert Nelson wrote: It's Friday and everyone is probally kicking back and enjoying a cold beverage... Well enough of that crap, time to start actually testing something... ;) First, for tracking please report all bugs to: http://bugs.elinux.org/projects/debian-image-releases Still not confirmed on the bug tracker, but I see this panic on halt: root@beaglebone:~# halt Broadcast message from root@beaglebone (ttyO0) (Fri Jan 10 17:17:21 2014): The system is going down for system halt NOW! root@beaglebone:~# Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes... Unmounting file systems. Unmounted /sys/fs/fuse/connections. Unmounted /dev/mqueue. Unmounted /sys/kernel/debug. Unmounted /sys/kernel/security. Disabling swaps. Detaching loop devices. Detaching DM devices. [ 40.057138] (NULL device *): gadget not registered. [ 40.072972] Power down. [ 40.079180] Kernel panic - not syncing: Attempted to kill init! exitcode=0x [ 40.079180] [ 40.088830] [c0013270] (unwind_backtrace+0x0/0xe0) from [c0630514] (panic+0x84/0x1e0) [ 40.097438] [c0630514] (panic+0x84/0x1e0) from [c0040364] (do_exit+0x470/0x88c) [ 40.105501] [c0040364] (do_exit+0x470/0x88c) from [c004ed30] (sys_reboot+0x128/0x1b4) [ 40.114106] [c004ed30] (sys_reboot+0x128/0x1b4) from [c000d580] (ret_fast_syscall+0x0/0x30) [ 40.123242] drm_kms_helper: panic occurred, switching back to text console Regards, Dave. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. attachment: dave.vcf
[beagleboard] Re: Interface BBB with camera
My problem is solved, and I can tell u all, Logitech c525 works fine I am using Logitech c525. It supports yuyv, mjpg and not h.264. So I was unable to use ./capture correctly. I was able to resolve my problem by using ./capture -c 600 -o output.raw In this case, the default setting for output format was used. I set it too mjpg using root@beaglebone:/dev# v4l2-ctl –set-fmt-video=pixelformat=1 To resolve my 2nd doubt, I compiled the code, which I forgot to do. Use – gcc –O2 –Wall `pkg-config –cflags –libs libv4l2` grabber.c –o grabber Then I was able to execute with no problems. (Don’t forget to press Ctrl+C to end frame capturing process, else your directory will be full of grabber001.ppm, grabber002.ppm, etc) -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: FreeBSD on BeagleBoard-xm
I think I got the answer now. The OMAP3530 and the DM3730 are compatible regarding the software running on it. Therefore, the freeBSD port for omap3530 SHOULD support the current bbxm. I will keep this updated if I can try on the bbxm. On Monday, January 21, 2013 6:17:56 PM UTC-5, Flavio Alves wrote: Hello all, Does anybody could advice me how to prepare an FreeBSD image from sources for a Beagle-xM? I could not find any tutorial or guide to do that. Best regards, Flavio -- Flavio de Castro Alves Filho flavio...@gmail.com javascript: www.linuxembarcado.com Twitter: http://twitter.com/#!/fraviofii LinkedIn profile: www.linkedin.com/in/flaviocastroalves -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Userspace RAM access
Thanks, Jack. Where is this documented so that I don't have to bother the board next time? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Cant boot kernel from TFTP
Hi all, i have beagleboard xM and using ti-sdk-beagleboard-06.00.00.00 I'm able to boot from SD/MMC card. However cant boot from TFTP with the same image. It just hangs after Uncompressing Linux... done, booting the kernel. Do you have any idea? What's wrong with it? Why it works with SD/MMC and not working from RAM? You can see logs below. PS : Do not care about filesystem mount failure. U-Boot SPL 2012.04.01 (Jan 11 2014 - 05:04:29) Texas Instruments Revision detection unimplemented OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img U-Boot 2012.04.01 (Jan 11 2014 - 05:04:29) OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In:serial Out: serial Err: serial Beagle xM Rev C No EEPROM on expansion board Die ID #26a600029ff8016842c81402800e Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 gpio: pin 173 (gpio 173) value is 0 gpio: pin 4 (gpio 4) value is 0 SD/MMC found on device 0 reading uEnv.txt ** Unable to read uEnv.txt from mmc 0:1 ** reading uImage 3413096 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Linux-3.3.7 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3413032 Bytes = 3.3 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK XIP Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Booting Linux on physical CPU 0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.3.7 (bugraaydogar@ubuntu) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 Sat Jan 11 05:40:07 PST 2014 [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine: OMAP3 Beagle Board [0.00] Reserving 12582912 bytes SDRAM for VRAM [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) [0.00] Clocking rate (Crystal/Core/MPU): 26.0/400/800 MHz [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 126720 [0.00] Kernel command line: console=ttyO2,115200n8 mpurate=auto buddy=none camera=none vram=12M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] allocated 1048576 bytes of page_cgroup [0.le=memory' option if you don't want memory cgroups [0.00] Memory: 499MB = 499MB total [0.00] Memory: 498404k/498404k available, 25884k reserved, 0K highmem [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xe080 - 0xff00 ( 488 MB) [0.00] lowmem : 0xc000 - 0xe000 ( 512 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .text : 0xc0008000 - 0xc061770c (6206 kB) [0.00] .init : 0xc0618000 - 0xc064e000 ( 216 kB) [0.00] .data : 0xc064e000 - 0xc069e800 ( 322 kB) [0.00].bss : 0xc069e824 - 0xc06d8034 ( 231 kB) [0.00] NR_IRQS:474 [0.00] IRQ: Found an INTC at 0xfa20 (revision 4.0) with 96 interrupts [0.00] Total of 96 interrupts on 1 active controller [0.00] OMAP clockevent source: GPTIMER12 at 32768 Hz [0.00] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms [0.00] Console: colour dummy device 80x30 [0.000122] Calibrating delay loop... 651.20 BogoMIPS (lpj=2543616) [0.038330] pid_max: default: 32768 minimum: 301 [0.038482] Mount-cache hash table entries: 512 [0.038787] Initializing cgroup subsys cpuacct [0.038787] Initializing cgroup subsys memory [0.038818] Initializing cgroup subsys devices [0.038848] Initializing cgroup subsys freezer [0.038848] Initializing cgroup subsys blkio [0.038848] Initializing cgroup subsys perf_event [0.038940] CPU: Testing write buffer coherency: ok [0.039123] Setting up static identity map for 0x80461c08 - 0x80461c60 [0.039703] devtmpfs: initialized [0.041046] omap_hwmod: usbtll_fck: missing clockdomain for usbtll_fck. [0.073089] print_constraints: dummy: [0.073303] NET: Registered protocol family 16 [0.073455]
[beagleboard] Re: Cant boot kernel from TFTP
Sorry guys, I have found the reason. It just doesnt read uEnv.txt when i try to boot from TFTP. After setting bootargs value it booted from RAM. Have a nice weeekend. On Saturday, January 11, 2014 7:31:49 PM UTC+2, Buğra AYDOĞAR wrote: Hi all, i have beagleboard xM and using ti-sdk-beagleboard-06.00.00.00 I'm able to boot from SD/MMC card. However cant boot from TFTP with the same image. It just hangs after Uncompressing Linux... done, booting the kernel. Do you have any idea? What's wrong with it? Why it works with SD/MMC and not working from RAM? You can see logs below. PS : Do not care about filesystem mount failure. U-Boot SPL 2012.04.01 (Jan 11 2014 - 05:04:29) Texas Instruments Revision detection unimplemented OMAP SD/MMC: 0 reading u-boot.img reading u-boot.img U-Boot 2012.04.01 (Jan 11 2014 - 05:04:29) OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz OMAP3 Beagle board + LPDDR/NAND I2C: ready DRAM: 512 MiB NAND: 0 MiB MMC: OMAP SD/MMC: 0 *** Warning - readenv() failed, using default environment In:serial Out: serial Err: serial Beagle xM Rev C No EEPROM on expansion board Die ID #26a600029ff8016842c81402800e Net: Net Initialization Skipped No ethernet found. Hit any key to stop autoboot: 0 gpio: pin 173 (gpio 173) value is 0 gpio: pin 4 (gpio 4) value is 0 SD/MMC found on device 0 reading uEnv.txt ** Unable to read uEnv.txt from mmc 0:1 ** reading uImage 3413096 bytes read Booting from mmc ... ## Booting kernel from Legacy Image at 80007fc0 ... Image Name: Linux-3.3.7 Image Type: ARM Linux Kernel Image (uncompressed) Data Size:3413032 Bytes = 3.3 MiB Load Address: 80008000 Entry Point: 80008000 Verifying Checksum ... OK XIP Kernel Image ... OK OK Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.00] Booting Linux on physical CPU 0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.3.7 (bugraaydogar@ubuntu) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 Sat Jan 11 05:40:07 PST 2014 [0.00] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7d [0.00] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache [0.00] Machine: OMAP3 Beagle Board [0.00] Reserving 12582912 bytes SDRAM for VRAM [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk ) [0.00] Clocking rate (Crystal/Core/MPU): 26.0/400/800 MHz [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 126720 [0.00] Kernel command line: console=ttyO2,115200n8 mpurate=auto buddy=none camera=none vram=12M omapfb.mode=dvi:640x480MR-16@60 omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] allocated 1048576 bytes of page_cgroup [0.le=memory' option if you don't want memory cgroups [0.00] Memory: 499MB = 499MB total [0.00] Memory: 498404k/498404k available, 25884k reserved, 0K highmem [0.00] Virtual kernel memory layout: [0.00] vector : 0x - 0x1000 ( 4 kB) [0.00] fixmap : 0xfff0 - 0xfffe ( 896 kB) [0.00] vmalloc : 0xe080 - 0xff00 ( 488 MB) [0.00] lowmem : 0xc000 - 0xe000 ( 512 MB) [0.00] modules : 0xbf00 - 0xc000 ( 16 MB) [0.00] .text : 0xc0008000 - 0xc061770c (6206 kB) [0.00] .init : 0xc0618000 - 0xc064e000 ( 216 kB) [0.00] .data : 0xc064e000 - 0xc069e800 ( 322 kB) [0.00].bss : 0xc069e824 - 0xc06d8034 ( 231 kB) [0.00] NR_IRQS:474 [0.00] IRQ: Found an INTC at 0xfa20 (revision 4.0) with 96 interrupts [0.00] Total of 96 interrupts on 1 active controller [0.00] OMAP clockevent source: GPTIMER12 at 32768 Hz [0.00] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms [0.00] Console: colour dummy device 80x30 [0.000122] Calibrating delay loop... 651.20 BogoMIPS (lpj=2543616) [0.038330] pid_max: default: 32768 minimum: 301 [0.038482] Mount-cache hash table entries: 512 [0.038787] Initializing cgroup subsys cpuacct [0.038787] Initializing cgroup subsys memory [0.038818] Initializing cgroup subsys devices [0.038848] Initializing cgroup subsys freezer [0.038848] Initializing cgroup subsys blkio [0.038848] Initializing cgroup subsys
Re: [beagleboard] Re: USB transmission speed
Ok, so with 3.13.0-rc6-bone2.8 and CONFIG_USB_TI_CPPI41_DMA=y # CONFIG_MUSB_PIO_ONLY is not set I'm getting about 14MB/s which is much better than before but still less than with the TI v3.2 Kernel. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Re: debian: test images (2014-01-10)
Is this beta specifically for the Beaglebones or should it work on the Beagleboard xM? I tried the setup_sdcard.sh method, substituting --uboot beagle_xm, but the resulting card didn't get very far in the boot process. -Michael On Friday, January 10, 2014 5:11:09 PM UTC-5, RobertCNelson wrote: It's Friday and everyone is probally kicking back and enjoying a cold beverage... Well enough of that crap, time to start actually testing something... ;) First, for tracking please report all bugs to: http://bugs.elinux.org/projects/debian-image-releases So go forward and test the first beta release. There are 3 files on the web server, depending on what you want to do. Using the same standard procedure found here: http://elinux.org/Beagleboard:Updating_The_Software http://rcn-ee.net/deb/testing/2014-01-10/ An eMMC flasher which can be installed to any 2GB or greater microSD card. [BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz] http://rcn-ee.net/deb/testing/2014-01-10/BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz 5cb3f88ae14cbcb94604786484f96309http://rcn-ee.net/deb/testing/2014-01-10/BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz5cb3f88ae14cbcb94604786484f96309 BBB-eMMC-flasher-debian-7.3-2014-01-10-2gb.img.xz It takes about 10-15 Minutes to dd microSD (2GB), 15 minutes to flash eMMC (look for full 4 LED's) 4GB standalone image that can be flashed to any 4GB or greater. [bone-debian-7.3-2014-01-10-4gb.img.xz] http://rcn-ee.net/deb/testing/2014-01-10/bone-debian-7.3-2014-01-10-4gb.img.xz 096915309ec4a8fe41b1e8076a0c436bhttp://rcn-ee.net/deb/testing/2014-01-10/bone-debian-7.3-2014-01-10-4gb.img.xz096915309ec4a8fe41b1e8076a0c436b bone-debian-7.3-2014-01-10-4gb.img.xz It takes about 20-30 Minutes to dd microSD (4GB) Finally one of my classic setup_sdcard.sh. [debian-7.3-console-armhf-2014-01-10.tar.xz] http://rcn-ee.net/deb/testing/2014-01-10/debian-7.3-console-armhf-2014-01-10.tar.xz 526adb40799a8e060df020ed1cd47c12http://rcn-ee.net/deb/testing/2014-01-10/debian-7.3-console-armhf-2014-01-10.tar.xz526adb40799a8e060df020ed1cd47c12 debian-7.3-console-armhf-2014-01-10.tar.xz Note for users who use my classic setup_sdcard.sh script, here is the magic options to get the beaglebone project files + systemd. sudo ./setup_sdcard.sh --mmc /dev/sdX --uboot bone --beagleboard.org-production --enable-systemd To rebuild git clone git://github.com/beagleboard/image-builder.git cd image-builder git checkout bb.org-v2014.01.10 -b tmp ./beagleboard.org_image.sh Thoughts/rants/list/etc? Go Test! -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: debian: test images (2014-01-10)
On Sat, Jan 11, 2014 at 4:37 PM, Michael Long nika...@gmail.com wrote: Is this beta specifically for the Beaglebones or should it work on the Beagleboard xM? I tried the setup_sdcard.sh method, substituting --uboot beagle_xm, but the resulting card didn't get very far in the boot process. Just the BeagleBone... The 'script' supports many different boards, however this image only contains the kernel for the BeagleBone.. The xM is already fully supported here: http://elinux.org/BeagleBoardDebian#Demo_Image This beta is specifically addressing: http://beagleboard.org/blog/2014-01-04-happy-new-year/ 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] sys_5v powering humidity sensor
HI All, I'm trying to trouble shoot why my two HIH4001 (or 4003) humidity sensors died after a couple of days of being connected to the beagle bone in my current config. I've got one connected to AIN5 and the other to 6 (central pin -- output voltage), via voltage dividers to knock the voltage down below 1.8 V. Output pins are tied to ground via 80K resistors (pulldown). Ground runs to BBB ground, and is also tied to AGND. Power is supplied via SYS_5v --- I thought this would give me a regulated supply. The measurements with a multimeter look good. After a couple of days the sensors were providing constant 2.6 V as output and are unresponsive. Can anyone see anything I am doing wrong with this setup? Thanks for your help. Kind regards Matt -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] Custom kernel with Angstrom
Anyone know how build a custom kernel with/for Angstrom using the OE/bitbake instructions? 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] freertos on bbxm
Hi all, In addition to create a freertos port for bbxm, I am THINKING to integrate the mechanism of freertos to the android system, which is running on bbxm. In other words, to integrate the freertos to an android app running on bbxm. Is that realistic or any suggestions? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
[beagleboard] beagleboard-xm start up problem
hi, from the day i bought bb-xm , its not booting up, the sd card shipped with the board and many angstrom images i tried didnt worked out.. i even tried Ubuntu but no luck. i am using lcd monitor,hdmi -dvi connector,straight through cable .. when i am connecting its showing no signal to monitor, and its not detecting keyboard or mouse. unable to understand whats the problem,plz plz help.. my project submission date is near.. its urgent.. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] Re: Unexpected Reboots on BBB Debian with 3.2 Kernel
Hi Mahammad, If you try ls -lt /dev/, can you find *mmcblk1?* Regards, Ali J. Ghandour www.alighandour.org “Intellectual growth should commence at birth and cease only at death.” On 8 January 2014 10:42, Mahammad Mostafa whilet...@hotmail.com wrote: Hi Ali.. I was using ubuntu 12.10: ubuntu-12.10-console-armhf-2013-04-26 Kernel is 3.2.0 that comes with chipsee capacitive 7lcd. It is based on the TI sdk with a few changes to support the LCD on BBB. Best Regards Mahammad On Wed, Jan 8, 2014 at 8:38 AM, Ali ghandour@gmail.com wrote: Hi Mahammad, Which 3.2 kernel you are using? And what version of Ubuntu? On Tuesday, January 7, 2014 10:00:23 PM UTC+2, Mahammad wrote: Hi There... Did anyone succeed running 3.2 from the eMMC on BBB? I managed to run ubuntu with 3.2 on BBB but from sdcard only.. it can't see the eMMC.. not even as a storage. 'lsblk' only shows the sdcard. Any idea how to support the eMMC under kernel 3.2? I feel it could be a backport effort to the eMMC driver... any help will be appreciated. Best Regards Mahammad On Thursday, December 12, 2013 8:34:23 PM UTC+2, Ali wrote: I have noticed that your are not supporting 3.2 kernel. But Maxim mentioned that he was able to run your 3.2 kernel on the BBB. That's why I was asking Maxim to provide me with the patched 3.2 kernel that he was able to run on the BBB. On Thursday, December 12, 2013 8:26:51 PM UTC+2, RobertCNelson wrote: On Thu, Dec 12, 2013 at 12:24 PM, Ali ghando...@gmail.com wrote: Thanks Robert and Maxim. I started again with a fresh git clone and was able to compile a new 3.2 kernel. When I tried booting the compiled kernel on a BBB, it hits the following error related to EEProm Configuration Option variable: . No daughter card found [1.103912] at24 1-0050: 32768 byte 24c256 EEPROM, writable, 64 bytes/write [1.119110] Board config.name: A335BNLT0A5C3513BBBK0428 [1.127502] Board name: A335BNLT [1.130889] Board version: 0A5C [1.134155] SKU: �� [1.136718] The error message above indicates that there is an issue with [1.136718] the EEPROM or the EEPROM contents. After verifying the EEPROM [1.136718] contents, if any, refer to the am335x_evm_setup function in the [1.136718] arch/arm/mach-omap2/board-am335xevm.c file to modify the board [1.136749] initialization code to match the hardware configuration . Laughs, no it's working perfectly, ! As previous stated, I never added BBB support to my 3.2 based kernel, I consider 3.2 long dead. AKA: DO NOT USE my 3.2 branch on the BBB, use 3.8... 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 a topic in the Google Groups BeagleBoard group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/H2R8dCj8xyI/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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/H2R8dCj8xyI/unsubscribe. To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- 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. For more options, visit https://groups.google.com/groups/opt_out.
