[RoadTest] "Freescale RD3803MMA7660FC Review - Serial Communication"

Hi again,

I changed the target CPU in sharpdevelop and got it to compile and run without errors, however I only get "Device not found." when running it.

Elias

Hi,

Is your board working with freescale software?

i attached a new version (with a combobox listing all detected serial ports), please check if the port used by the board is listed.

Amine

Hi,

The board works normally in 32bit environment and with direct serial connection.

With the build you attached I get a list of the serial ports and the correct port is actually mentioned there twice for some reason.

In device manager I see it only once as usual so I'm not sure what is causing the behaviour.

Maybe something different registry wise in Windows 7.

Elias

It seems like an issue in GetPortNames function as described here:

http://connect.microsoft.com/VisualStudio/feedback/details/236183/system-io-ports-serialport-getportnames-error-with-bluetooth

Here's a build with a workaround.

Hi,

Thanks for the new build. I'm getting an exception however:

System.ArgumentException: An entry with the same key already exists.
   at System.ThrowHelper.ThrowArgumentException
   at System.Collections.Generic.TreeSet<System.Collections.Generic.KeyValuePair<System.Int32,System.String>>.Add
   at System.Collections.Generic.SortedDictionary<System.Int32,System.__Canon>.Add
   at MMA7660.MPR031COM.getAvailablePorts in c:\Users\Sene\Desktop\MMA7660\MMA7660\MPR031COM.cs:line 117
   at Demo.MainForm..ctor in c:\Users\Sene\Desktop\MMA7660\Demo\MainForm.cs:line 26
   at Demo.Program.Main in c:\Users\Sene\Desktop\MMA7660\Demo\Program.cs:line 24

The line 117 is this one: cleanPortNames.Add(int.Parse(portNumber), string.Format("COM{0}", portNumber));

Thanks

Elias

edit: as I saw from your link the issue was related to the MS bluetooth stack so I removed my dongle and your previous build now finds the MMA.

I still see the correct COM listed twice there though which is weird but the corrupted bt virtual com is gone and that seems to do the trick.

I did not have any issues accessing the device itself with virtual OS or with direct serial probing so it still looks like something with this method

edit2: I replaced the dongle to another port and it was assigned a different COM (with a different weird character) and now it seems to work normally. the latest build also works, maybe I did not remember to delete everything before replacing. I still see two times COM9 but at least I get values out

hi,

the method just lists entries in registry key : HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\SERIALCOMM

did the com port is also listed twice in registry?

Hi,

No in the registry everything is correct so the usb to serial is listed only once and the bt serial com number is normal.

Elias