• AVR Freaks

Helpful ReplyHot!BM62 error while writing EEPROM

Author
ptibruno
Starting Member
  • Total Posts : 84
  • Reward points : 0
  • Joined: 2007/04/18 05:25:29
  • Location: 0
  • Status: offline
2018/04/06 08:16:43 (permalink)
5 (1)

BM62 error while writing EEPROM

Hi Gents,
I've just received some BM62 bluetooth module, I've mouted them on my PCB design.
According to the steps described on the DevKit manual I've done the following steps :
- Generate the .txt file with the DSP parameters using DSPTool_IS206x_012_DualModeSPK1.1_v1.06.exe
- Generate the .txt file with UITool_IS206x_012_DualModeSPK1.1_v1.03.exe with IC package=BM62
- Merge the files using MPET.exe using the default bin file IS206X_012_DUALMODESPK1.1_E1.0.0.2_0FCD.bin
-> then I generate an Ipf file to write on BM62 EEPROM
 
Using EEPROM_Tool_V4851.exe  I've got MPSE Name : IS2064S_012_SPK02_V2.1_BETA
I'm trying to write on the EEPROM but i've got the following error : ''Device's IC version doesn't match file's IC Version: IS206X_012_DUALMODESPK1.1_E1.0""
 
When I'm doing the same steps with the DevKit it is working fine, the EEPROM tool is giving me MPSE name = IS206X_012_DUALLMODESPK1.1_E1.0
 
both module are BM62 so I'm not really understanding the meaning of the MPSE Name
 
Can anyone help with this error?
 
Thanks for your help
Regards
Bruno
 
 
 
 
 
 
 
#1
ryanafleming
New Member
  • Total Posts : 15
  • Reward points : 0
  • Joined: 2017/12/17 23:00:51
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/07/24 22:57:18 (permalink) ☄ Helpfulby Rbaragona 2018/10/29 21:27:26
0
For those who like me took a while yo get the solution. I have been working with the BM64 and had the same issue, but managed to fix it.
 
First this response is actually from the switches on the eval board being set still in programming mode rather than eeprom load mode. That is SW9 modes:
Running app: 1 off, 2 on.
Programming: 1 off, 2 off.
Programming eeprom: 1 on, 2 off.
 
Whenever you change switch states you have to power cycle the chip too, else it won't take effect.
#2
floppen
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2013/11/09 03:19:36
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/10/25 04:54:01 (permalink)
0
Hi
 
Similar problem but with BM64.
I get an error that version is wrong when i try to program EEPROM, I found that if i have pin 39 "P3_6" low i get this error and if i have it high programming the EEPROM works just fine.
#3
Rbaragona
New Member
  • Total Posts : 10
  • Reward points : 0
  • Joined: 2017/06/01 21:23:08
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/10/29 21:13:12 (permalink)
0
Hey Bruno,
Any success with this issue?  I'm running into the same thing now, and I'm not sure how to fix it.  I've tried re-flashing the BM62s but that doesn't seem to help either.
#4
Rbaragona
New Member
  • Total Posts : 10
  • Reward points : 0
  • Joined: 2017/06/01 21:23:08
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/10/29 21:27:21 (permalink)
0
Ah, it was as Ryan described, I just had to fully click the switch for the EAN.
 
#5
gcooper434
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2018/08/30 04:51:57
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/11/15 18:15:40 (permalink)
0
1st question: Bruno, did your problem get resolved?
2nd question: I don't understand how the switch being in the wrong position would cause Bruno's problem: if the switch was not in the right position (and the the power then turned off/on after the switch is set to the right position) then I don't see how the USB connection would be made, and there wouldn't be ANY response.
 
I'm having the very same problem Bruno reported, and I DO have the switch in the right position. Did I miss something here? I have the switch in what I think is the right position, and I have the red and blue LEDs on continuously. I can connect, and I get the same error Bruno reported. With the switch in any other position, I cannot connect, and get NO response.
 
#6
Rbaragona
New Member
  • Total Posts : 10
  • Reward points : 0
  • Joined: 2017/06/01 21:23:08
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/11/15 18:51:41 (permalink)
0
Hi gcooper434,
I agree with your assumption, and that was my initial problem too.  I anticipated either no response or the response with the correct version.  In my particular case, it wasn't the EEPROM programming switch that was in the incorrect position, it was the the BTM_CONFIG_EAN pin.  Once I confirmed all 3 switches/pins (BTM_Config, P2_0, and P2_4) were in the correct position I was able to read the correct MPSE name and program the EEPROM.
#7
gcooper434
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2018/08/30 04:51:57
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/11/16 07:18:31 (permalink)
0
Rbaragona,

