请问哪里能找到信息描述接口协议的BM78在EEPROM写模式？

有什么事吗？没有从我的支持票，没有信息的文件，这是胡说八道。



      以下为原文

    Anything? No answer from my support ticket, no info in the docs, this is nonsense.

你可以在24小时后打电话来加快反应速度。



      以下为原文

    You can call after 24 hours to speed up a response.

我没有答案，但我确实有一些建议：步骤1：首先使用SDA/SCL管脚通过I2C作为EEPROM转储工厂配置。我能做到这一点没有太多的麻烦使用树莓PI。可下载的“工厂”配置不具有在开发代码时可能覆盖的所有数据。我猜在工厂里也有一些单位修剪配置。大概，你也可以通过I2C编写EEPROM，但是你必须让BM78禁用写保护，如果你要这么做，你最好在整个BM78协议上都这样做。至于协议本身，哟你可以用逻辑分析仪来分析它，并观察Windows工具的工作原理。我自己还没弄清楚，但我已经很接近了。我不愿意通过张贴一个关于（故意？）的详细猜测来激怒论坛神灵。未发布的协议。由于我通过写入坏数据半砖块化了单元，因此当前处于暂停状态，并且我没有完整的工厂配置要恢复（参见步骤1…）



      以下为原文

    I don't have an answer, but I do have some advice:
 
 
Step 1:
I would start by doing a dump of the factory configuration as an EEPROM via I2C using the SDA/SCL pins.  I was able to do this without too much trouble using a Raspberry PI.  The downloadable "factory" configs don't have all of the data that you might overwrite while developing your code.  I'm guessing there is some per-unit trimming config done at the factory.
 
Presumably, you could write the EEPROM over I2C as well, but you'd have to get the BM78 to disable write protect, and if you're going to do that, you might as well do it all over the BM78 protocol.
 
As for the protocol itself, you may be able to figure it out with a logic analyzer and watching the Windows tool work.  I haven't quite figured it out myself, but I've gotten pretty close.  I hesitate to anger the forum gods by posting detailed guesses about an (intentionally?) unpublished protocol.
 
I'm currently on hold since I've semi-bricked my units by writing bad data, and I don't have the full factory config to restore (see step 1...)

顺便说一下，你仍然需要协议，甚至使用I2C来读取它。在不知道确切的协议的情况下，我只能测试2种定义良好的方式——读取7位地址空间和10位地址空间。i2c的规格说明这些空间是分开的，而某些设备可能希望合并这些空间，从而通过两个映射访问相同的数据。有些设备可以通过单独的空间访问不同的数据部分。我不知道里面有什么BT78。我也担心“半砖”的状态…不愿意冒险。我完全没有办法在线上记录UI工具的传输，而且sw工具并不总是稳定的。而且反正我没有EV板，所以我仍然需要与UI工具兼容的u***-to-串行转换器。希望它是非常标准的串口，不需要额外的GPIO引脚。你有什么想法吗？谢谢



      以下为原文

    BTW, you still you need the protocol even to use I2C to read it. Without knowing exact protocol I can only test 2 well-defined ways - read 7-bit address space and 10-bit address space. Specs for i2c tell those spaces are separate, while some devices might want to merge it, giving access to same data via both mappings. Some devices might give access to different parts of data via separate spaces. I don't know what's in there with bt78. I am also worried about the "semi-bricked" state ..... not willing to risk it really. I definitely have no hw to record UI tool transfers on the wire, and sw tools is not always stable.
And anyway I don't have the EV board, so I still need u***-to-serial converter compatible with UI tool. Hopefully it's pretty standard serial port, without additional fancy gpio pins. Do you have any idea about it ?
THX

更多信息：我们已经在线检查了所有的官方文档（在bm78页面上），并且所有这些文档都主要涉及评估板和一些Win配置工具。但我们需要确认，评估板是使用标准的USB到串行转换器。我们没有EV板，所以我们必须使用一些其他的u***串行转换器，很可能是基于FTDI的ft232芯片，而不是微芯片转换器。如果我们想要更新模块的固件（不太可能，但仍然可能），我们必须用u***-to-serialconverter将模块连接到窗口。不可能像在插件SD卡上放置特殊文件那样进行更新。MCU可以从SD读取更新，但是没有协议，它不能更新模块的内存。那些在线文档不告诉我们细节，但是UI工具使用在EV板手册中描述。同样的板是用来实际模拟串口，所以必须有u***到串行转换器，连接到模块的uart引脚。但我们需要确认，只有那些引脚用于编程。外部交换机会拉下模块的引脚进入eeprom写/测试模式，而u*** toserial转换器会直接将数据馈送给模块，即使我们不知道协议。然而，我们需要通过MCU访问Bt模块，正如官方营销材料中所宣传的：“易于配置用户界面（UI）工具，Windows∈配置实用程序或直接由MCU配置。如何从MCU直接配置它？这仍然是一个谜：THX



      以下为原文

    Some more info: we checked already all the official documentation online (at the bm78 page) and all those docs mostly refer to the evaluation board and to some Win config tools. But we need confirmation that the evaluation board is using standard u*** to serial converter. We don't have EV board, so we'll have to use some other u*** to
