Re: [beagleboard] UART data sliced in two piece ....
Hi,
On Fri, Jan 3, 2014 at 4:08 PM, Micka mickamus...@gmail.com wrote:
Ok,
Well, the baudrate is at 38400, the distribution is the Ubuntu from
Robert C Nelson ( 3.8.13 bone 30 ), the driver is the omap . I've modified
a little bit the driver to add RS485 support ( see the patch attached ) ,
the only major modification that I've done is to add :
+ wait_for_xmitr(up);
+if (up-rs485.flags SER_RS485_ENABLED) {
+ if(up-rs485.delay_rts_after_send0){
+udelay(up-rs485.delay_rts_after_send);
+ }
+ /* Disable RS485 TX EN */
+ val = (up-rs485.flags SER_RS485_RTS_AFTER_SEND) ? 1 :
0;
+ gpio_set_value(up-rs485.gpio_pin, val);
+}
in the function serial_omap_stop_tx .
It works most of the time, but for an unknown reason there is this weird
behavior .
Any tips ? lead to follow ?
How much data are you writing?
Are you doing it with a single call to write?
If you're doing multipe calls to write then its quite possible that a
context switch is allowing another task to run and delaying your second
write.
--
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.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] usb-serial device doesn't appear in /dev. Need a udev rule?
On 01/03/2014 10:52 PM, loonsailor wrote: 'ERROR: could not insert 'ti_usb_3410_5052': Operation not permitted'. Thanks for the help. This is a bit new to me. Try to do that using sudo or as root :) sudo modprobe ti_usb_3410_5052 If you want a more permanent solution that survives reboots, you can either put that module into /etc/modules or setup udev to load it on insertion. regards, Nuno -- http://aeminium.org/nuno/ -- 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] Angstrom Abandoned for BBB? Rumor + a Rant
On Mon, Dec 23, 2013 at 4:21 PM, Terry Storm terrystor...@gmail.com wrote: A little birdy told me that Angstrom has been abandoned for the BBB ?? I wouldn't say abandoned. If there are things you need fixed, it is still possible for us to make bug fixes in the image. Also, I haven't heard anything from Koen that says Angstrom won't continue or won't continue to support all the Beagles. It is true he's not being paid by CircuitCo to work on Angstrom for Beagle anymore. If this is the case, and seems to be the case as there hasnt been an update for the Angstrom image for the BBB for quite some time, and there are still a number of issues with LCD CAPES which have not yet been resolved... Not an official release, but I just checked the site and saw new image builds as recent as Jan 3. What is the 'new' standard distribution for the BBB going to be now? We are working with Robert Nelson's Debian images to try to produce an out-of-box experience on par with the Angstrom images. Once we have a few more features in, namely an updated Cloud9 IDE that works with node 0.10, then we'll push out a beta image broadly for testing. You can already grab Debian test images today. The script to build the image is at https://github.com/beagleboard/image-builder. Us LCD CAPE users are having a hard time getting touch working reliably for a wide range of LCD Capes on the market. I know most of us don't know enough to fix problems ourselves or know what the problem is actually caused by, and we don't know if anyone is working on these issues or if they are being ignored or pass over, or if 'the people' who do know what is going on just don't have time to look at them etc? The LCD Cape vendors should push support for their hardware into https://github.com/beagleboard/kernel and https://github.com/beagleboard/cape-firmware. CircuitCo does so. Github pull requests are the best way to do so. Starting to really dislike this whole 'open' community based thing especially when there are issues and no one wants to own them. These issues have been reported for many months, and we are no further ahead. Can you be specific? Does anyone know of anyone who is working on the LCD CAPE touch issue which is a problem on Angstrom (and maybe others which use the same driver/source?) Terry -- 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] usb-serial device doesn't appear in /dev. Need a udev rule?
On Sat, Jan 4, 2014 at 8:22 AM, Nuno Sucena Almeida n...@aeminium.org wrote: On 01/03/2014 10:52 PM, loonsailor wrote: 'ERROR: could not insert 'ti_usb_3410_5052': Operation not permitted'. Thanks for the help. This is a bit new to me. Try to do that using sudo or as root :) sudo modprobe ti_usb_3410_5052 If you want a more permanent solution that survives reboots, you can either put that module into /etc/modules or setup udev to load it on insertion. Can you confirm this resolved your issue? regards, Nuno -- http://aeminium.org/nuno/ -- 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.
[beagleboard] Re: chipsee beaglebone lcd/dvi expansion kernel support
Hi Luke... if you are still looking for the DVD.. I think one post here has a link to download the linux branch from the DVD. If you are looking for the full dvd it is about 4GB compressed. Let me know if you still need it so I can upload it for you. And please make sure it is not copyrighted. On Thursday, December 26, 2013 12:47:39 AM UTC+2, sol...@gmail.com wrote: Dear all, I am new to this forum. My friend helped me to buy the Chipsee touch LCD from China but it comes without a DVD/CD! Is there any link that I can download it as Chipsee people are not very helpful at all in my case! Thanks very much! Kind regards, Luke tripzero於 2012年5月22日星期二UTC+1上午6時27分07秒寫道： Anyone gotten the chipsee lcd cape working with ubuntu or debian? cape found here: http://www.tigal.com/product/2559 chipsee's website: http://www.chipsee.com/beaglebone-exp.html -- 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] usb-serial device doesn't appear in /dev. Need a udev rule?
When I sudo, I no longer get an error on the modprobe (duh!), but it still doesn't make a device at the /dev level, like /dev/ttyusb0 or similar. Should it? Or should I just have my software, which expects a serial device (it's talking to a weather station) directly access /dev/bus/usb/001/003. If I want a tty-type device, is it enough to 'ln -s /dev/bus/... /dev/ttyUSB', either manually or with udev, or does a usb-serial device need some sort of pseudo-driver for serial protocols? Thanks again! On Saturday, January 4, 2014 6:23:44 AM UTC-8, Jason Kridner wrote: On Sat, Jan 4, 2014 at 8:22 AM, Nuno Sucena Almeida nu...@aeminium.orgjavascript: wrote: Try to do that using sudo or as root :) sudo modprobe ti_usb_3410_5052 -- 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] Happy New Year Beaglers!
http://beagleboard.org/blog/2014-01-04-happy-new-year/ Here we are, 2014. Expect a big year for Beagle! Unfortunately, I have to start out with an apology. LinuxGizmos.com recently hopped on the news that over 100,000 BeagleBone Blacks have now been sold. When they contacted me to confirm, I blundered a bit by repeating and confirming what I thought was a fairly broadly shared rumor---that we are looking to soon shift the Linux distribution that ships in the flash of the boards from Angstrom to Debian. The blunder wasn't the confirming of the news, but rather not doing a good job at communicating to the community about this move better ahead of time. It didn't help that I was taking off for vacation where my Internet access is spotty at best. So, I owe you all a big apology, but I hope you are still excited about the news. So what's coming? The big news is a shift to Debian in the on-board flash. You'll still be able to flash Angstrom if you want to use that and myself and others in the community will still be rather happy to help you with Angstrom-related questions, but the feeling is that we'll get a much broader support base if we have new users encounter Debian first on the upcoming boards. The exact date of the switch-over hasn't been determined. Gerald had most recently given me and everyone involved a deadline of giving him an image by the end of January, but we are currently bottlenecked by the updated version of Cloud9 IDE. I have been playing with a beta of version 3 and I find it to be a huge improvement that will enable us to provide support for C compilation within the IDE using plug-ins. The new version also runs on node 0.10, making it much easier to work with recent Debian builds. Before any switch in production happens, there will be a fairly complete beta image shared broadly for testing. How similar will the experience be? If you aren't a heavy Linux user and just do a few things from the command-line and use the Cloud9 IDE, the experience will be pretty similar, but I hope you'll find it somewhat improved. If you are a more seasoned developer, I probably don't need to answer the question, because you are already likely to be somewhat experienced with Debian. All of the key features you expect should be there. We have a handful of performance goals to try to keep the experience on-par with Angstrom. One is a boot time target of under 10 seconds. Using the typical boot strategy for Debian Wheezy without any significant optimization, Robert Nelson observed that boot time was more like 30 seconds. By switching over to systemd, as is used by typical Angstrom builds, boot time dropped to around 16 seconds. We'll be spending a bit of time trying to improve this between now and the beta image. Space on the flash will likely be very similar, due to trying to provide similar functionality. The builds are currently quite a bit smaller, but Robert is still adding in items to bring in feature parity. BoneScript will still be included in the out-of-box experience to help quickly prove out the various hardware interfaces and help people learn about wiring up hardware. I've fixed most of the issues with getting BoneScript onto other distros besides Angstrom and am planning to soon release version 0.2.4 that already has improved support for switching pin modes and reading pin states. The USB flash drive and USB networking features will still be included, as well as the driver install guide, self-hosted web-based tutorial and the previously mentioned Cloud9 IDE. Over time, there will be more promotion of the Userspace Arduino project that provides an easy-to-learn C API for rapid prototyping of hardware projects. Of course, the boards will continue to ship with a C/C++ compiler and build tools, libraries, and a number of interpreters, such as Python. I'd love to include the Adafruit BBIO Python library, so I'll be contacting them to see if they'll approve that. I've also been chatting quite a few times with the Erlang folks, so that is something that has a good likelihood of being included. The kernel is likely to be the same one included currently in Angstrom, the customized 3.8.x kernel. However, if the release slips enough, there is a reasonable chance we'll be switching over to one of either the 3.12 or 3.13-rc kernels. A good amount of attention will be paid to having a good set of drivers and firmware for USB wifi adapters included as this was a pain point for some people in the past. How to contribute? The script for building the image is currently hosted at https://github.com/beagleboard/image-builder . Hop on the mailing list with questions about running the script and send Github pull requests if you have suggested improvements. Contributing to the kernel continues to be the same athttps://github.com/beagleboard/kernel . I am overdue, however, at writing up how to contribute Cape DTS firmware sources that configure Cape hardware automatically using devicetree. The new repository
Re: [beagleboard] current solution for JTAG debugging of beagleboard xm?
On Fri, 3 Jan 2014, Mark Lazarewicz wrote: Well if you prefer non open source solution and prefer a feature rich IDE(CCS5.X) backed by the vendor (TI) @ $79 xdsv2usb is the only way. I trust your google skills starting from here http://elinux.org/BeagleBoard http://processors.wiki.ti.com/index.php/XDS100 code composer jtag support uses a .gel file to initialize processor and memory so you will have to google around for the Beagle Board one or uses the bootloader to initialize things and then grab control I dont recommend that approach The industry trend now is jtag over usb with no need for a connector the bone white supports this the Beagleboard and Panda and BBB need connectors admitting i know next to nothing about JTAG debugging, can you clarify a couple things? first, i need to do some JTAG debugging *strictly* on a beagleboard xM in a few weeks and, for that, it seems that my most convenient solution is tin can tools' flyswatter 2 and adapter (which i believe i even have somewhere buried in a drawer, which makes it *really* convenient. :-) next, given that i have that, is there still value in purchasing a TI XDS100v2? i have no problem investing in more toys as long as they provide additional value. i guess i really need to find a good JTAG tutorial somewhere and start reading ... rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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] How to install mutt in angstrom?
Hello everyone, i am trying to make an script to send my dinamic IP address trought email but i need mutt to doing it. Can someone explain me how i can install this? 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] Flashing eMMC or Booting from microSD
While Flashing eMMC or Booting from microSD, we need a USB based card reader. Can I use my cell phone instead to have access to microSD? Has anyone tried? Or you recommend a USB based card reader? Share if you experienced any problems using cell phone -- 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: BBB refuses restart
Go my BBB 2 days back I have an issue, when I plug BBB via USB, the Safely remove hardware symbol doesnt appear...I dont know what to do then, so I removed it directly. Will this cause any problems? Is there some problem as Safely remove hardware symbol doesnt appear? Going as per your problem, why do you use the power switch? I dont touch it at all -- 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] grrrrrr ... fedora 20 has a broken kpartx command
just in case anyone else runs into this, i was putting together some notes for the aforementioned beagleboard xM-based embedded linux course and went to test kpartx for mounting the partitions inside a bootable image file and ran smack into this: https://bugzilla.redhat.com/show_bug.cgi?id=1039136 rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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: Deleted the files that comes inside the beaglebone black. Now computer can't detect it.
Exact procedure on - http://elinux.org/Beagleboard:Updating_The_Software#Flashing_the_eMMC -- 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] Cloning a SD-card ends up with an unbootable partition?!
Hello Robert, many thanks for your hints. My linux-box is an open-suse system kernel 3.11.6-4 running inside an Oracle VM 4.3.6. I investigated this UUID-topic more careful but ended up even more confused. As I cloned the cards using dd I expected them to be identical in every bit (aside the cards' different sizes that should not affect partitions cloned by dd). And in deed - for both cards I get the following identical output: # ls -lh /dev/disk/by-id/usb* lrwxrwxrwx 1 root root 9 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0 - ../../sdb lrwxrwxrwx 1 root root 10 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0-part1 - ../../sdb1 lrwxrwxrwx 1 root root 10 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0-part2 - ../../sdb2 lrwxrwxrwx 1 root root 10 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0-part3 - ../../sdb3 # blkid /dev/sda1 /dev/sda1: UUID=1a741a3f-1d6e-49f7-958b-a83e9ac4107f TYPE=swap # blkid /dev/sda2 /dev/sda2: UUID=a8748c5a-2bfa-4f9a-ac4f-b0c314ded6eb TYPE=ext4 PTTYPE= dos # blkid /dev/sda3 /dev/sda3: UUID=5a41fb0b-d553-4f35-abdf-26a0210b4826 TYPE=ext4 It seems that the UUID is preserved by dd but still the second (cloned) card does not boot. Is there any other reason for not booting the clone you could imagine? Best regards, Christian -- 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] Cloning a SD-card ends up with an unbootable partition?!
Hello Robert, many thanks for your hints. My linux-box is an open-suse system kernel 3.11.6-4 running inside an Oracle VM 4.3.6. I investigated this UUID-topic more careful but ended up even more confused. As I cloned the cards using dd I expected them to be identical in every bit (aside the cards' different sizes that should not affect partitions cloned by dd). And in deed - for both cards I get the an identical output: # ls -lh /dev/disk/by-id/usb* lrwxrwxrwx 1 root root 9 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0 - ../../sdb lrwxrwxrwx 1 root root 10 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0-part1 - ../../sdb1 lrwxrwxrwx 1 root root 10 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0-part2 - ../../sdb2 lrwxrwxrwx 1 root root 10 4. Jan 17:52 /dev/disk/by-id/usb- Mass_Storage_Device_125C20100726-0:0-part3 - ../../sdb3 # blkid /dev/sdb1 /dev/sdb1: UUID=1a741a3f-1d6e-49f7-958b-a83e9ac4107f TYPE=swap # blkid /dev/sdb2 /dev/sdb2: UUID=a8748c5a-2bfa-4f9a-ac4f-b0c314ded6eb TYPE=ext4 PTTYPE= dos # blkid /dev/sdb3 /dev/sdb3: UUID=5a41fb0b-d553-4f35-abdf-26a0210b4826 TYPE=ext4 It seems that the UUID is preserved by dd but still the second (cloned) card does not boot. Is there any other reason for not booting the clone you could imagine? Best regards, Christian -- 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] C/C++ Program to control onboard leds/GPIO using Visual Studio,GDB
Thanks Williams..I have found A LINK http://visualgdb.com/tutorials/beaglebone/ ..the hello world pgm worked successfully..i want to know about gpio control using the same and on board led control which however did not work in my case..Also need to know how to run the hello world pgm without compiling it each time..any help regarding the same would be appreciated On Saturday, January 4, 2014 4:14:45 AM UTC+5:30, William Hermans wrote: BTW, probably not what you want to hear, but you can use a GCC toolchain from within visual studio via using make file projects. It is however a big hassle. I've done it myself for the MSP430 Launchpad v1.5. toolchain. Debigging does not work like this, but can be made to work using a perl script, and monitoring STD error / STD out From within the Windows environment. Search around a bit there is a code Project article about it. On Fri, Jan 3, 2014 at 3:41 PM, William Hermans yyr...@gmail.comjavascript: wrote: I have never actually used visual GDB but in theory it should work. You should contact the developer behind visualGDB. Initial support may not be there but once he finds out about he BBB if he has not already. He'd be a fool not to add support. On Fri, Jan 3, 2014 at 7:49 AM, Jishnu M Thampan jish...@gmail.comjavascript: wrote: Is there any way to control onboard leds or access gpios using the visual gdb method? also what more is to be done for the application to start automatically without compilation each 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...@googlegroups.com javascript:. 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.
[beagleboard] vi editor in beaglebone to run an opencv program
I have an opencv code. can I use the vi editor available in the angstrom to write the program and use gcc to compile the same.? is any linking of opencv libraries necessary ? if so what is the procedure? -- 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] the inconvenience of CRs in the uEnv.txt file
incredibly pedantic note here and not sure why i never noticed this before but i downloaded the current shipping BB-xM image as linked to from here: http://elinux.org/Beagleboard:BeagleBoard-xM created my micro SD card, my xM booted just fine, but when i went to display the kernel command line that had been used, this is what i saw: # cat /proc/cmdline omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait # turns out that only the tail end of the actual kernel command line is displayed because the uEnv.txt file that was sourced contains CR characters at end of line which causes redraws of the poor command line so that only the last part shows. you can see this with: # less /proc/cmdline where the ^M characters show up that cause the annoyance. it's still parsed correctly by u-boot, it just reminds me to tell my students to not create their uEnv.txt file in a DOS editor. :-) rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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: Which build would you recommend?
Just thought I would mention, I am making more progress :)
Using the debian release is nice as like when compiling on the RPI, I could
install PCM and espeak, by simply doing apt-get install and the packages
were installed. On Angstrom I had to find sources build and install. No
big deal but it is nice.
Next up is to start connecting it up to hardware. XBee will be easy,
connect to TTL usart like before, as it is 3.3v. But not sure which way I
will go to talk to SSC-32. Could USB to serial adapter or could connect to
another USART through level shifter. The SSC-32 is a 5v ATmega based
board.
Another thing I want to investigate more is in my code, I like to reference
devices by a name such as: /dev/ttyXBee instead of by some actual hardware
name. When it is /dev/ttyUSBn it also had the complication that if you
rearrange things and/or add devices your device may change names. ttyUSB0
today may be ttyUSB1 tomorrow... So I used UDEV rules to do the mapping.
Something like:
SUBSYSTEM==tty, ATTRS{idVendor}==0403, ATTRS{idProduct}==6001,
ATTRS{serial}==A800fclo, SYMLINK+=ttyXBEE
But at the time was not sure of the best way to simply map ttyO1 to
ttyXBee. When I tried it the last time was not sure, so I simply added a
line to my .profile file that did something like: ln -s /dev/ttyO1
/dev/ttyXBee
But my gut tells me there is a cleaner way. So will probably play a little
with this, before I simply fall back to doing what I did before.
Again having fun
Kurt
P.S - the Wifi has stopped twice now. Could be related that I am powering
board through USB (1 amp wall wart) instead of DC power input. Will
change soon
--
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] need for sd card in bbb
On Sat, Jan 4, 2014 at 1:12 PM, Jishnu M Thampan jishnu...@gmail.com wrote: Since the bbb shipped one already containsangstrom as the os, is there any need to add an sd card ? my requirement is to run an opencv code which involves real time image processing As long as the available free space on eMMC is sufficient for your application you should be fine. -- 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] vi editor in beaglebone to run an opencv program
On Sat, Jan 4, 2014 at 1:09 PM, Jishnu M Thampan jishnu...@gmail.com wrote: I have an opencv code. can I use the vi editor available in the angstrom to write the program and use gcc to compile the same.? is any linking of opencv libraries necessary ? if so what is the procedure? Yes. The editor has nothing to do with your opencv code. You would need to follow the same procedure for compiling and linking against the opencv library as you would on a typical desktop environment. Search the archives for the exact steps. -- 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: Prevent linux from clearing GPIO pins during boot
On Fri, Dec 27, 2013 at 4:45 AM, Ives van der Flaas ives@gmail.com wrote: Some more information: I'm running the BeagleBone Black with a 3.8.13-bone33 kernel. Adding the HWMOD_INIT_NO_RESET flag to gpio0 and gpio1 structs in arch/arm/mach-omap2/omap_hwmod_33xx_data.c similar to [1] should work. [1]https://git.ti.com/~mugunthanvnm/ti-linux-kernel/mugunth-connectivity-linux-feature-tree/commit/e43edd44fd2174cdabd459c1d97c7f0d512d1b04 -- 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] Pogramming in C.
On Tue, Dec 24, 2013 at 9:38 AM, mayuresh salelkar mayureshsalel...@gmail.com wrote: Hey there. I am working on BBB for my college project. i would like to interface various sensors to the board using GPIO and want to program in c/c++. Do i need to flash the eMMc with linux image or can i directly start programming using putty software? Also can you tell me about any tutorials for the programming,if possible?? thanks. If you can get a console via PuTTY you already have linux running. Have a look at http://derekmolloy.ie/beaglebone-controlling-the-on-board-leds-using-c/ for a sample program and search the archives for more info. -- 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] Prevent linux from clearing GPIO P8_12 and P8_13 on boot
On Mon, Dec 23, 2013 at 8:06 AM, Ives van der Flaas ives@gmail.com wrote: Hi everyone, I'm building a product based on the BeagleBone Black that uses LEDs to indicate the current status. These LEDs are connected to P8_12 and P8_13 (GPIO 44 and 23) and need to be turned on during boot. I succeeded in setting the relevant pins to high in uBoot, but as soon as the linux kernel boots, the pins are immediately cleared. After boot I can regain control through a device tree overlay, but the GPIO pins I mentioned before need to be high during the entire boot process. Any ideas on what driver/module is responsible for this behaviour and how I can prevent linux from clearing the relevant GPIO ports? I think i already replied to another post on this. In case you are looking for an explanation on who's clearing the pins, that would be init code of the kernel which resets all the peripherals to get them to a known state. Have a look at the other reply on how to avoid 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.
Re: [beagleboard] Flashing eMMC or Booting from microSD
On Sat, Jan 4, 2014 at 11:35 AM, Pariyan Shah pariyans...@gmail.com wrote: While Flashing eMMC or Booting from microSD, we need a USB based card reader. Can I use my cell phone instead to have access to microSD? Has anyone tried? Or you recommend a USB based card reader? IMHO you're complicating things unnecessarily. Just buy a card reader. -- 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] Angstrom Abandoned for BBB? Rumor + a Rant
On Friday, January 3, 2014 9:57:12 PM UTC+1, John Syne wrote: Have you tried Xenomai? I looked at using F28M35C Concerto devices and I always seemed to run out of memory when adding all the pieces I needed such as network stack, security, etc. Not yet. I am not that experienced with Linux and find it already complicated to get Linux without Xenomai to work on the BBB. So I prefer to keep things simple separated and communicate with my Cortex M3 or M4 via USB, SPI, or whatever. Anguel -- 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] Angstrom Abandoned for BBB? Rumor + a Rant
On Saturday, January 4, 2014 3:20:07 PM UTC+1, Jason Kridner wrote: We are working with Robert Nelson's Debian images to try to produce an out-of-box experience on par with the Angstrom images. Once we have a few more features in, namely an updated Cloud9 IDE that works with node 0.10, then we'll push out a beta image broadly for testing. It is good news that you are working with Robert on Debian. IMHO this is the way to go. Robert is doing so much for the BBB community. TI should support him in every way they can. It is a fact that BBB developer resources are extremely limited. So efforts should really concentrate on getting the serious stuff working properly, I mean the basic things a serious developer needs: kernel + stability + Qt, because Linux is used for touch GUIs, not as a desktop replacement. For me Linux Desktops, Cloud9, USB networking etc. is just a big waste of precious development time, unless the intention is to fool new customers that the BBB is something easy to use. This is definitely not the case and will never be! Just have a look at all the posts in this thread. The LCD Cape vendors should push support for their hardware into https://github.com/beagleboard/kernel and https://github.com/beagleboard/cape-firmware. CircuitCo does so. Github pull requests are the best way to do so. The problem with touch was that someone ported the ADC / touchscreen stuff from an upcoming TI kernel to the 3.8 kernel and some things broke. Then this somebody just did not have the time to fix the bugs and they stayed there. I already discussed this in another thread. Anguel -- 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] couple questions about trying flyswatter 2 on beagle xm from fedora 20
following up on my earlier post on JTAG debugging, i dug into my supplies and found my flyswatter 2 and associated cables and started following the instructions here: http://elinux.org/Flyswatter2_Beagleboard_XM_How_To and ran into a couple issues. the first is that, if you look at the photos on that page, there's a discrepancy between pics 4 and 5, as pic 4 shows the 10-pin ribbon cable being connected, then suddenly that cable has vanished in pic 5, and is replaced by the serial cable in pic 6, which is kind of confusing. the bigger issue is an apparent bug in openocd. there is an openocd package for fedora 20, which i installed with yum -- it's version 0.7.0, which appears to be the latest version. if i then connect the USB cable and run the appropriate openocd command, i get: # openocd -f interface/flyswatter2.cfg -f board/ti_beagleboard_xm.cfg -c init -c reset init Open On-Chip Debugger 0.7.0 (2013-09-07-16:51) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : only one transport option; autoselect 'jtag' adapter speed: 10 kHz Warn : dm37x.dsp: huge IR length 38 Runtime Error: embedded:startup.tcl:20: Unknown target type cortex_a, try one of arm7tdmi, arm9tdmi, arm920t, arm720t, arm966e, arm946e, arm926ejs, fa526, feroceon, dragonite, xscale, cortex_m, cortex_a8, cortex_r4, arm11, mips_m4k, avr, dsp563xx, dsp5680xx, testee, avr32_ap7k, or hla_target in procedure 'script' at file embedded:startup.tcl, line 58 at file /usr/share/openocd/scripts/board/ti_beagleboard_xm.cfg, line 5 in procedure 'target' called at file /usr/share/openocd/scripts/target/amdm37x.cfg, line 144 in procedure 'ocd_bouncer' at file embedded:startup.tcl, line 20 # Unknown target type cortex_a? if i go to line 144 of the config file, sure enough, i find: target create $_TARGETNAME cortex_a -chain-position $_CHIPNAME.dap should that instead say cortex_a8? is this really a bug in openocd? has anyone else tried this? rday -- Robert P. J. Day Ottawa, Ontario, CANADA hhttp://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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] couple questions about trying flyswatter 2 on beagle xm from fedora 20
... snip ... oh, wait, i found the additional elinux page: http://elinux.org/OpenOCD_Config_Files with apparently newer versions of some of the files, including the very file that gave me trouble. i will continue reading ... rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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] current solution for JTAG debugging of beagleboard xm?
On 1/4/14, 7:42 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: On Fri, 3 Jan 2014, Mark Lazarewicz wrote: Well if you prefer non open source solution and prefer a feature rich IDE(CCS5.X) backed by the vendor (TI) @ $79 xdsv2usb is the only way. I trust your google skills starting from here http://elinux.org/BeagleBoard http://processors.wiki.ti.com/index.php/XDS100 code composer jtag support uses a .gel file to initialize processor and memory so you will have to google around for the Beagle Board one or uses the bootloader to initialize things and then grab control I dont recommend that approach The industry trend now is jtag over usb with no need for a connector the bone white supports this the Beagleboard and Panda and BBB need connectors admitting i know next to nothing about JTAG debugging, can you clarify a couple things? first, i need to do some JTAG debugging *strictly* on a beagleboard xM in a few weeks and, for that, it seems that my most convenient solution is tin can tools' flyswatter 2 and adapter (which i believe i even have somewhere buried in a drawer, which makes it *really* convenient. :-) next, given that i have that, is there still value in purchasing a TI XDS100v2? i have no problem investing in more toys as long as they provide additional value. i guess i really need to find a good JTAG tutorial somewhere and start reading ... Hi Robert, It really depends on what you are trying to achieve. If you want to understand the workings of JTAG, then flyswatter is a good solution. If like the rest of us you just want to debug u-boot or kernel code, then XDS100V2 or XDS200 together with CCSV5 is a good solution. One thing to note, although you can debug Linux Kernel code, CCSV5 isn¹t kernel aware so there are limitations in what you can do. Strangely, CCSV4 was Linux Kernel aware, but TI decided that CCSV5 stay as close to the standard Eclipse IDE as possible and avoid extensive customization required for making it Linux Kernel aware. Also, with the addition of DWARF4, it is now possible to see most of the local variables. If you want kernel aware debugging, then I suggest you use ARM DS-5 or Lauterbach, but these are expensive solutions. I have also used PEEDI which is a very good solutions and is Linux Kernel aware and uses standard Eclipse IDE. Regards, John rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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] Angstrom Abandoned for BBB? Rumor + a Rant
From: Anguel anguel.stan...@gmail.com Reply-To: beagleboard@googlegroups.com Date: Saturday, January 4, 2014 at 3:09 PM To: beagleboard@googlegroups.com Cc: jason.krid...@hangerhead.com Subject: Re: [beagleboard] Angstrom Abandoned for BBB? Rumor + a Rant On Saturday, January 4, 2014 3:20:07 PM UTC+1, Jason Kridner wrote: We are working with Robert Nelson's Debian images to try to produce an out-of-box experience on par with the Angstrom images. Once we have a few more features in, namely an updated Cloud9 IDE that works with node 0.10, then we'll push out a beta image broadly for testing. It is good news that you are working with Robert on Debian. IMHO this is the way to go. Robert is doing so much for the BBB community. TI should support him in every way they can. It is a fact that BBB developer resources are extremely limited. So efforts should really concentrate on getting the serious stuff working properly, I mean the basic things a serious developer needs: kernel + stability + Qt, because Linux is used for touch GUIs, not as a desktop replacement. For me Linux Desktops, Cloud9, USB networking etc. is just a big waste of precious development time, unless the intention is to fool new customers that the BBB is something easy to use. This is definitely not the case and will never be! Just have a look at all the posts in this thread. Actually, Cloud9 together with DojoToolKit is amazing for developing Web based GUI. Using websockets makes the GUI very responsive. The LCD Cape vendors should push support for their hardware into https://github.com/beagleboard/kernel and https://github.com/beagleboard/cape-firmware. CircuitCo does so. Github pull requests are the best way to do so. The problem with touch was that someone ported the ADC / touchscreen stuff from an upcoming TI kernel to the 3.8 kernel and some things broke. Then this somebody just did not have the time to fix the bugs and they stayed there. I already discussed this in another thread. Use Capacitive based touchscreen. These interface via USB. Anguel -- 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: Which build would you recommend?
Using the debian release is nice as like when compiling on the RPI, I
could install PCM and espeak, by simply doing apt-get install and the
packages were installed. On Angstrom I had to find sources build and
install. No big deal but it is nice.
Actually, it is a hugely big deal. With the packages already built there
should be some minimal testing already done that you wont get when you
build it yourself.
Just as a for instance, I had the need for Nodejs on my BBB's( still do
actually ), and I was running Wheezy with no actual apt-gettable package.
No big deal I thought, the Nodejs github page has instructions for building
Nodejs from source . . . my first attempt failed, but I quickly found older
instructions that gave me some insight to a single command line switch to
make Nodejs compile for ARM . .. With this step out of the way I proceeded
to get a Nodejs package manager working, compiled in the sources, etc, got
it installed, and then went to download a common package. The package
manager started pulling in x86 compatible only code . . .
Anyway, none of this was a super huge hassle by its self, but by the time I
got everything worked out and running the way I wanted, 2-3 days had passed.
Very glad to see you seem to be pleased with how Debian is working for you
! I felt the same way, and still do.
On Sat, Jan 4, 2014 at 12:41 PM, KurtE ku...@rockisland.com wrote:
I will answer my own question, on the off chance someone else is wanting
to do the same. Actually I did it two ways:Another thing.
One example /etc/udev/rules.d/99-tty-serial.rules Looks like:
SUBSYSTEM==tty, KERNEL==ttyO1, SYMLINK+=ttyXBEE
SUBSYSTEM==tty, KERNEL==ttyO2, SYMLINK+=ttySSC-32
I also was able to do it like:
SUBSYSTEM==tty, ATTRS{port}==0x0, ATTRS{line}==1, SYMLINK+=ttyXBEE
SUBSYSTEM==tty, ATTRS{port}==0x0, ATTRS{line}==2, SYMLINK+=ttyRCLAW
Earlier I was using a Roboclaw motor controller on this.
Kurt
--
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.
[beagleboard] lcd3, lcd4, lcd7 status
Do the LCD3, LCD4, LCD7 by Circuitco all now support the black with a current software build. What issues am I likely to encounter? Thanks, Eric -- 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] C/C++ Program to control onboard leds/GPIO using Visual Studio,GDB
There is an awful lot of room for the what-if factor Jishnu. Pretty much we would need to know an exact step by step process( that you've followed ), and possibly some knowledge of visualGDB / Visual Studio as well. So if you can tell us what it is you're trying to do, and the exact steps you've taken to try and achieve this. Well then we'd have a better chance at helping you. On Sat, Jan 4, 2014 at 11:04 AM, Jishnu M Thampan jishnu...@gmail.comwrote: Thanks Williams..I have found A LINK http://visualgdb.com/tutorials/beaglebone/ ..the hello world pgm worked successfully..i want to know about gpio control using the same and on board led control which however did not work in my case..Also need to know how to run the hello world pgm without compiling it each time..any help regarding the same would be appreciated On Saturday, January 4, 2014 4:14:45 AM UTC+5:30, William Hermans wrote: BTW, probably not what you want to hear, but you can use a GCC toolchain from within visual studio via using make file projects. It is however a big hassle. I've done it myself for the MSP430 Launchpad v1.5. toolchain. Debigging does not work like this, but can be made to work using a perl script, and monitoring STD error / STD out From within the Windows environment. Search around a bit there is a code Project article about it. On Fri, Jan 3, 2014 at 3:41 PM, William Hermans yyr...@gmail.com wrote: I have never actually used visual GDB but in theory it should work. You should contact the developer behind visualGDB. Initial support may not be there but once he finds out about he BBB if he has not already. He'd be a fool not to add support. On Fri, Jan 3, 2014 at 7:49 AM, Jishnu M Thampan jish...@gmail.comwrote: Is there any way to control onboard leds or access gpios using the visual gdb method? also what more is to be done for the application to start automatically without compilation each 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...@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. -- 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] Cloning a SD-card ends up with an unbootable partition?!
Hello folks, forget about that SuSE-image http://en.opensuse.org/HCL:BeagleBoard-xM I fell into trouble with and stick closely to Robet's Ubuntuhttp://www.elinux.org/BeagleBoardUbuntu#Demo_Imagewhich works and allows cloning the easy way. Following those instructions allows cloning without pain; best way to do it, I suppose. Best regards, Christian -- 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] current solution for JTAG debugging of beagleboard xm?
Just curious, but why would we need to buy TI specific JTAG emulators, and software ? Honestly there has to be a better solution. Last I looked a single seat for CCS was $400 . . . that is a bit pricey . . . On Sat, Jan 4, 2014 at 5:13 PM, John Syne jsyne...@us-power.com wrote: On 1/4/14, 7:42 AM, Robert P. J. Day rpj...@crashcourse.ca wrote: On Fri, 3 Jan 2014, Mark Lazarewicz wrote: Well if you prefer non open source solution and prefer a feature rich IDE(CCS5.X) backed by the vendor (TI) @ $79 xdsv2usb is the only way. I trust your google skills starting from here http://elinux.org/BeagleBoard http://processors.wiki.ti.com/index.php/XDS100 code composer jtag support uses a .gel file to initialize processor and memory so you will have to google around for the Beagle Board one or uses the bootloader to initialize things and then grab control I dont recommend that approach The industry trend now is jtag over usb with no need for a connector the bone white supports this the Beagleboard and Panda and BBB need connectors admitting i know next to nothing about JTAG debugging, can you clarify a couple things? first, i need to do some JTAG debugging *strictly* on a beagleboard xM in a few weeks and, for that, it seems that my most convenient solution is tin can tools' flyswatter 2 and adapter (which i believe i even have somewhere buried in a drawer, which makes it *really* convenient. :-) next, given that i have that, is there still value in purchasing a TI XDS100v2? i have no problem investing in more toys as long as they provide additional value. i guess i really need to find a good JTAG tutorial somewhere and start reading ... Hi Robert, It really depends on what you are trying to achieve. If you want to understand the workings of JTAG, then flyswatter is a good solution. If like the rest of us you just want to debug u-boot or kernel code, then XDS100V2 or XDS200 together with CCSV5 is a good solution. One thing to note, although you can debug Linux Kernel code, CCSV5 isn¹t kernel aware so there are limitations in what you can do. Strangely, CCSV4 was Linux Kernel aware, but TI decided that CCSV5 stay as close to the standard Eclipse IDE as possible and avoid extensive customization required for making it Linux Kernel aware. Also, with the addition of DWARF4, it is now possible to see most of the local variables. If you want kernel aware debugging, then I suggest you use ARM DS-5 or Lauterbach, but these are expensive solutions. I have also used PEEDI which is a very good solutions and is Linux Kernel aware and uses standard Eclipse IDE. Regards, John rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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. -- 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] couple questions about trying flyswatter 2 on beagle xm from fedora 20
On Sat, Jan 4, 2014 at 6:34 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: following up on my earlier post on JTAG debugging, i dug into my supplies and found my flyswatter 2 and associated cables and started following the instructions here: http://elinux.org/Flyswatter2_Beagleboard_XM_How_To and ran into a couple issues. the first is that, if you look at the photos on that page, there's a discrepancy between pics 4 and 5, as pic 4 shows the 10-pin ribbon cable being connected, then suddenly that cable has vanished in pic 5, and is replaced by the serial cable in pic 6, which is kind of confusing. Yes, PIC4 and 5 are slightly confusing and incorrect. the bigger issue is an apparent bug in openocd. there is an openocd package for fedora 20, which i installed with yum -- it's version 0.7.0, which appears to be the latest version. if i then connect the USB cable and run the appropriate openocd command, i get: # openocd -f interface/flyswatter2.cfg -f board/ti_beagleboard_xm.cfg -c init -c reset init Open On-Chip Debugger 0.7.0 (2013-09-07-16:51) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : only one transport option; autoselect 'jtag' adapter speed: 10 kHz Warn : dm37x.dsp: huge IR length 38 Runtime Error: embedded:startup.tcl:20: Unknown target type cortex_a, try one of arm7tdmi, arm9tdmi, arm920t, arm720t, arm966e, arm946e, arm926ejs, fa526, feroceon, dragonite, xscale, cortex_m, cortex_a8, cortex_r4, arm11, mips_m4k, avr, dsp563xx, dsp5680xx, testee, avr32_ap7k, or hla_target in procedure 'script' at file embedded:startup.tcl, line 58 at file /usr/share/openocd/scripts/board/ti_beagleboard_xm.cfg, line 5 in procedure 'target' called at file /usr/share/openocd/scripts/target/amdm37x.cfg, line 144 in procedure 'ocd_bouncer' at file embedded:startup.tcl, line 20 # Unknown target type cortex_a? if i go to line 144 of the config file, sure enough, i find: target create $_TARGETNAME cortex_a -chain-position $_CHIPNAME.dap should that instead say cortex_a8? is this really a bug in openocd? has anyone else tried this? Yes, and it used to work. Did the cfg file get patched for cortex_a. I'd also recommend NOT using the distros OpenOCD, but rather using the latest version in OpenOCDs Git repo. rday -- Robert P. J. Day Ottawa, Ontario, CANADA hhttp://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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] couple questions about trying flyswatter 2 on beagle xm from fedora 20
On Sat, 4 Jan 2014, Bill Traynor wrote: On Sat, Jan 4, 2014 at 6:34 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: following up on my earlier post on JTAG debugging, i dug into my supplies and found my flyswatter 2 and associated cables and started following the instructions here: http://elinux.org/Flyswatter2_Beagleboard_XM_How_To and ran into a couple issues. the first is that, if you look at the photos on that page, there's a discrepancy between pics 4 and 5, as pic 4 shows the 10-pin ribbon cable being connected, then suddenly that cable has vanished in pic 5, and is replaced by the serial cable in pic 6, which is kind of confusing. Yes, PIC4 and 5 are slightly confusing and incorrect. the bigger issue is an apparent bug in openocd. there is an openocd package for fedora 20, which i installed with yum -- it's version 0.7.0, which appears to be the latest version. if i then connect the USB cable and run the appropriate openocd command, i get: # openocd -f interface/flyswatter2.cfg -f board/ti_beagleboard_xm.cfg -c init -c reset init Open On-Chip Debugger 0.7.0 (2013-09-07-16:51) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : only one transport option; autoselect 'jtag' adapter speed: 10 kHz Warn : dm37x.dsp: huge IR length 38 Runtime Error: embedded:startup.tcl:20: Unknown target type cortex_a, try one of arm7tdmi, arm9tdmi, arm920t, arm720t, arm966e, arm946e, arm926ejs, fa526, feroceon, dragonite, xscale, cortex_m, cortex_a8, cortex_r4, arm11, mips_m4k, avr, dsp563xx, dsp5680xx, testee, avr32_ap7k, or hla_target in procedure 'script' at file embedded:startup.tcl, line 58 at file /usr/share/openocd/scripts/board/ti_beagleboard_xm.cfg, line 5 in procedure 'target' called at file /usr/share/openocd/scripts/target/amdm37x.cfg, line 144 in procedure 'ocd_bouncer' at file embedded:startup.tcl, line 20 # Unknown target type cortex_a? if i go to line 144 of the config file, sure enough, i find: target create $_TARGETNAME cortex_a -chain-position $_CHIPNAME.dap should that instead say cortex_a8? is this really a bug in openocd? has anyone else tried this? Yes, and it used to work. Did the cfg file get patched for cortex_a. I'd also recommend NOT using the distros OpenOCD, but rather using the latest version in OpenOCDs Git repo. i just tried to build openocd from the git repo and, when all was said and done, i was right back where i started -- with openocd complaining about an unknown target type of cortex_a. i'll try this again tomorrow after a good night's sleep, but i would be interested in whether anyone else can get this to work on 64-bit fedora 20 to talk to the beagleboard xm. more tomorrow ... rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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] couple questions about trying flyswatter 2 on beagle xm from fedora 20
On Sat, Jan 4, 2014 at 10:11 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: On Sat, 4 Jan 2014, Bill Traynor wrote: On Sat, Jan 4, 2014 at 6:34 PM, Robert P. J. Day rpj...@crashcourse.ca wrote: following up on my earlier post on JTAG debugging, i dug into my supplies and found my flyswatter 2 and associated cables and started following the instructions here: http://elinux.org/Flyswatter2_Beagleboard_XM_How_To and ran into a couple issues. the first is that, if you look at the photos on that page, there's a discrepancy between pics 4 and 5, as pic 4 shows the 10-pin ribbon cable being connected, then suddenly that cable has vanished in pic 5, and is replaced by the serial cable in pic 6, which is kind of confusing. Yes, PIC4 and 5 are slightly confusing and incorrect. the bigger issue is an apparent bug in openocd. there is an openocd package for fedora 20, which i installed with yum -- it's version 0.7.0, which appears to be the latest version. if i then connect the USB cable and run the appropriate openocd command, i get: # openocd -f interface/flyswatter2.cfg -f board/ti_beagleboard_xm.cfg -c init -c reset init Open On-Chip Debugger 0.7.0 (2013-09-07-16:51) Licensed under GNU GPL v2 For bug reports, read http://openocd.sourceforge.net/doc/doxygen/bugs.html Info : only one transport option; autoselect 'jtag' adapter speed: 10 kHz Warn : dm37x.dsp: huge IR length 38 Runtime Error: embedded:startup.tcl:20: Unknown target type cortex_a, try one of arm7tdmi, arm9tdmi, arm920t, arm720t, arm966e, arm946e, arm926ejs, fa526, feroceon, dragonite, xscale, cortex_m, cortex_a8, cortex_r4, arm11, mips_m4k, avr, dsp563xx, dsp5680xx, testee, avr32_ap7k, or hla_target in procedure 'script' at file embedded:startup.tcl, line 58 at file /usr/share/openocd/scripts/board/ti_beagleboard_xm.cfg, line 5 in procedure 'target' called at file /usr/share/openocd/scripts/target/amdm37x.cfg, line 144 in procedure 'ocd_bouncer' at file embedded:startup.tcl, line 20 # Unknown target type cortex_a? if i go to line 144 of the config file, sure enough, i find: target create $_TARGETNAME cortex_a -chain-position $_CHIPNAME.dap should that instead say cortex_a8? is this really a bug in openocd? has anyone else tried this? Yes, and it used to work. Did the cfg file get patched for cortex_a. I'd also recommend NOT using the distros OpenOCD, but rather using the latest version in OpenOCDs Git repo. i just tried to build openocd from the git repo and, when all was said and done, i was right back where i started -- with openocd complaining about an unknown target type of cortex_a. i'll try this again tomorrow after a good night's sleep, but i would be interested in whether anyone else can get this to work on 64-bit fedora 20 to talk to the beagleboard xm. more tomorrow ... I'll give it a try as well tomorrow, or Monday. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- 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] usb-serial device doesn't appear in /dev. Need a udev rule?
The Startech device, with the TI chipset, continues to have the same problem. I've tried a couple of other converters, Keyspan and Trendnet, both of which use the Prolific chipset, and they do work, making both /dev/serial devices and /dev/ttyUSB0. It may be fixable with the Startech converter, but since the other converters work straight out of the box, I'm just going to use one of them and move on to the next step of making my system work. Thanks for the help, Nuno! On Saturday, January 4, 2014 9:48:07 AM UTC-8, Nuno wrote: On 01/04/2014 10:22 AM, loonsailor wrote: When I sudo, I no longer get an error on the modprobe (duh!), but it still doesn't make a device at the /dev level, like /dev/ttyusb0 or similar. Should it? Or should I just have my software, which expects a serial device (it's talking to a weather station) directly access /dev/bus/usb/001/003. If I want a tty-type device, is it enough to 'ln -s /dev/bus/... /dev/ttyUSB', either manually or with udev, or does a usb-serial device need some sort of pseudo-driver for serial protocols? Thanks again! Hi, you might want to take a look at 'dmesg' to see if a device is created when inserting the kernel module. This is what I get when connecting a pl2303 based usb-rs232 adapter: - (desktop x86 machine): ~$ uname -a Linux antec 3.8.0-34-generic #49-Ubuntu SMP Tue Nov 12 18:00:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ~$ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID:Ubuntu Description:Ubuntu 13.04 [83848.138366] usb 2-1.8.6: new full-speed USB device number 8 using ehci-pci [83848.231040] usb 2-1.8.6: New USB device found, idVendor=067b, idProduct=2303 [83848.231045] usb 2-1.8.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [83848.231047] usb 2-1.8.6: Product: USB-Serial Controller [83848.231050] usb 2-1.8.6: Manufacturer: Prolific Technology Inc. [83848.231337] pl2303 2-1.8.6:1.0: pl2303 converter detected [83848.232879] usb 2-1.8.6: pl2303 converter now attached to ttyUSB0 - (beaglebone black) ~$ uname -a Linux bb2 3.8.13-bone28 #1 SMP Fri Sep 13 01:11:14 UTC 2013 armv7l armv7l armv7l GNU/Linux ~$ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 13.10 [ 472.737991] usb usb1: usb wakeup-resume [ 472.738086] usb usb1: usb auto-resume [ 472.738138] hub 1-0:1.0: hub_resume [ 472.738259] hub 1-0:1.0: port 1: status 0101 change 0001 [ 472.840661] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 472.840787] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 472.946041] usb 1-1: new full-speed USB device number 2 using musb-hdrc [ 473.065944] usb 1-1: default language 0x0409 [ 473.066357] usb 1-1: udev 2, busnum 1, minor = 1 [ 473.066401] usb 1-1: New USB device found, idVendor=067b, idProduct=2303 [ 473.066439] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 473.066473] usb 1-1: Product: USB-Serial Controller [ 473.066505] usb 1-1: Manufacturer: Prolific Technology Inc. [ 473.071233] usb 1-1: usb_probe_device [ 473.071294] usb 1-1: configuration #1 chosen from 1 choice [ 473.072221] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 473.080129] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 473.080247] hub 1-0:1.0: port 1 enable change, status 0103 [ 473.175207] usbcore: registered new interface driver usbserial [ 473.175427] usbcore: registered new interface driver usbserial_generic [ 473.175638] usbserial: USB Serial support registered for generic [ 473.193055] usbcore: registered new interface driver pl2303 [ 473.193317] usbserial: USB Serial support registered for pl2303 [ 473.193446] pl2303 1-1:1.0: usb_probe_interface [ 473.193487] pl2303 1-1:1.0: usb_probe_interface - got id [ 473.193564] pl2303 1-1:1.0: pl2303 converter detected [ 473.206726] usb 1-1: pl2303 converter now attached to ttyUSB0 As you can see, there's a ttyUSB0 device being created. Can you show what you get from 'dmesg' or /var/log/kern.log ? Cheers, Nuno -- http://aeminium.org/nuno/ -- 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.