I have SW12's individual switches set as follows:
- 1: ON
- 2: OFF
- 3: OFF

When I attach the USB cable to the PC, the RED and BLUE LEDs are both on (and not blinking.) The GREEN LED is off.

When I connect (Port 28) I can click on the Module/Identify control and get the response of "IS2064S_012_SPK02_V2.1_BETA". This is different from the name shown in Illustration in FIGURE 3-30 of BM62 EVB User’s Guide (page 48).

Is there something I'm missing?

Gerald
#8
Rbaragona
New Member
  • Total Posts : 10
  • Reward points : 0
  • Joined: 2017/06/01 21:23:08
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2018/11/16 08:26:42 (permalink)
0
Hi Gerald,
It sounds like your doing things correctly.  Maybe try flipping the switches back and forth, or when the USB is plugged in hit SW1, RST_N, to reset the module.
 
Maybe even try other incorrect switch positions.  I'm sorry I can't be more helpful!
 
Rob
#9
AleksOM
New Member
  • Total Posts : 1
  • Reward points : 0
  • Joined: 2018/12/27 03:11:06
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2019/01/14 00:39:02 (permalink)
0
Hi All!
I have similar problem.
I used BM64 BT module with my PCB design.
I made the first version of the device more than 6 month ago.All was good.
Now I recieved more modules. All modules are v1.1. I take first module of 11, EAN->hight via 10 Ohm, P2_0->GND via 4.7 kOhm and update ROM to v2.1. But when I upload my EEPROM,which generated for BM64v2.1(EAN low,P2_0 low), I have problem:'Device's IC version doesn't match file's IC Version: IS206X_012_DUALMODESPK2.1_E1.0_BETA"
I solder my old BM64 - all working.
Herewith all modules with the same ROM version.
All new BM64 similar problem.
Then i generated new EEPROM to v1.1,but it didn't work either!
When I'm write generated EEPROM to DevKit all working fine(I updated the version to v2.1).
Can anyone help me?
#10
GTV31
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2016/04/20 07:51:35
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2019/11/10 07:46:36 (permalink)
0
Dear AleksOM,
 
I had a similar issue to yours with a custom BM64 PCB. 
Initially everything worked. 
  1. First I flashed the latest version from the website using the Flash Update Tool
  2. Then I made the settings for the for the EEPROM with the UI Tool and the DSP Tool
  3. Merged them with the MPET Tool
  4. Then upload them to the BM64 (EAN = High / P2_0 = LOW) using the EEPROM Tool
  5. Everything worked for the first 5 - 10 uploads on the same module (was trying to get I2S to work with my DAC) and then suddenly a wild ERROR message appeared when uploading the EEPROM code: Cannot connect the Device !
I am concerned that I might have reached a maximum write cycles on the EEPROM some how or most probably enabled / disabled a setting and not being able write anymore to the EEPROM. Any ideas or have any of your issues have been resolved.
 
Thank you for you time.
#11
ryanafleming
New Member
  • Total Posts : 15
  • Reward points : 0
  • Joined: 2017/12/17 23:00:51
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2019/11/10 16:12:35 (permalink)
0
Note that my eeprom appears to permanently stuck with "Can't connect to device". These days I just upload the full eeprom file with the isupdate.exe tool and select eeprom instead of flash. This seems to work for me consistently. I have done it probably 30 times now.
 
JUST MAKE SURE YOU SELECT THE CORRECT EEPROM FILE AND THE CORRECT SETTINGS IN YOUR FILE. The application is relatively bulletproof, but try it with one of the supplied files first. Once you have it going, you should be good in the future and you won't have to deal with all the can't connect bs.
#12
GTV31
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2016/04/20 07:51:35
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2019/11/18 14:38:28 (permalink)
0
Dear ryanafleming,
 
Thank you so much for noting this. It definitely worked and I did not notice this section of the "isupdate.exe".
 
Thank you for your time and assistance.
 
Kind regards,
 
KinefDesigns 
 
#13
Nesca
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2019/10/16 15:39:46
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2019/11/25 07:19:49 (permalink)
0
Hey Guys!
 
I've been trying to get a response from the BM64, and the EEMRPOM tool always reads "unknown version".
 
I do not have the EVB and and I've been trying to use the CH340 to establish communication with the PC.
I noticed when using the SPKCommandSetTool, the error reads "The MCP2200 is disconnected".  
Do I need the MCP2200 specifically to use the EEPROM tool?
 