serial converter, most likely based on ft232 chip from FTDI, not microchip's converter. If we would want to update module's firmware (not likely, but still possible) we'd have to connect that module to windows with u***-to-serial
converter. It won't be possible to make update as simple as placing special file on plugged sd card. MCU could read update from sd, but without protocol it can't update module's memory. And those online docs don't tell us details, but UI tool usage is described in EV board manuals. Same board is used to actually simulate com port, so there must be u*** to serial converter, connected to module's uart pins. But we need confirmation that only those pins are used for programming. External switch would pull down module's pins to enter eeprom write/test mode, and u*** to
serial converter would feed data directly to module, even if we don't know the protocol.
However we need to access the Bt module via MCU as advertised in the official marketing material: "Easy to configure with User Interface (UI) tool, a Windows® configuration utility or directly by MCUs".
How can we do to configure it directly from the MCU ? This still remains a mistery :)
THX

嗨，有2种不同的产品使用相同的硬件模块：BM78和RN467。RNXXXX风格是基于命令的，并且使得从外部MCU更容易控制。也许你想要做的是使用RN467 8更容易？如果你需要呆在BM78上，那么我建议你给MyCyPigGARD提交一张网络票。



      以下为原文

    Hi,
There a 2 different products using the same hardware module : BM78 & RN4678.
the RNxxxx style is command based and makes it much easier to control from an external MCU.
Maybe what you want to do would be easier using RN4678 ? 
If you need to stay with BM78, then I suggest you submit a webticket to Microchip
Regards
 

HISRC，THX的答复。我们正在建造一些HW原型，我们需要一个BT模块，为此我们建议使用BM78。现在我们有3个（已经焊接），我们希望使用它们，而不是开始使用一个新的模块。将尝试WebTICKET.THX



      以下为原文

    Hi RISC,
thx for the reply. We are building some HW prototypes and we needed a BT module and for this we have been suggested to use the BM78. Now we got 3 of them (already soldered) and we want to use them rather than start using a new modules. Will try the webticket.
THX

根据我所听到的，BM7X模块的文档功能不足。您可以尝试与评估模块一起使用的库。但是我也建议移动RN46X模块。这是可能的，因为他们有相同的硬件，你也许可以改变固件。但我从来没有听说过。我可以更换模块，而不用轻蔑合金提升垫。



      以下为原文

    From what I hear the BM7x modules have insufficient documentaction. You can try the library that goes with the evaluation module.
But I was advised to move the the RN467x modules too.
It is possible that since they have the same hardware you maybe able to change the firmware. But I never heard back on that.
I was able to replace the modules without lifting the pads with despisers alloy.

但到目前为止没有运气。似乎不可能直接从MCU切换到配置模式，而不修改固件（这同样不可能通过MCU）。感觉几乎被骗了，但是希望通过支持服务找到一个解决办法。



      以下为原文

    THX but so far no luck. It seems impossible to switch into configuration mode directly from the MCU and without modifying the firmware (which again is impossible just via the MCU). It feels almost as cheated but hope to find a solution via the support service waiting their answer on this.
THX

您可以用Chipqick SMD1NL移除模块。如果您想尝试RN467X模块，这将很有帮助。正如我所说的，我们没有运气。



      以下为原文

    You can remove the Modules with Chipqick SMD1NL.
This would be helpful if you want to try a RN467X module.
 
AS I said, we had no luck with the ticket.

谢谢。。。。但对我来说，BM78可能会更容易，可能会切换到RN467。



      以下为原文

    Thx .... but for me might be easier ditch the BM78 and to switch probably to the RN4677

在数据表2-1中，将x5NC2的P2_0、P2_4、EAN设置为（LHH）或将x5MC2的LHL设置为写EEPROM模式，然后按照IS1678 UART命令集用户指南设置大多数参数。您可以使用UB-UART桥进行流量控制或不进行流量控制。通常，更新固件需要流量控制。如果不熟悉协议，可以在执行任何WRITE命令之前尝试几个READ命令。但是写命令通常会有一个StureSype选项标志，它决定存储到EEPROM（E2PROM）或不。



      以下为原文

    In the datasheet Table 2-1, you set the P2_0,P2_4,EAN to (LHH) for x5NC2 or (LHL) for x5MC2 to the Write EEPROM mode.
 
