[beagleboard] Re: Custom eMMC Flasher
I haven't moved files. I moved entire flash image. Firstly, created working 2GB SD card, then copied it on the linux PC to a file using DD tool. Then booted from SD, mounted NFS to see the file and DDed into /dev/mmcblk1. If you bother with silent of DD tool, you may use great PV utility e.g: pv /dev/sdb | dd of=my_sd_image.bin Note, when booted from SD, SD device is /dev/mmcblk0 and eMMC is /dev/mmcblk1. When booted from eMMC, /dev/mmcblk0 is eMMC! Cheers, Piotr. W dniu środa, 30 kwietnia 2014 00:17:40 UTC+2 użytkownik kip...@ualberta.ca napisał: I've been using an SD card to dev on my board similar to the BBB for a while, but I'd like to start using the eMMC instead. I've made modifications to U-Boot/the kernel/the root filesystem, so I'd like to be able to flash the eMMC based on my own pre-existing image. From my understanding, the emmc-prepare.sh script https://github.com/beagleboard/meta-beagleboard/blob/master/contrib/bone-flash-tool/emmc-prepare.shfrom the meta-beagleboard layer of the OpenEmbedded build system. I'm not sure if there are other tools to accomplish this, but this is the only thing I've tried so far. I'm mostly confused by the parameters at the start of the script and what each one represents. These are my assumptions: *IMAGE=* I'm not sure on this. I'm guessing that this is the raw image that will be flashed into the eMMC? Or maybe the output image name? *DEPLOYDIR=* This defaults to the location of the output images from Angstrom's bitbake build, so my guess is that this is the directory that contains U-Boot images, the filesystem and all that jazz. *MOUNTPOINT=* *MOUNTPOINT1=* Based on emmc.sh, it looks like MOUNTPOINT1 is the location of the SD card boot partition and MOUNTPOINT is the location of the file system partition. On my SD card these are currently /media/myname/BEAGLE_BONE and /media/myname/Angstrom, respectively. *FLASHIMG=* The default for this is a tar.gz file for the Linux root file system, so my assumption was that this should be the .tar.gz of my modified root file system in the DEPLOYDIR directory. *SCRATCHDIR=* A temporary directory? I've tried modifying these a few times, but I've never gotten the script to get very far. The farthest I've ever gotten is when I set IMAGE to an exact image of the SD card I'm booting my board with, and with that same SD card inserted in my computer and mounted. In that case I get the following output: *Trying to attach image filedevice-mapper: resume ioctl on loop0p2 failed: Invalid argumentcreate/reload failed on loop0p2Loopdev: loop0/media/myname/BEAGLE_BONE already mounted, trying to unmountMounting /dev/mapper/loop0p1mount: mount point /media/myname/BEAGLE_BONE does not existmyname@ubuntu:~/Dev/meta-beagleboard/contrib/bone-flash-tool$*I'm not really sure what the loop related errors mean, but it looks like the script is unmounting my SD card boot partition, remounting and it and then failing. /media/myname/BEAGLE_BONE is definitely still there after the scripts fails, so I'm not really sure why this error is being thrown. Any help understanding this would be appreciated. -- 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/d/optout.
[beagleboard] Re: Touchscreeen automatically clicking at random points
Hi, Actually I have posted what I have discovered. The problem I faced was with 10 inch screen, with theLCD7CAPE every thing works fine. Touch screen has a capacitance, and there is a charging cycle, which is used in initial touch detecting. If the charging faze is too short, touch screen voltage is too low and this is detected as touch event. I have changed CHARGEDLY_OPENDLY from 1 to 10 (ti_am335x_tscadc.h), 1 is definitely too short. Regards, Piotr. W dniu piątek, 18 kwietnia 2014 12:22:45 UTC+2 użytkownik Kishor Dhanawade napisał: Hello, I am working with Beaglebone black board with ubuntu-12.04LTS (3.8.13). I have interfaced 7 LCD with BBB. LCD is working properly. Touch is also detecting but problem with touch is that it is clicking automatically at random points on the screen. Due to that I unable to run my application which has lots of button on screen. And touch is automatically clicking any button on the screen. I searched lot to solve this problem. But I didn't get solution for it. Please help me to resolve this problem. Thanking you. Regards , kishor -- 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/d/optout.
[beagleboard] Re: Does it supports FreeRTOS
Actually, FreeRTOS is a kind of micro Kernel OS, that is, the Kernel is SoC independent. It is supported on anything it can be compiled to, and is reasonable resourceful. Since it works on 8bit controllers, 1000 times faster BBB is ok. Porting to a new SoC requires connecting System timer and some wrappers around interrupts. There are other potential problems: - drivers for all peripherals, there are hundreds of them in BBB and each requires many registers settings and configurations. - MMU, that is memory management unit, and DRAM configuration. These two things needs to be configured, if the whole effort is expected to make sense. If theses are not already done, and there is no simple C code to borrow, the effort will be rather huge. Regards, Piotr. W dniu wtorek, 15 kwietnia 2014 12:18:18 UTC+2 użytkownik Tulsi napisał: Hi, I am new to thisDoes beaglebone black supports FreeRTOS Harsha -- 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/d/optout.
[beagleboard] Re: Help with Cross Compile of first HelloWorld App
Just compile the kernel following the commonly known instructions for BBB. On of the step, will download appropriate gcc toolchain, it will be named like gcc-linaro-arm-linux-gnueabihf-4.8-2013.10_linux/. That's it. Regards, Piotr. W dniu czwartek, 10 kwietnia 2014 01:20:47 UTC+2 użytkownik RV9Flyer napisał: I'm a newbie and this is my first post. I just got started with building my first HelloWorld style app to test the cross-compile capabilities of Eclipse/CDT, The app compiles successfully and generate the expected HelloBeagle.elf executable. However, when I transfer it to my beagle and attempt to run, I get an Illegal instruction error. I've watched every video I could find (Thanks Derek Malloy) and I still can't find the reason for the error. Obviously it's not generating the right code base, but the build output does show that it it aimed for the cortex-a8 processor which I believe is correct for the beaglebone black. I would appreciate any suggestions or ideas!! Thanks *Here is my environment info and build output:* *Build Environment:* Windows 7 Eclipse Kepler SR2 CDT GNU ARM Eclipse Plug-in MinGW *Beaglebone Black:* (Angstrom Distro) Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l GNU/Linux *Build output:* 16:11:12 Build of configuration Debug for project HelloBeagle make pre-build main-build arm-none-eabi-gcc --version arm-none-eabi-gcc.exe (GNU Tools for ARM Embedded Processors) 4.8.3 20140228 (release) [ARM/embedded-4_8-branch revision 208322] Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Building file: ../src/HelloBeagle.cpp Invoking: Cross ARM C++ Compiler arm-none-eabi-g++ -mcpu=cortex-a8 -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wall -g3 -MMD -MP -MFsrc/HelloBeagle.d -MTsrc/HelloBeagle.d -c -o src/HelloBeagle.o ../src/HelloBeagle.cpp Finished building: ../src/HelloBeagle.cpp Building target: HelloBeagle.elf Invoking: Cross ARM C++ Linker arm-none-eabi-g++ -mcpu=cortex-a8 -O0 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wall -g3 -Xlinker --gc-sections -Wl,-Map,HelloBeagle.map --specs=rdimon.specs -Wl,--start-group -lgcc -lc -lc -lm -lrdimon -Wl,--end-group -o HelloBeagle.elf ./src/HelloBeagle.o Finished building target: HelloBeagle.elf Invoking: Cross ARM GNU Create Flash Image arm-none-eabi-objcopy -O ihex HelloBeagle.elf HelloBeagle.hex Finished building: HelloBeagle.hex Invoking: Cross ARM GNU Print Size arm-none-eabi-size --format=berkeley HelloBeagle.elf text databssdechex filename 211304 2732 7776 221812 36274 HelloBeagle.elf Finished building: HelloBeagle.siz 16:11:28 Build Finished (took 16s.236ms) -- 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/d/optout.
[beagleboard] Re: i want to build a internet kiosk
Hello Navot, There are several options regarding OS and configurations, there are pros and cons for any of them. I'll describe my experience with Ubuntu and browsers. 1) I'm creating somehow operator desktop, which is not much different then a kiosk application. 2) The biggest issue is the browser: - Ice Weasel (Firefox like), heavy, clunky, generally always makes troubles for my pages. I gave up this guy quite quickly. - Chromium, fast but heavy, starts a bit long but it is smooth. It has a kiosk mode, but sometimes displays nasty po-pups (like info about no closing last time), this can be fixed by cleaning up the profile on start-up. - Midori, The Third browser in my opinion, positive experience. Not that fast in vector graphics as Chromium. - DWB, regarding performance, same as Midori, but with extremely minimalist UI. Interesting project however, I'm afraid of support. - There are few others I have looked at, like :luab or something like this. Except Ice Weasel, all other browsers bases on Web-Kit, so they are somehow similar standard implementations. 3) I didn't start UI desktop, just Xorg and a very simple window manager Matchbox Window Manager. DWB even do not require a manager. If you plan to build a kiosk, try do the same and do not start a UI desktop, it just wastes memory in this case. 4) Do you plan to use touch screen? Generally quite painful, there are several discussions about this. I had to fix the driver for my touch screen hardware. That's it. Good Luck. Piotr. W dniu sobota, 5 kwietnia 2014 08:47:10 UTC+2 użytkownik navo...@gmail.com napisał: HI all, I bought the Beaglebone Black. i want to transform it into a nice little desktop for my family. What is the best setup (OS, desktop, browser) for a nice internet kiosk machine (mainly browser). Thanks Navot. -- 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/d/optout.
[beagleboard] Re: BeagleBone Black and resistive touchscreen.
Hello Dennis, I did exactly the same. I connected a touchscreen without a cape. So... 1) Capes are recognized thanks to EEPROM data, then appropriate device tree file is loaded which does the job, that is set hardware pins and loads + configures the driver. 2) You don't have a cape and hence neither an EEPROM, you need to use so-called device tree overlay. 3) By default, touch screen driver is build in into the kernel, somehow, this does not play well with overlay-ed device tree, the kernel needs to be recompiled with the touch screen driver compiled as a module. this is because we need to load the driver after the device tree overlay is loaded. 4) I got 10 tsc, which has bigger capacity, and the default tsc driver charging delay was not good at all, I need to modify the driver before kernel compilation. So, It may look scary, I know. Le me know, if you know how to do the steps. I mean: are you able to configure and build the kernel? Do you know how to load device tree overlay? Do you know how to load a driver module? I have attached my device tree file for the touchscreen, assuming it has exactly same connections as the LCD7 cape. The file shall be but into KERNEL/firmware/capes directory before kernel compilation. Regards, Piotr. -- 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/d/optout. BB-ADC-00A0.dts Description: Binary data
[beagleboard] Re: Encouragement for the disencouraged
Sometimes, we joke that the whole free stuff in IT was created be the evil programmers. Kind of the virtual doctor no, to make the world depended on our knowledge, experience, services and ... bring us lot of money. Yes it works! There is more and more Linux everywhere. In my domain - STBs is almost 99% penetration (excluding Microsoft (actually Ericsson now) MediaRoom), millions of dollars spend on making it work, customizing, porting, writing drivers. You get free drugs sample, then you will keep paying till the end. I like this model. I have to spend many ours to fix two drivers I had to use in my BBB project, I've shared results with the audience of this forum, but experience I've gained will stay with me. -- 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/d/optout.
[beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes
There is a part in the driver (ti_am335x_tsc.c): config = STEPCONFIG_MODE_HWSYNC | STEPCONFIG_AVG_16 | ts_dev-bit_yp | ts_dev-bit_xn | STEPCONFIG_INM_ADCREFM | STEPCONFIG_INP(ts_dev-inp_xp); titsc_writel(ts_dev, REG_STEPCONFIG(end_step), config); titsc_writel(ts_dev, REG_STEPDELAY(end_step), STEPCONFIG_OPENDLY); end_step++; *config |= STEPCONFIG_INP(ts_dev-inp_yn);* There is possible bug, with using OR. It does not show up when XP - AN0 and YN - AN3 because 0 is ORed to 3 (fortunately). With other X/Y plate connections, z2 might be totally wrong. Regards, Piotr. -- 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/d/optout.
Re: [beagleboard] Re: Touchscreen Jitter / Jumping on Beaglebone Black LCD Capes
Good point! However, the issue in the errata is about pen-up whereas I had pen-down false interrupt. Increasing charging time clearly moves the problem away. Piotr. W dniu poniedziałek, 24 lutego 2014 14:45:31 UTC+1 użytkownik Bas Laarhoven napisał: Hi Piotr, Have you studied the errata for the processor? IIRC some issues and workarounds with the TSC are documented there. -- Bas On 24-2-2014 12:51, mich...@o2.pl javascript: wrote: Hi, I step in as everybody looking to find solutions for TS issues. Actually, I'm still working on solving it. However, I have some tips and discoveries I'd like to share, meby someone will find it useful. 1) I have just external TS, no cape at all, the TS is 10 inch. 2) I found after many hours :( that ti_am335x_tsc driver can not be build in, and must be loaded as a module after the cape for TSC is loaded. That's because I use overlay-ed cape for TSC. Even though it is set to be loaded in uEnv.txt! 3) Big touch screen has bigger capacity, it results in permanent auto-touch event generation, driving me nuts since LCD7 TS works nicely. I have discovered, that adjusting delays in driver is the solution!!! There are open-delay, sample-delay, charging-delay defined in ti_am335x_tscad... -- 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: BeagleBone Black touch input problem with ESD protection
I hope, you have solved the problem. If not, I'm hurry with the answer! 1) I had to connect a 10 inch resistive touchscreen, and go t the same issue. 2) The explanation is capacitance of the touch screen, which is a bit bigger then anything, the driver author had to deal with. BTW, quite surprising that they have not taken this to account, I'll explain in next point. 3) If you look in the ti_am335x_tsc driver, there is a charge phase, which load charge into touchscreen surfaces, which if not touched are like capacitor. This capacitor needs time to charge, so if the charging time is too short, the false touch is detected. Adding ESD protection increases capacitance! 4) The driver sets the charging time to 1 clock tick! That's, in my opinion a huge bug. Just ignorance of the topic knowledge. 5) In order to fix the issue, you need to recompile ti_am335x_tsc driver, before do two modifications: - linux-dev/KERNEL/inlcude/linux/mfd/ti_am335xtscadc.h : #define CHARGEDLY_OPENDLYCHARGEDLY_OPEN(*100*) also, I have increased sampling time, not sure if needed: #define STEPCONIG_SAMPLEDLY STEPDELAY_SMAPLE(*10*) - linux-dev/KERNEL/drivers/input/touchscreen/ti_am335x_tsc.c: (line around 276) z /= z2; - z/=z1; (another silly bug) Let me know if this helped. I have send some time before I have figure out that if cope configuration is loaded as overlayed, the driver shall be modproed after loading the cape config. This is not the case when cape configuration is discovered using EEPROM. So, I have also made this driver a module. Regards, Piotr. W dniu środa, 5 lutego 2014 17:09:05 UTC+1 użytkownik moore.cyril napisał: Hi Guys, I have been working on an expansion board for the BBB that includes a resistive LCD touchscreen. The problem that we are having is that our ESD protection diodes seem to break the break the touch input. We are using a 4 wire touch interface on AN0, AN1, AN2, and AN3. The symptom we are seeing is that when the diode is connected to the touch interrupt seems to be triggered inconsistently. When checking the signals with a scope, it shows that the interrupt seems to work fine until an application that uses touch is run then it becomes inconsistent. This does not happen if the ESD diode is removed. The apps we are running are the Qt calibration and Qt touch test. Looking at the raw data from the touch device from within Linux on the BBB we see a steady stream of data before a touch app is run, then inconsistent data streams once a touch app is running AND after the app closes. Again this symptom does not happen with the diode removed. My question is 2 parts: 1)What could be happening that would make the touch interrupt inconsistent only when that diode is present AND one of these applications is run? 2) Do we really need additional ESD protection? Does Anyone have any experience with a BBB and a heavy usage resistive touch screen, that is not have additional ESD protection? In the two cape examples I looked at additional ESD protection is not used. This is the ESD part that we are using: http://www.comchiptech.com/cms/UserFiles/CPDT6-5V4U%20RevD364097.pdf Thanks Cyril -- 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 SD card with ubuntu
Nice tool: PV! pv /dev/sdb | dd of=sd_image_file Then, you will see the progress! Cheers. W dniu piątek, 14 lutego 2014 18:18:02 UTC+1 użytkownik RobertCNelson napisał: On Fri, Feb 14, 2014 at 11:12 AM, gmsmith...@gmail.com javascript:wrote: Thank you for the quick reply, does that mean I can clone the SD card on the xm itself while it is running? I thought I have to power it off, pull the card out, and do it on something like a PC ubuntu or vm.. So I have to get a SD card adapter and for the of part, is that correct? Thanks in advance. Either or should work.. just as long as you do not use any uuid values in u-boot or /etc/fstab.. 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.
