36 replies to this topic

[Dreambox_user]

@Erik Slagter and @pieterg: Thank you very much for your answers. It makes my view of the OpenPLi clearer.
However, would you be able to correct my thinking about the OpenPLi (C/C++ part) development chain? Are these points correct?
1. Implementation: modification in VIM.
2. Build: direct build for Dreambox using your makefile
3. Upload: upload to Dreambox
4. Run and debug: running gdbserver (with TCP and attaching to Enigma) on Dreambox
5. Connecting to gdbserver from other x86 machine using command-line gdb
Thank you very much in advance for your help.

[Erik Slagter]

If you're only developing or running enigma, most of the time it's sufficient to copy the enigma binary to the box and start it there.

If you mean to ask if there is a simulator (like for android etc.) then the answer is "no".

[Dreambox_user]

@Erik Slagter: Thank you. I know that there is no simulator (what a pity ).
However, most of my concerns are about the process of development so:
1. Do you modify C/C++ files locally on x86 machine, then build using the make and upload to the machine?
If so, how the process of debugging is going? Are you connecting from x86 machine to gdbserver,
places some breakpoints and then perform some actions on Dreambox and wait until your code is stopped by the debugger?
2. I have the same concerns about Python plug-ins development:
a. Implementation: modification in VIM on local x86 machine.
b. Build: No build but is it possible to validate the Python code before uploading on Dreambox?
c. Upload: upload modified files to Dreambox
d. Run and debug: running gdbserver (with TCP and attaching to Enigma) on Dreambox
e. Connecting to gdbserver from other x86 machine using command-line gdb
I’m sorry if my questions are not accurate enough but development for Dreambox is in some way different than I’m used to in x86/x64 machines and even well-documented mobile devices (like iOS, Android).
One more time, thank you for your help.

[Erik Slagter]

Do you already have a complete up-and-running OpenPLi Open Embedded build environment? That is where you compile things. The x86 compiler won't produce mips binaries...
BTW vim is a text editor.

Edited by Erik Slagter, 26 January 2012 - 13:58.

[Dreambox_user]

@Erik Slagter: Thank you!
Yes, I have complete OpenPLi Open Embedded build environment and yes, there I compile the stuff for Dreambox (MIPS) and I’m aware that I need to use cross-compiling and I know VIM very well (I mentioned this editor only for exemplary purpose, because personally I use another editor for modifying C/C++).
My previous post is focused rather on methodology because it’s difficult for me to efficiently introduce the changes and then run and debug my code (both C/C++ and Python) on Dreambox.

[Erik Slagter]

Hmmm, I don't understand the fuzz. Edit code, type make, correct compiler errors, type make again, copy binary to box, run binary. Where is the need for a IDE in this?

[Dreambox_user]

@Erik Slagter: Thank you! Now, I understand the process of the build and deployment on the device (that is great). Of course, IDE is not necessary, but testing/debugging is necessary and I would like to know how you debug the code. Do you use plain gdb in the shell to connect to the gdbserver on Dreambox or you use more sophisticated methods?
Thank you for your help!

[Erik Slagter]

Ah okay, now I understand what you mean. You are talking about the debugging part of the IDE.

As there is no specific IDE for OE, you will have to use gdb (and maybe gdb server).

Most of the time it's easier to include debug statements in the code than to use gdb anyway.

[pieterg]

connecting to a remote gdb target is supported by most ide's.
But I usually don't go through the hassle.
I debug my code with debug statements, and for the occasional hard to find segfault I run gdb on the stb, or use a coredump.
Happens only once or twice a year maybe

BTW, to speed up the process of moving the binary to the box, especially a large e2 binary with debug symbols, copy it to /tmp and run it from there.

[Sjaaky]

If you mean to ask if there is a simulator (like for android etc.) then the answer is "no".

Well there is actually, if I understand correctly. Look here: http://openpli.org/f...ntu-104-32-bit/ to compile enigma2 for a pc. You'll need a dvb device attached to your pc, or you'll need to forward a tuner to your pc using vtuner.

[Dreambox_user]

Hey,

how can I disable autorefresh pages in TuxTxt?

[littlesat]

What do you mean?

[Dreambox_user]

Oh I mean that one page can has subpages. Subpages are refreshing after some period of time. Is it possible to disable that?

[Meega]

When you press the back arrow ,then the page you are at ,will stay there.(some sort of hold)
And you can zap between pages.
If thats what you mean?

[theparasol]

Oh I mean that one page can has subpages. Subpages are refreshing after some period of time. Is it possible to disable that?

Searching & asked for that one a long time ago. PieterG said: wont fix, do it your self // said it a lot nicer but in essence the same

I'll try the backarrow, if that works its fine with me!

Edited by theparasol, 21 May 2012 - 21:11.

[jimux]

A certain amount of final diagnostic testing can be done on the enigma box once your code is installed. Open a telnet session and issue the command...
init 4; sleep 8; enigma2
Then some debug and event messages will route to the telnet session.

[Dreambox_user]

Hey again,

do anybody know how to check in tuxtxt.c if teletext is in subtitle mode?