Hello there,
I am trying to revive a EB024 Bluetooth board, which seems to elude any attempts using it.
We worked with the bluetooth board and an AVR programmer for some days and returned one morning back to the lab finding it not working at all. The use case was pretty simple:
- setting it up as discoverable
- connect to it via a computer as a virtual COM
- send back data back and forth between uC and PC
I have tried anything from changing the AVR programmer, to ordering a replacement board from Farnell and to different programs and scripts ending at the one I found here on the forum for a bluetooth controlled car with an AVR. My multimeter shows that the board should be powered with 3.3 volts after the voltage supply and I am running out of options. I am sure the bets are too high for two modules to be dead and therefore my educated guess would be it is the board/chip on the EB024 that just died. If you have any other further ideas how to test the board I am more than welcome to test them. Maybe you have some other low level tests that I could try. Thanks for any help.
Reagrds,
Nils
EB024 Bluetooth board - no sign of life
EB024 Bluetooth board - no sign of life
Custom_Code.c help needed? -> http://tinyurl.com/2y2mzq
Flowchart high quality vector graphic output =>>http://tinyurl.com/6sx2sx
Flowchart high quality vector graphic output =>>http://tinyurl.com/6sx2sx
Re: EB024 Bluetooth board - no sign of life
Hello,
I am sorry to bother you again, but as I need to work with bluetooth communications in a project, I would like to resolve my problem.
Thanks,
Nils
I am sorry to bother you again, but as I need to work with bluetooth communications in a project, I would like to resolve my problem.
Thanks,
Nils
- Benj
- Matrix Staff
- Posts: 15312
- Joined: Mon Oct 16, 2006 10:48 am
- Location: Matrix TS Ltd
- Has thanked: 4803 times
- Been thanked: 4314 times
- Contact:
Re: EB024 Bluetooth board - no sign of life
Hello,
The returned board was investigated and it was found that the board was 100% working when received.
The problem with using the board with a system such as AVR where the patch system is required is that the labelling on the Bluetooth board is a bit odd. The pin marked as RX on the E-block needs to be connected to the TX pin of the microcontroller and visa versa. This also applies for the RTS and CTS pins which should be connected through to their opposite on the uC. Having understood this the board and the non-working module fires up first time on the AVR system as it did on the PIC system.
The returned board was investigated and it was found that the board was 100% working when received.
The problem with using the board with a system such as AVR where the patch system is required is that the labelling on the Bluetooth board is a bit odd. The pin marked as RX on the E-block needs to be connected to the TX pin of the microcontroller and visa versa. This also applies for the RTS and CTS pins which should be connected through to their opposite on the uC. Having understood this the board and the non-working module fires up first time on the AVR system as it did on the PIC system.
- Attachments
-
- Ex1.fcf_avr
- (9.5 KiB) Downloaded 294 times
Regards Ben Rowland - MatrixTSL
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel
Flowcode Product Page - Flowcode Help Wiki - Flowcode Examples - Flowcode Blog - Flowcode Course - My YouTube Channel