• AVR Freaks

Hot!BM23 reimaging

Author
netstar77
New Member
  • Total Posts : 2
  • Reward points : 0
  • Joined: 2016/06/04 08:14:59
  • Location: 0
  • Status: offline
2016/07/05 15:57:02 (permalink)
0

BM23 reimaging

Hi everybody.
We are working on the HiDef Audio project that uses BM23 module connected directly to the digital audio codec.
We were able to get audio trough the Bluetooth, but with very bad quality. It sound like codec uses low speed connection, and you here high pitches being cut off.
We have purchased EVM board, and it sounds very good in the beginning.
However, when I made first patch file to re-flash it; is stopped to give me sound anymore.  
The EEPROM tool sees correct IC. It is able to communicate, pair with BT device, and reload EEPROM over and over.
However, there is no activity on the I2S lines, doesn't meter it is master or slave.
Is there any suggestions, what do we need to try next?
 
Thank you.
#1

4 Replies Related Threads

    PIC4C code
    Junior Member
    • Total Posts : 105
    • Reward points : 0
    • Joined: 2011/02/21 10:32:55
    • Location: 0
    • Status: offline
    Re: BM23 reimaging 2016/07/06 09:29:36 (permalink)
    0
    HI testing to get on this fourm
    #2
    netstar77
    New Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2016/06/04 08:14:59
    • Location: 0
    • Status: offline
    Re: BM23 reimaging 2016/07/12 08:25:15 (permalink)
    0
    Hi.
    We have resolved sound issue. It turns out that we used 48K sampling frequency on our device, but BM23 by default uses 44.1K.
    However, the re-imaging issue are still exist. We, cannot change broadcast name of the BM23 away from IS2023.
    Looks like it may be done on the go, by sending a 0x05 command, but this command usually make BM23 to crash and not to do anything until you recycle the power.
    Also, we would like to do some changes, stated tin datasheet, like using 24-bit I2S instead of 16-bit. Also, may be switching to 48K sampling instead of 44.1K.
     
    Any suggestions?
    #3
    dspencer007
    New Member
    • Total Posts : 3
    • Reward points : 0
    • Joined: 2018/09/04 08:05:50
    • Location: 0
    • Status: offline
    Re: BM23 reimaging 2018/09/19 06:53:46 (permalink)
    0
    I have solved the broadcast name issue on my BM23 custom design. The protocol defines the length of a "normal" package sent to the BM23 as: Sync, UL, LL, OP, Param1...Param?  ending with CS. LL defines the length of bytes that include Op Code plus all Parameters.
     
    The BT Naming package requires all 32 parameters (Text Chars). 32 max chars are allowed for a name, anything shorter must be padded with zero's. Here's an example package.
     
    \0xAA\0x00\0x21\0x05\0x4D\0x59\0x20\0x42\0x4C\0x55\0x45\0x54\0x4F\0x4F\0x54\0x48\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x00\0x5E      // Set Local Device Name to "MY BLUETOOTH"
     
    Yeah, Holy Moly BUT it works. I'm using an LPC1549 and RealTerm for UART comm so you may have to convert to 0xyy format for your bytes. This can be confirmed by changing BTM Name on the UART Tool (203 tools) and monitoring the cmd traffic when you change the BTM Local Name.
     
    DAS
    post edited by dspencer007 - 2018/09/19 06:56:10
    #4
    susbala
    New Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2019/06/04 00:22:22
    • Location: 0
    • Status: offline
    Re: BM23 reimaging 2019/06/05 04:28:30 (permalink)
    0
    Hi ,
    i need to change the bluetooth device name in BM23 . Am using 05 opcode to change the device name but the device name is not changing 
    #5
    Jump to:
    © 2019 APG vNext Commercial Version 4.5