and then following the IS1678 UART Command Set User Guide to set most of the parameters.  You can use USB-UART bridge with flow control or without flow control.  Usually, flow control is required for updating the firmware.
 
If you are not familiar with the protocol, you can try a couple of READ command before doing any WRITE command.  But the WRITE command usually will have a Store_Option flag which decides to store to EEPROM(E2prom) or not).

你好，谢谢你的回复。我相信有一些误解，也许我用错误的方式解释了一些事情。UART命令列表有一列，当命令有效时标记。一些命令只在配置模式下有效，而另一些命令在手动模式模式下有效。配置模式仅在模块在自动模式模式下运行时可用，并且如果在eeprom中没有禁用配置模式。我在uart命令集中没有看到任何关于p2_0、p2_4、EAN引脚的内容。所以我没有看到认为是1678 UART命令集用户指南适用于EEPROM写模式，是由Windows UI/EEPROM工具使用的。还有关于EAN pin的困惑。在我们的第一个原型中，我们没有连接，模块在应用模式下工作。现在你建议把它放低。阅读EV板用户指南，我发现EAN的SW4开关在打开位置时用10欧姆连接到VDD_IO，在eeprom写入模式下工作需要该开关处于关闭位置。当SW4为ean关闭时，示意图不能告诉EAN连接到任何地方。这是否有意义或帮助您更好地理解我们的问题？谢谢



      以下为原文

    Hi Timijk
thank you for the reply. I believe there's some misunderstanding and probably I did explan something in the wrong way. Uart commands list has a column, marking when a command is valid. Some commands are valid only in configuration mode, while other valid in manual pattern mode.
Config mode is only available when module is running in auto pattern mode, and if config mode wasn't disabled in eeprom.
I didn't see anything in uart command set talking about p2_0,p2_4,EAN pins.
So I don't think IS1678 uart command set user guide applies to eeprom write mode that is used by windows UI/eeprom tools. Also there's confusion about EAN pin. In our first proto we left it unconnected, and module is
working in application mode. Now you are suggesting to set it low. Reading EV board user guide I see that SW4 switch for EAN connects it with 10ohm to VDD_IO when in ON position, and working in eeprom write mode needs that switch in OFF position. Schematic diagram doesn't tell EAN is connected anywhere when SW4 is OFF for ean.
Does this make sense or help you to better understand our issue ?
THX

手动模式或自动模式是将BM77置于正常操作/应用模式。另一种模式称为测试模式，即当我们想要升级固件（FLASH）或将一些设置写入EEPROM或执行一些测试……这是我对文件的理解。



      以下为原文

    The Manual Pattern or Auto Pattern is when we put BM77 in NORMAL Operation/Application Mode.  The other mode is called TEST Mode, that's when we want to upgrade the firmware(FLASH) or write some setup into EEPROM or do some TEST.... this is my understanding from the document.
 
   Attached Image(s)

如何通过MCU进入配置模式（在FW中禁用）？



      以下为原文

    How to enter the config mode (seems disabled in fw) via MCU ?

设置用于测试模式的2200、2Y4、EA/L的L/H值并重置该设备。我不确定您在测试模式中必须保留这些值多长时间。



      以下为原文

    Set the L/H values of the P2_0,P2_4,EAN for the TEST mode and RESET the device.  I am not sure how long you have to keep those values during the TEST mode.

基本上我就是这么做的。除了EAN没有接触之外，因为在EV板原理图中，当SW4处于断开状态时，EAN没有下拉电阻。也就是说，EV板显示测试和应用模式在Py0 0开关中只是不同，这就是为什么我只焊接了2200引脚。我把它拉下来，然后重置设备，我看到LED不断发光（有些意思？）但是eeprom工具不能编写eeprom更新，可能是因为它没有直接连接到模块，但是在两个串行端口之间存在“cat”管道。



      以下为原文

    Basically that's what I did. With the exception of EAN left untouched, because in EV board schematic there's no pull-down resistor for EAN when SW4 is in disconnected state for ean pin. I.e. EV board shows that TEST and Application
modes only differs in p2_0 switch, that's why I soldered only p2_0 pin. I pull it down, then reset device, I see led constantly glowing (some meaning?), but eeprom tool can't write eeprom updates, probably because it's not directly
connected to module, but there's 'cat' pipe between two serial ports.