Gordon might have a better answer when he wakes up. But here's a
diagram of the footprint of the bluetooth module (the module itself,
not the gumstix, which will be a mirror image). I believe we use the
UART1 connection on the module, but you should check for signals -- it
might be that we use UART2. Other than power and ground, the only
signals connected are Tx,Rx,CTS and RTS.

I'm actually not 100% sure that statement is still correct. What it
meant was that if you compile MMC support into the kernel, you could
not also compile in "pre-emptible kernel threads" support. That is,
system calls would not be pre-emptible if MMC support was in the
kernel. Now that the MMC driver is actually folded into mainline and
not just an added patch, this problem may very well have been resolved.
If you need pre-emptible system calls, then please do just try it, and
see if it works. If it does, then update the wiki :)
Thanks,
C
On Nov 19, 2004, at 6:25 AM, Dave Hylands wrote:
> Hi,
>
> In the wiki,
> http://www.gumstix.org/tikiwiki/tiki-index.php?page_ref_id=14
> it says,:
>
> using the mmc makes the kernel non-pre-emptible.
>
> Does this mean that it's only non-pre-emptible while the mmc is being
> accessed (I'm hoping that this is the case), or that it's
> non-preemptible if mmc is mounted?

Some MMC cards have trouble being detected by u-boot. I need to take
another pass at cleaning up the u-boot MMC code (and possibly adding SD
support at the same time). Another way of doing this, if you can
access your MMC in linux, is to copy the new uImage to say
/boot/uImage2 and then use fsload /boot/uImage2 to load it instead of
the regular uImage.
C
On Nov 19, 2004, at 5:34 AM, Fred Haze wrote:
> I have just received my gumstix. Let me see if i have
> things correct. The Uimage it the kernel and the
> root_fs_arm is the whole image including all of the
> whole file system. So believing that is correct i
> created a new Uimage. Before I permentaly copy it
> over i want to boot it from the mmc. I have looked
> through the past posts and found the following:
> So, what I have done for my own kernel testing is:
> 1) create a "loadkernel" env variable:
> setenv loadkernel mmc\; sleep 1\; mmc\; fatload mmc
> 1 0xa2000000 uimage
>
> 2) create a "testkernel" env variable:
> setenv testkernel run loadkernel\;cp 0x140000
> 0xa2100000 0x40000\; bootm 0xa2000000
> 0xa2100000
>
> 3) you can check the list of env variables with
> "printenv"
> printenv
>
> 4) save it to flash
> save
>
> Thereafter, upon reset, you can
> 1) intervene within the 3 seconds by pressing any
> key, then
> 2)type "run testkernel" at the prompt.
>
> Which i do and i get errors of the following sort:
> GUM> printenv
> bootdelay=2
> baudrate=115200
> bootargs=console=ttyS0,115200n8 root=1f02
> rootfstype=jffs2 reboot=cold,hard
> bootcmd=fsload a2000000 boot/uImage;bootm a2000000
> stdin=serial
> stdout=serial
> stderr=serial
>
> Environment size: 196/131068 bytes
> GUM> setenv loadkernel mmc\; sleep 1\; mmc\; fatload
> mmc 1 0xa2000000 uimage
> GUM> setenv testkernel run loadkernel\;cp 0x140000
> 0xa2100000 0x40000\; bootm 0xa2000000 0xa2100000
> GUM> run testkernel
> No MMC card found
> No MMC card found
>
> ** Unable to use mmc 1:1 for fatload **
> ## Booting image at a2000000 ...
> Bad Header Checksum
>
> My MMC works fine, when started i can cd to /mnt/mmc
> and make and creat files and read exsisting files.
>
> Also once i get this straightened out am i correct in
> assuming the easiest way to update kernels is to
> replace the /boot/Uimage with the new one i have made?
> Thanks a lot
>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Meet the all-new My Yahoo! - Try it today!
> http://my.yahoo.com
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: InterSystems CACHE
> FREE OODBMS DOWNLOAD - A multidimensional database that combines
> robust object and relational technologies, making it a perfect match
> for Java, C++,COM, XML, ODBC and JDBC. http://www.intersystems.com/match8
> _______________________________________________
> gumstix-users mailing list
> gumstix-users@...
> https://lists.sourceforge.net/lists/listinfo/gumstix-users

I need to use all four of the serial ports on the gumstix for a project
I'm working on. Though the first four were easy enough, the port that
normally goes to the Bluetooth module is a bit of a problem. Since my
board doesn't have Bluetooth, I see all the leads that would normally
connect to that module. However, I can't find any diagrams that would
tell me where those two (UART) wires show up at in the actual board. Can
someone tell me where I need to solder my leads? Thanks.
=20
Fernando

Hi,
Have followed all of Dave's steps to compile i2c support into the
kernel (static, not modules). When the gumstix boots it now runs
through all the possible 7 bit i2c addresses for the first i2c
controller i2c-0, which does slow down the bootup time as noted by
Craig. However, contrary to the documentation
(Documentation/i2c/dev-interface), /proc/bus/i2c and /dev/i2c-0 are
not there.
At the moment I don't have any i2c devices attached to the Gumstix,
since I'm trying to preempt hardware developers to save time,. Is it
simply the case that the aforementioned files don't exist because
there are no devices or have I done something wrong?
Our main application for the gumstix requires hanging various flavours
of PIC on the i2c bus, in order (amongst other things) to add 6 RS485
lines. So getting i2c working is crucial for us.
Dan
--
Dan Taylor
Software Development Engineer, JTL Systems Ltd
PhD Student, Reading University, UK
http://www.logicalgenetics.com

I have just received my gumstix. Let me see if i have
things correct. The Uimage it the kernel and the
root_fs_arm is the whole image including all of the
whole file system. So believing that is correct i
created a new Uimage. Before I permentaly copy it
over i want to boot it from the mmc. I have looked
through the past posts and found the following:
So, what I have done for my own kernel testing is:
1) create a "loadkernel" env variable:
setenv loadkernel mmc\; sleep 1\; mmc\; fatload mmc
1 0xa2000000 uimage
2) create a "testkernel" env variable:
setenv testkernel run loadkernel\;cp 0x140000
0xa2100000 0x40000\; bootm 0xa2000000
0xa2100000
3) you can check the list of env variables with
"printenv"
printenv
4) save it to flash
save
Thereafter, upon reset, you can
1) intervene within the 3 seconds by pressing any
key, then
2)type "run testkernel" at the prompt.
Which i do and i get errors of the following sort:
GUM> printenv
bootdelay=2
baudrate=115200
bootargs=console=ttyS0,115200n8 root=1f02
rootfstype=jffs2 reboot=cold,hard
bootcmd=fsload a2000000 boot/uImage;bootm a2000000
stdin=serial
stdout=serial
stderr=serial
Environment size: 196/131068 bytes
GUM> setenv loadkernel mmc\; sleep 1\; mmc\; fatload
mmc 1 0xa2000000 uimage
GUM> setenv testkernel run loadkernel\;cp 0x140000
0xa2100000 0x40000\; bootm 0xa2000000 0xa2100000
GUM> run testkernel
No MMC card found
No MMC card found
** Unable to use mmc 1:1 for fatload **
## Booting image at a2000000 ...
Bad Header Checksum
My MMC works fine, when started i can cd to /mnt/mmc
and make and creat files and read exsisting files.
Also once i get this straightened out am i correct in
assuming the easiest way to update kernels is to
replace the /boot/Uimage with the new one i have made?
Thanks a lot
__________________________________
Do you Yahoo!?
Meet the all-new My Yahoo! - Try it today!
http://my.yahoo.com