Vista64 and Telnet Debugging (Wireless)

Archived
1

My wireless works fine - Roku plays back data just fine, I get no streaming errors, and I can connect to the debug port and brightscript debugger. It displays —running— I press control C, it gives me a lot of information and a prompt with a flashing cursor for the deviantart example - ie

roPinEntryDialogEvent
roPlugin
roPluginEvent
roPosterScreen
roPosterScreenEvent
roRegex
roSearchHistory
roSearchScreen
roSearchScreenEvent
roSlideShow
roSlideShowEvent
roSpringboardScreen
roSpringboardScreenEvent
roSystemLog
roSystemLogEvent
roTimespan
roVideoPlayer
roVideoPlayerEvent
roVideoScreen
roVideoScreenEvent
roUrlEvent
roUrlTransfer
roWebScreen
roWebScreenEvent
BrightScript Debugger> BrightScript Debugger> BrightScript Debugger>

the cursor is flashing at the bottom to the right of the >
Anything I type from here on out, no matter when I type anything, doesn’t produce any result. It’s as if the connection was instantly dropped.
What am I doing wrong or what could be causing this? Does everyone use wired ethernet for debugging on the Roku? running the latest 2.9 firmware.

2

If it makes any difference for troubleshooting, I can generate keys all day (apparently) with no timeout issues or disconnections through telnet to the box. It’s just the debugger routine that is having problems.

3

This happens to me as well from time to time. I just restart (unplug it from the wall) my roku and it functions for a variable amount of time afterwards.

4

I’ve noticed that pressing Ctrl-C sometimes allows debugging commands and sometimes doesn’t. It’s easy to tell when commands will be accepted. If you look at the screen and the box has exited the channel back to the main menu, you will not be able enter commands. Just start the channel and try again. When you can press Ctrl-C and have the screen remain in the channel, you’ll be able to enter commands. Another quick check is to type a question mark and return at the prompt. If you get another prompt, you’ll be able to enter commands.

It would be nice if pressing Ctrl-C always allowed debugging, but it doesn’t.

-JT

5

If there’s a specific place in the code that you want to debug, you can add “stop” to the code, and the debugger will automatically kick in at that point. That’s much easier than trying to time a CTRL-C.

6

Thanks! I’ll be using stop then as well as the other suggestions.

7

I believe I’ve had the same problem with ‘stop’ where it kicks you out of the channel, but I’m not positive.

-JT

8

The debugger will only work if:

  1. The first screen that was opened has not been closed. An exception to this would be something like this:

sub main()
stop
end sub

Which should just drop you into the debugger and let you play around. However something like this:

sub main()
screen=createobject(“roimagecanvas”)
screen.show()
screen.close()
stop
end sub

should kick you out of the debugger, because the app will never reach the stop statement.

  1. The app has not exited. To mess around with the debugger, kill an app that is running in the middle of a loop with control-c Don’t type exit, or close the currently visible screen, or you will exit the debugger. Would be nice if the debugger was always running, but that is not the case.
  • Joel
9

Others have said it, but just to be clear:

the debugger will only work when your developer app is running on the Roku box.

–Kevin