I'm trying to get debug messages from the modules, but Debug.Write only crashes mc-Studio all the time. Can you point me in the right direction, please?

Setup used: mc-dev, mc-module 110, mc-Studio connected via TestBoardGateway

I've upgraded to the newest version and having several issues:

1) I've created a new project but building the project fails with "Build Failed: Could not find file C:\Users\MyUser\mcThings\Blinky\Blinky.lst"
2) I2C Error 32 I2cInvalidSdaPin when using I2c.Create(I2C_HiGH_SPEED, Pin.SCL, Pin.SDA, addr)

mcMod110 0.7-368
mcGate110 0.6-362 0.7-410

I've used one of those kits. http://amzn.to/2bFG98z

@kristofferis sure, I'll share the code here. But it was done before the mc-Things platform was declared proprietary instead of open source. Therefor I'm considering leaving this platform and will not develop this any further. Therefor github would be inappropriate.

Tom,

that's simply very unfair.

@Software:
Ok, I can live with your decision to close down the source code. I'm not really happy with that, but I accept it.
It's a pity because I wanted to add features to your platform, which you told me that wouldn't be added or are not planned at all.

@Hardware:
Now I want to make use at least of the hardware, not with your closed source because I don't want to support a proprietary solution which is completely useless for my needs. May I kindly remember you that you've also promised to make the hardware open source at the Kickstarter campaign. At the moment every sentence published there is not true anymore. The current status has nothing to do with the "reward" you've promised there.

Well, how would you feel in my situation?

Regards,
Helge

Hi Tom,

thanks for the clarification. Now I'm speechless, more than disappointed, upset and some other things which I won't post here.

I've thought about it for the last few days since you confirmed that software/hardware open source is not going to happen. In my opinion mc-Things does not act trustfully, you've promised too much and kept this information hidden from your supporting users until now. As mentioned within the direct messages on kickstarter it was and is a key argument for me to support this project and even more, to invest more money. I'm sure it was much more than the average. 

I do understand your decision regarding the investment, but it's your responsibility to arrange the requirements of your company and the promises made to your customers at the funding campaign. How you did that isn't truly honest.

Right now I cannot use the mc-things platform for my needs, just because you closed all doors and I cannot add the needed functionality by myself. What offends me much more is the fact that I can't even try to completely reprogram the firmware by myself, because you don't provide any schematics of the hardware in addition to the fact that I can't even get the mc-Module firmware back on those reprogrammed modules. Brilliant.

Really sad.
Helge

@mc-Abe

1) no, the connection to the module is still not working. In the meantime another module is also dead. OTA updates are still possible.
2) why does my code work within the ButtonPressed Event and bricked the mc-module in the Boot Event? Doesn't make sense.
3) hex file: read my in mc-Product General section here, which is still waiting for an official response here