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:
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
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
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
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
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
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
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);
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
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
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
11 matches
Mail list logo
