Hi,
Using the done-in-a-day kit I have managed to turn a LED on and off connected toSCL.andSDAon the small board's (DA14531MOD-devkit-vC) mikroBUS, using the "DA14531 standalone (SET-TWO)" firmware. I also managed to test digital input setting the pins high and low, but when I configure for I2C using "AT+IOCFG=11,8" and "AT+IOCFG=8,7", and then run a "AT+I2CSCAN" with a I2C device connected to SDA and SCL, the system hangs for a while, after which it reboots (I believe), I have a heartbeat LED "AT+IOCFG=9,27" running, which suddenly turns off - assuming a reset/reboot.
我尝试过主板断开连接ed, powering the small board using the mikroBUS 3V and GND. Using the iOS app I then connect via BLE and run the same AT commands above, incl testing the LED's and digital input, all perfectly running, but the I2C is still just crashing.
Hi Gotfredsen,
Thanks for your forum post and for taking part in the “done-in-a-day”.
因此，您正在使用Flash Programmer工具中的Dodeless_531_Standalone_set_two.hex，并将模块连接到对等设备（iOS应用程序）后，连接丢弃。如果我错了，请纠正我。
Does the connection drop only when having I2C configuration? If you don’t have any I2C activity, can you replicate this behavior? Is the connection stable or it drops again?
Did you try to use the other two available pre-compiled images (codeless_531_datadump and codeless_531_standalone)?
Thanks, PM_Dialog
So it has nothing to do with a peer device. That was just to see if it made a difference from using PyTTY or similar Serial Terminal - and it didn't.
As you can see in the attached image, I have activate the LED on the small board using the Heartbeat function "AT+IOCFG=9,27"
I then configure the SDA and SCL and run a I2CSCAN as per the attached screenshot from my serial terminal program. After a minute or so (after the red arrow), it returns a dot (.) and on the next line "+READY" and the LED goes out.
Which is why I assume the boards resets after a while. I am trying without anything attached, but I have tried with many different I2C sensors, without luck.
And...
Heartbeat:AT+IOCFG=9,27
SDA:AT+IOCFG=8,8
SCL.:AT+IOCFG=2,7
扫描：AT+I2CSCAN
...but since I can't get to the Serial Console using PuTTY or similar, I use the iOS APP ... and I get same result, except I don't have to wait, it switches the LED off immidiately and drops the connection to my iPhone, so here I also expect a crash...
Hi Gotfredsen,
Thanks for your detail response. Please download the “SET_TWO” CodeLess firmware, connect the module with your iPhone and leave as it is ( without sending any of the available AT comments and without I2C activity). Can you replicate the connection drop?
Thanks, PM_Dialog
Iamusing SET-TWO, as mentioned before. There are no reset/reboot/connection drop, unless I issue an AT+I2CSCAN command.
Hi Gotfredsen,
请您使用附加的调试器运行它，并检查它是否堆叠在任何地方？您应该为调试启用开发调试（#define cfg_development_debug）。
Thanks, PM_Dialog
Hi,
Sorry for my ignorance, but does that mean I have to re-compile the SET_TWO, with the #define set, or is it at "thing" on the development boards?
If I have to recompile, I have an issue since the resulting code is larger than 32k, which is the limitation on my Kiel/uVision. I believe I have tried a while ago, and that this error came up, possibly on one of the other CODELESS version, but I can only imaging the SET_TWO is larger.
Thanks again for you assistance,
Bjarke
Hi Gotfredsen,
Yes – in order to run it in debug mode you should use the Keil IDE and attach the debugger. Would it be possible o do it?
Thanks, PM_Dialog