Hot!BM62 eeprom programming via MCU

Author
tutroby
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2018/09/24 02:58:05
  • Location: 0
  • Status: offline
2018/09/25 00:01:24 (permalink)
0

BM62 eeprom programming via MCU

Hello there,
is there any documentation about programming internal eeprom of BM6x modules via MCU (of course using HCI_TXD/HCI_RXD and entering Test mode)?
 
I don't want to use external EEPROM tool. 
 
Thank you
 
Best Regards,
Roberto
 
 
#1

5 Replies Related Threads

    rainier
    New Member
    • Total Posts : 2
    • Reward points : 0
    • Joined: 2018/11/08 03:18:24
    • Location: 0
    • Status: offline
    Re: BM62 eeprom programming via MCU 2018/11/09 02:31:22 (permalink)
    5 (1)
    Yes I had to figure out the protocol as I had a completely corrupted BM20 and had to rewrite the entire EEPROM
    The protocol is very simple (and does not even have a checksum so corruption is easily possible).
    To write the data 01 02 03 04 to address 0120
     
    01 27 FC 07 01 20 04 01 02 03 04
    (01 27 FC <# bytes following> <address MSB/LSB> <# bytes data following> 01 02 03 04)
     
    Then wait for return:
     
    04 0E 04 01 27 FC 00
     
    The last 00 could be an error code if not zero.
    Microchips update tool sends a maximum amount of data of 128 bytes in one go - not sure if that is a forced limit but probably safe to stick to that.
     
    Seems like BM62 uses same protocol as BM20.
     
    Rainier
     
     
    #2
    tutroby
    New Member
    • Total Posts : 4
    • Reward points : 0
    • Joined: 2018/09/24 02:58:05
    • Location: 0
    • Status: offline
    Re: BM62 eeprom programming via MCU 2018/11/14 09:42:05 (permalink)
    0
    Dear Rainer,
    thank you very much!
     
    I'll try and let you know
     
    Thank you again,
    Best Regards
    Roberto
    #3
    tutroby
    New Member
    • Total Posts : 4
    • Reward points : 0
    • Joined: 2018/09/24 02:58:05
    • Location: 0
    • Status: offline
    Re: BM62 eeprom programming via MCU 2018/11/28 04:01:43 (permalink)
    0
    Dear Rainer
    I confirm the commands you described.
     
    Current tool after a write perform also a read (so.. readback to avoid corruption)
     
    example
    readback of a single byte 14 previously written at address 0007
     
    01 29 FC 03 00 07 01
    (01 29 FC <# bytes following> <address MSB/LSB> <# bytes to read>
     
    reply:
    04 0E 08 01 29 FC 00 00  07 01 14
    (04 0E <# bytes following> 01 29 FC 00 <address MSB/LSB> <# bytes following> <..data..>)
     
    ---
     
    at the beggining of eeprom write there are also 2 startup commands
    one is unknown (a startup command?)
    (-->) 01 03 0c 00
    (<--) 04 0e 04 01 03 0c 00
     
    the other ask for a name
    (-->) 01 20 fc 00
    (<--) 04 0e 18 01 20 fc <followed by string and some closing bytes, in my case string is "5506_DUAL_SPK0">
     
    Roberto
    #4
    gcooper434
    New Member
    • Total Posts : 4
    • Reward points : 0
    • Joined: 2018/08/30 04:51:57
    • Location: 0
    • Status: offline
    Re: BM62 eeprom programming via MCU 2018/12/06 07:48:12 (permalink)
    0
    Question: where sis you find documentation of the EEPROM content addresses?
     
    I've been evaluating the BL64 for possible use in a new generation of an existing Bluetooth product, and I am most disappointed in Microchip documentation and support. I feel like I must be missing a layer of documentation, for surely no one has built anything around the BM64 with just the documentation listed on the Microchip site.
     
    Microchip support people...are you listening? My trouble ticket from Nov 16 is still open, though you CLOSED IT without completing it.
    #5
    tutroby
    New Member
    • Total Posts : 4
    • Reward points : 0
    • Joined: 2018/09/24 02:58:05
    • Location: 0
    • Status: offline
    Re: BM62 eeprom programming via MCU 2018/12/11 01:07:50 (permalink)
    0
    Same problem for me...
    BM6x modules documentation and support is lacking, also my experience with ticket is poor.
     
    I asked to local Microchip support and they said that (at least in Europe) support for these products starts from 100Kpcs. 
     
     
    Currently the only good point on BM6x is price.
     
    Anyway.. no documentation on EEPROM, but you can find what Microchip tools generate editing the ".ipf" file.
    You'll find something like:
    ADDR 000B DATA "06 00 00 00 06 00 00 31 11 10 18"
    ADDR 001D DATA "9B"
    ADDR 0021 DATA "03"
    ...
    so.. it's quite easy to rev. eng. ..
    and very easy to upload "as is" for production purposes. 
     
    Roberto
    #6
    Jump to:
    © 2018 APG vNext Commercial Version 4.5