I keep getting an exception thrown when converting strings to byte[].
The code increments a counter in a loop and writes the bytes out to COM1.
Inspecting the variables when an exception is thrown shows everything is OK.
The exception is thrown at various times (under 30sec it seems) and various counter values.
The code is shown further below
Any ideas as to what is happening?
Also, the output of the serial port “SOMETIMES” changes to like debug output, shown below:
@ mhardy - I have not tried this and I do not have a G120 so I am not going to even try guess what the issue is (though I do have a gut feeling)… what would like to ask is that you try something a little different to confirm that the issues is where it looks like it is or is it just an artifact of something else.
Rather than access the UTF8 property every iteration, cache and instance of the encoder. For example
@ mhardy - I’ve had your code running for over an hour now with no issue, both with and without the sleep. If you haven’t already, I would reflash the loader and firmware, then I would try a second Cobra II, cable, connector, and computer.
Yes, I started off running a much larger program (multiple serial ports, ethernet, SD Card, CAN…). The program crashed, so I tried to minimize scope, i.e. a simple serial port sending out data.
I have been stuck in the debug mode for about a week now!
I really want to send the board to you for evaluation. We are desinging a board based on the G120…we need to know the root cause of this problem!
Can you tell me what voltage I should supply via the power jack. I have heard, thru the forum, anywhere from 6V to 12V? The webpage says anywhere from 7-30VDC. Note: I will also have the USB (client) debug cable connected.
So, the plan will be:
1.) Try a different RS232 module.
2.) Try a different USB cable.
3.) Re-flash everything.
4.) Try a different Cobra II (eco)
If I need to get a new Cobra II, will you guys find the root cause of the failure if I ship the board to you?
@ John - FYI, I had to go with TeraTerm last week. Couldn’t update my Cobra II using FEZ Config. COM Port was visible in Device Manager, but FEZ Config acted like it was not.
Using Fez Config I updated Tiny Booter and by default the Firmware (TinyCLR, netMF).
Reloaded my application and ran it.
Same results, crash report after ~30sec.
Is it agreed that my Cobra II (eco) has some problem / defect?
I would like to ship this one back and get it evaluated for root cause.
I will order another Cobra II (eco) and hopefully all goes well.
Does this sound like best method to keep moving forward?
Aside from above, It’s not clear how to update Tiny Booter manually?
The COM port is not visible in Device Manager until I run Fez Config to update Tiny Booter.
Once Tiny Booter starts loading, Fez Config says it found COM 3, and COM3 shows in device manager. After Fez Config is done loading stuff, COM 3 disappears from device manager?