@stoffera So sorry. My mono make was seriously out of date, and I didn't realize it. Thank you!

I realize that this project doesn't seem to be alive any more (sadly) but hope someone can get me going again.

I'm unable to build hello_world, with this error output:

Compiling C++: app_controller.cpp
In file included from /usr/local/openmono/mono/include/mono.h:70:0,
from app_controller.h:8,
from app_controller.cpp:2:
/usr/local/openmono/mono/include/io/wifi.h:10:28: fatal error: wifi_interface.h: No such file or directory
compilation terminated.

The thing is, that wifi_interface.h file is definitely where it's supposed to be, and /usr/local/openmono/mono/include is in the path.

Thoughts, please?

Thanks!

@maz Yep, sure have. But, I'll try again tomorrow and report back.

@stoffera So I really did brick it then?

@stoffera It's not showing up in System Profiler, nor via monomake monoprog -d.

What can I try next, please?

Thanks!

@stoffera tried both; results per my original note above. I'm guessing I need to worry.

So, I was playing around with my first app, and as happens sometimes, I messed up somewhere. My device is now non-responsive.

Ok, no problem, right? This thing's got to have a reset button somewhere. Oh, there it is! And there are the instructions on how to reset it back to the bootloader.

But, I have followed the instructions 6 or more times now, and the device is still - for all intents and purposes - dead.

I even peeled off the back of the case just to make sure I was really depressing the reset switch. No love.

Occasionally, tantalizingly, monoprog detects it as available and running an app:

Mono device running app detected.

but then I can't successfully make install:

Resetting Mono device to start bootloader
Programming Mono device with hallowelt.elf...........
Mono device not detected on USB ports.
No connection to Mono device.
make: *** [install] Error 2

Worse, after another attempted reset, monoprog goes back to not seeing the device at all.

Thoughts?

Thanks!

Now I've got a different problem, in that I appear to have bricked my device, and can't get it to respond to my reset. (With paperclip and user button.)

@pktm OK, so the trick with minicom was related to settings. Not only did I have to put it to 9600bps, I also had to turn hardware flow control off and save the settings as minicom defaults. ($ minicom -s).

I'm documenting that here to help others, and I'll add it to the serial debug article in the docs, too.

@maz Thanks for the reply.

I changed the bit rate in minicom, but I'm still not seeing any output, frustratingly.

I guess I should have posted the full switch block, but it doesn't use the rand() value directly:

    switch (newColorCase) {
        case 0:
            helloLabel.setTextColor(display::WetAsphaltColor);
            break;
//...

Thanks!