Also, I've just been using an old PIC to switch between modes, just trying to get some functionality, and the LEDs I've connected to the BM64 are lighting up correctly, according to the EVB guide.  Do I absolutely need the humongous MCU program Microchip uses for the EVB?
 
edit: Also worth noting that my phone connects with the module via Bluetooth, but quickly disconnects.
 
Any help would be greatly appreciated,
 
Nesca
post edited by Nesca - 2019/11/25 08:13:39
#14
Nesca
New Member
  • Total Posts : 4
  • Reward points : 0
  • Joined: 2019/10/16 15:39:46
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2019/11/27 08:17:42 (permalink)
0
Just wanted to give an update to future googlers.
 
The datasheet saying that EAN and P2_0 have internal pull-up is dubious, so be sure that they're going all the way high.  I connected them to the SYS_PWR for high, through a 10Ω resistor each.  P3_6 does seem to have something to do with which mode the BM64 goes into, and how the EEPROM tool detects it.  If you're getting the wrong version error from the EEPROM tool, experiment with EAN, P2_0, and P3_6. 
 
I also managed to update the flash through an old version of isupdate.exe, but the newest one didn't seem to work. 
 
I also had a problem with connecting the module to my PC at first.  I had never worked with serial before, so there were a couple of things I missed.  You have to have USB drivers for the USB-Serial chip you are using, and if that doesn't seem to be enough, try switching RX/TX, atleast if you are using an Arduino with the processor reset (remember to level shift the lines though, since the Arduino serial runs at 5V, which is too high for the BM64). 
 
The CH340G chip worked with everything except the SPKCommandSetTool, which seems to specifically need to be connected to the BM64 through the MCP2200 (very annoying).
 
I'll edit this comment if something else comes to mind that I think'll help.
 
Hope this helps someone. cheers! :)
 
Nesca
#15
echorules
New Member
  • Total Posts : 25
  • Reward points : 0
  • Joined: 2015/06/11 13:44:57
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2020/01/03 09:35:19 (permalink)
0
  • I get the warning when I use the SPKCommandSetTool about the MCP2200 but it still functions.
  • I have had issues with cheap USB cables causing these issues.  The ones MCP includes with their kits are very good.
  • As previously mentioned, make sure your switches and pullups are configured correctly their appears to be a mistake on some of the MCP daugther boards - https://www.microchip.com/forums/FindPost/1066932
#16
GTV31
New Member
  • Total Posts : 8
  • Reward points : 0
  • Joined: 2016/04/20 07:51:35
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2020/01/12 08:26:57 (permalink)
0
For anyone with issue regarding programming the module.
 
A FTDI FT232 (USB-2-UART) board that you can get from AliExpress or even Amazon, will also work, its just UART @ +3V3. However, it will show the MCP2200 not found but communication will still be there and you can use the SPKCommand tool (or any other tool in the package release by Microchip).
 
Regarding the Pull-Up/Down, in the development board PDF, on page 75 is the required configuration to enter Firmware / EEPROM upgrade (RCM TEST) or normal operation (Flash APP).
 
http://ww1.microchip.com/downloads/en/DeviceDoc/50002514B.pdf
 
Hope this helps others.
 
#17
gcooper434
New Member
  • Total Posts : 5
  • Reward points : 0
  • Joined: 2018/08/30 04:51:57
  • Location: 0
  • Status: offline
Re: BM62 error while writing EEPROM 2020/10/02 06:59:27 (permalink)
4 (1)
I'm hoping a few of the posters above are still around:
 
Ryan posted:
Note that my eeprom appears to permanently stuck with "Can't connect to device". These days I just upload the full eeprom file with the isupdate.exe tool and select eeprom instead of flash. This seems to work for me consistently. I have done it probably 30 times now.
 
JUST MAKE SURE YOU SELECT THE CORRECT EEPROM FILE AND THE CORRECT SETTINGS IN YOUR FILE. The application is relatively bulletproof, but try it with one of the supplied files first. Once you have it going, you should be good in the future and you won't have to deal with all the can't connect bs
 
Regarding the "full eeprom file" is this different from the "ipf" file?
In my case, when I use the flash tool to write the ipf file, the BTM appears not to have received the correct file, BUT after doign so I AM now able to connect with the EEPROM tool for one successful programming. After that, the connection problem starts again.
 
It like the ipf file somehow precludes subsequent programming. (The ipf file was generated by Microchip support personnel, not me.)
 
 
Gerald
gcooper@bdesn.com in case you would rather respond privately.
#18
Jump to:
© 2021 APG vNext Commercial Version 4.5