Thanks Marcel,

What I know about the device is that its command interface (UART) uses a 
frame protocol, with start and end delimiters of frames, frame ids and 
so on. I understand from your words that this is the standard way to 
communicate and that all devices have the same set of commands.

Anyway, I will check what you mention about hciattach. Is there any kind 
of documentation on how to do this, or I must dig into the code?

Thanks again,

David


Marcel Holtmann wrote:

>Hi David,
>
>  
>
>>We have included a National LMX9830 module in a new design. The 
>>communication between the chip and the microprocessor is via UART and we 
>>have also connected the audio channels of the chip to the processor, so 
>>that we can use the SCO link.
>>
>>It's the first time we use bluetooth modules in our designs, and so, we 
>>are open to any kind of suggestion on how to work on this.
>>
>>At first sight, it seems that we should use the UART(H4) driver, but we 
>>are not really sure if the commands to communicate to the chip are 
>>standard or not. I think that we will probably need to develop some kind 
>>of a driver.
>>    
>>
>
>unless you use some vendor specific deep-sleep things, the H4 driver
>should be fine. However you might need to adapt hciattach for the module
>initialization.
>
>Regards
>
>Marcel
>
>
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by DB2 Express
>Download DB2 Express C - the FREE version of DB2 express and take
>control of your XML. No limits. Just data. Click to get it now.
>http://sourceforge.net/powerbar/db2/
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>  
>