LM3S6569 on Mac OS X Issues

[Stefan Brantschen-3]

I experience issues with connecting my brand-new LM3S6569 to Mac OS X. I flashed the eLua 0.7 binary to the board from Windows, and can operate the board from Windows as well without problems (eLua shell, Lua interpreter, example programs in ROM).

I then tried to talk to the board from Mac OS X. I installed the FTDIUSBSerialDriver and edited the Info.plist file according to James' instructions, including making sure the permissions are OK:

desroches:Extensions] sbr2> pwd
/System/Library/Extensions
[desroches:Extensions] sbr2> cd FTDIUSBSerialDriver.kext/Contents/
[desroches:Contents] sbr2> ls -l
total 384
-rwxr-xr-x  1 root  wheel  196303 May 27 16:56 Info.plist
drwxr-xr-x  3 root  wheel     102 Oct 21  2009 MacOS
drwxr-xr-x  3 root  wheel     102 Oct 21  2009 Resources
[desroches:Contents] sbr2> plutil -lint Info.plist
Info.plist: OK
[desroches:Contents] sbr2>

From the Info.plist file:

<key>IOKitPersonalities</key>
        <dict>
         <key>Stellaris LM3S6965</key>
                <dict>
                        <key>CFBundleIdentifier</key>
                        <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
                        <key>IOClass</key>
                        <string>FTDIUSBSerialDriver</string>
                        <key>IOProviderClass</key>
                        <string>IOUSBInterface</string>
                        <key>bConfigurationValue</key>
                        <integer>1</integer>
                        <key>bInterfaceNumber</key>
                        <integer>1</integer>
                        <key>idProduct</key>
                        <integer>48345</integer>
                        <key>idVendor</key>
                        <integer>1027</integer>
                </dict>
...

In the System Profiler I see the Stellaris board on USB level, including the product and vendor IDs (0xbcd9 and 0x0403, ie. 48345 and 1027 decimal). I have rebooted the system more than once.

But: the serial link does not appear in /dev.

Have I missed something?

Thanks!
-- Stefan


_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

[jbsnyder]

I don't think you've missed anything, but here are a few other things
that you can check on.

Check that the FTDI module has loaded:
$ kextstat -l | grep FTDI
  174    0 0x592b6000 0x8000     0x7000
com.FTDI.driver.FTDIUSBSerialDriver (2.2.14) <112 31 5 4 3 1>

If not, you could try using kextload to load the module, something like:
$ sudo kextload FTDIUSBSerialDriver.kext
(when you're in /System/Library/Extensions)

You might want to check your "All Messages" display with Console.app
to see if anything shows up on device insertion, or if any messages
with "FTDI" appear, when I reconnect a device I get something like
this:
"5/27/10 6:33:01 PM kernel FTDIUSBSerialDriver:        0  4036001 start - ok"

It could also be that the
/System/Library/Extensions/Caches/com.apple.kext.caches hasn't cached
this extension yet and is loading an unedited version of the extension
for you.

You can ask for this to be rebuilt manually, with the kextcache
command, however the man page recommends just using touch on
/System/Library/Extensions to alert the system to the need to rebuild
the startup cache:
http://devworld.apple.com/mac/library/documentation/Darwin/Reference/ManPages/man8/kextcache.8.html




On Thu, May 27, 2010 at 3:10 PM, Stefan Brantschen
<[hidden email]> wrote:

> I experience issues with connecting my brand-new LM3S6569 to Mac OS X. I flashed the eLua 0.7 binary to the board from Windows, and can operate the board from Windows as well without problems (eLua shell, Lua interpreter, example programs in ROM).
>
> I then tried to talk to the board from Mac OS X. I installed the FTDIUSBSerialDriver and edited the Info.plist file according to James' instructions, including making sure the permissions are OK:
>
> desroches:Extensions] sbr2> pwd
> /System/Library/Extensions
> [desroches:Extensions] sbr2> cd FTDIUSBSerialDriver.kext/Contents/
> [desroches:Contents] sbr2> ls -l
> total 384
> -rwxr-xr-x  1 root  wheel  196303 May 27 16:56 Info.plist
> drwxr-xr-x  3 root  wheel     102 Oct 21  2009 MacOS
> drwxr-xr-x  3 root  wheel     102 Oct 21  2009 Resources
> [desroches:Contents] sbr2> plutil -lint Info.plist
> Info.plist: OK
> [desroches:Contents] sbr2>
>
> From the Info.plist file:
>
> <key>IOKitPersonalities</key>
>        <dict>
>         <key>Stellaris LM3S6965</key>
>                <dict>
>                        <key>CFBundleIdentifier</key>
>                        <string>com.FTDI.driver.FTDIUSBSerialDriver</string>
>                        <key>IOClass</key>
>                        <string>FTDIUSBSerialDriver</string>
>                        <key>IOProviderClass</key>
>                        <string>IOUSBInterface</string>
>                        <key>bConfigurationValue</key>
>                        <integer>1</integer>
>                        <key>bInterfaceNumber</key>
>                        <integer>1</integer>
>                        <key>idProduct</key>
>                        <integer>48345</integer>
>                        <key>idVendor</key>
>                        <integer>1027</integer>
>                </dict>
> ...
>
> In the System Profiler I see the Stellaris board on USB level, including the product and vendor IDs (0xbcd9 and 0x0403, ie. 48345 and 1027 decimal). I have rebooted the system more than once.
>
> But: the serial link does not appear in /dev.
>
> Have I missed something?
>
> Thanks!
> -- Stefan
>
>
> _______________________________________________
> eLua-dev mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/elua-dev
>

--
James Snyder
Biomedical Engineering
Northwestern University
[hidden email]
PGP: http://fanplastic.org/key.txt
Phone: [phone]
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

[Stefan Brantschen-3]

James

On 28 May 2010, at 01:35, James Snyder wrote:

> Check that the FTDI module has loaded:
> $ kextstat -l | grep FTDI
>  174    0 0x592b6000 0x8000     0x7000
> com.FTDI.driver.FTDIUSBSerialDriver (2.2.14) <112 31 5 4 3 1>
>
> If not, you could try using kextload to load the module, something like:
> $ sudo kextload FTDIUSBSerialDriver.kext
> (when you're in /System/Library/Extensions)

Thanks. kextstat indeed showed that the kext was not loaded, which I could correct with kextload, as indicated by you. I then got the serial /dev. Alas, the kext still does not load automatically upon reboot. I touched /System/Library/Extensions, even dared to run kextcache -e, to no avail. I'll have to examine that one, but for now I can at least connect to the board! Great Stuff. Next step: try to upload own programs...

What terminal program are you using to connect to the board on Mac OS X?

Cheers
-- Stefan

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev