A Forum at Sky's Edge

hey everyone, i got my kit last week and assembled it over the weekend. assembly went very smoothly (i think). i'm unfortunately having the following issues that i'm trying to sort out:

- phone turns on with a green LED under the dial (no white light near the bell). OLED displays STARTING. after this, phone becomes largely unresponsive. manipulating the dial does not display digits or trigger any lights (visually and audibly confirmed that the limit switch is triggering). buttons don't cause any visible changes. at one point, holding the phone button got the OLED to display CALLING (since trying to reflash firmware this is no longer the case, however). when turning the phone off, there is a delay and then the OLED says GOODBYE
- others have mentioned the e-ink display showing things on startup. mine does not. i've tried reseating the connector to no avail. screen does not appear physically damaged in any way.
- another thread suggested updating the firmware. i followed the instructions in the build documentation and ran into two issues. first, the IDE _really_ thinks that the phone is an ATmega 2560, not a 1280. As such, i can upload a sketch if the settings are set to 2560 but not 1280. i get green and amber lights near the bell during this process, but nothing particularly changes.

would love some thoughts on where to start looking to start getting this to work!

Also worth noting that I had a longer, and much more detailed version of this post written last night, but the forum ate it. Happy to provide documentation and describe tests I've run in more detail.

I've also completed assembly and found the device unresponsive with dial and buttons. Haven't tried updating yet, will go there next. My eink does show the initial RUSP message (the one with all the fonts), but I've found it's distorted when the case is assembled, normal with the case open. Not sure what's up with that.

Ah, my eInk display does nothing at all. I'll try fiddling with (and maybe replacing) that.

I'd be curious if anyone could disconnect their eInk display and test to see if that stalls boot or prevents the rotary dial from registering digits. My guess (hope?) is that the answer is yes.

The chip should indeed be a 2560. Some documentation may be out of date....

As for troubleshooting first check:

• do you see anything over serial?
• can you send AT commands over serial? https://github.com/skysedge/rusp_firmwa ... atsheet.md