seadolphine2000
Advanced Member level 3
- Joined
- Apr 12, 2005
- Messages
- 880
- Helped
- 122
- Reputation
- 244
- Reaction score
- 87
- Trophy points
- 1,308
- Activity points
- 7,372
you cant make hex of intel binary and load it into pic - machine opcodes are completely different. Yet not only hardware driver but protocol related part must be added as well.
Picstudent said:
DDS said:Hi MathGeek,
As for me, the main reason is not cost price of embedded bluetooth
modules. The main reason is availability.. You can easlily find and buy an
USB bluetooth dongle in nearest computer shop withal great choices.
Secondly, regularity.. I think they will be permanent in the market
because of generality of portable equipments like mobile phones, PDAs,
Notebooks, cameras etc.
Thirdly, they have universal interface port. It is USB. If you have
an already designed a reliable USB host in your embedded system, either
use it as bare USB port or equip with that dongle and provide cable-free
possibility to communicate other bluetooth devices.. Instead of a lot
of pin allocation of embedded bluetooth modules, dongles need an USB
port that aready you have.
Regards.
niket_304 said:One more advantage for Windows stack is it will be easy to migrate the driver/stack from Windows to Embedded controller device.
So do you(or anyone) have any idea about free Bluetooth Stack or related codes for WINDOWS?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?