Omnimaga
Calculator Community => TI Calculators => General Calculator Help => Topic started by: merauder75 on February 22, 2011, 02:06:01 pm
-
Hey,
I dont know if these is against the rules to ask this (I apologize if it is), but can someone who figured out the infernal setup of the development environment for ndless post a working precompiled copy for download?
I have tried following the compile directions, and got all of the tools set up(YAGARTO and the like), and it sort of compiles, but comes up with errors and fails to finish. I see no reason why one of the devs cant just post an unstable copy (yes, i know that frequent changes are made, but any copy of the Ndless 2.0 is better than no copy). I am sort of getting sick of dealing with OS 1.7 on my Nsipre and having to use the ugly mismatched clickpad (a petty complaint, i know). Is anyone willing to do that for those who lack the time, patience, and luck to successfully compile it themselves?
-
I am fairly certain that if you post the error logs people would be happy to help you compiling it. Ndless 2.0 installer isn't distributed because then we would have to deal with an extra group of people that don't read readmes who would install Ndless without worrying about what is it compatible with then end up bricking their calc (or rendering it temporary unuseable but think it's broken) then they would yell at us accusing us of giving them buggy softwares. Since that kind of people will usually not go through the process of trying to compile softwares or even ask for help compiling it, Ndless 2.0 was made that way until it comes out of beta.
Sorry for the inconveniences.
-
Ah, i see, that makes a lot more sense, well, ill give compiling another go maybe, and see exactly what error I ran into, it had to do with the nspire-ld component not working.
-
Ok, good luck, but please post the error log text if you get any. Hopefully that should help people pointing you in the right direction.
-
OK, heres the error I get when I try to build something using msys:(maybe the thread name should be changed, oh well)
Greg@GREG-WIN7 /c/Users/Greg/Documents/ndless2/samples/hello
$ ls
Makefile hello.c
Greg@GREG-WIN7 /c/Users/Greg/Documents/ndless2/samples/hello
$ make
nspire-gcc -Os -nostdlib -Wall -W -marm -c hello.c
nspire-ld -nostdlib hello.o -o hello.elf
c:/program files (x86)/yagarto/bin/../lib/gcc/arm-none-eabi/4.5.2/../../../../arm-none-eabi/bin/ld.exe: cannot find -lndls
collect2: ld returned 1 exit status
make: *** [hello.tns] Error 1
I have installed YAGARTO properly, i think? I do have a clean XP system I can redo a setup on, on a seperate partition, I have also tried linux mint, but with even less sucess.
-
I think you have to add the ndless directory to your system path, but I'm not certain.
-
Yeah, its added in the Windows system path, it and Yagarto's stuff are added, here my system path:
C:\Program Files (x86)\ATI Stream\bin\x86_64;C:\Program Files (x86)\ATI Stream\bin\x86;%CommonProgramFiles%\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\yagarto\bin;C:\Users\Greg\Documents\ndless2\bin;C:\Program Files (x86)\Common Files\GTK\2.0\bin
I think thats correct.
-
"lndls" is a Ndless library file - looks like you're trying to compile the programs before you have compiled Ndless. You must first run the makefile in the ndless root, to get the libraries and other things you'll need to compile the programs themselves.
EDIT: Judging by your log, your program is actually getting compiled, and it's just the linker that's failing (since you haven't compiled the library yet), so I really think you've done everything correctly, except for running the wrong file. It should be all good after that.
-
Yay! Hello world compiles! You sir, are awesome! :thumbsup:. However, i still cant figure out how to get the whole thing to compile so that I get the ndless installer.tns file so I can upgrade to 2.0(or 2.1?) and play Doom.
-
Also, heres the error I get when building in the root, I just built the libndls manually from its folder.
Greg@GREG-WIN7 /c/Users/Greg/Documents/ndless2
$ make
make all in tools...
make[1]: Entering directory `/c/Users/Greg/Documents/ndless2/tools'
make all in build...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/tools/build'
cp nspire-gcc nspire-ld nspire-as ../../bin
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools/build'
make all in MakeLoader...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/tools/MakeLoader'
gcc -W -Wall MakeLoader.c -o ../../bin/MakeLoader.exe
make[2]: gcc: Command not found
make[2]: *** [MakeLoader.exe] Error 127
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools/MakeLoader'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools'
make: *** [subdirs] Error 1
What exactly is wrong with makeloader?
-
Can you run a "make clean all" instead of just "make", so that we can see the whole log? It's strange that it can't find "gcc", though...
EDIT: This is definitely a path issue, looking at it again. Give me a few moments to recheck where gcc should be (Yagarto, MSYS, Mingw, I forget...).
EDIT2: You've installed yagarto in C:\Program Files (x86)\, judging by your path. If I remember correctly, Yagarto doesn't like special symbols in its filepath; Try uninstalling Yagarto completely, then reinstalling it in C:\YAGARTO or something similar (avoiding brackets, and also spaces just in case). I remember having some issues on my Win7 box with this.
-
Ok, here you go,
Greg@GREG-WIN7 ~
$ cd C:/Users/Greg/Documents/ndless2
Greg@GREG-WIN7 /c/Users/Greg/Documents/ndless2
$ make clean all
rm -rf dist
Clearing in tools...
make[1]: Entering directory `/c/Users/Greg/Documents/ndless2/tools'
Clearing in build...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/tools/build'
cd ../../bin && rm -f nspire-gcc nspire-ld nspire-as || :
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools/build'
Clearing in MakeLoader...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/tools/MakeLoader'
rm -f ../../bin/MakeLoader.exe
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools/MakeLoader'
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools'
Clearing in libndls...
make[1]: Entering directory `/c/Users/Greg/Documents/ndless2/libndls'
rm -rf *.o *.elf *.a
rm -f ../lib/libndls.a
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/libndls'
Clearing in arm...
make[1]: Entering directory `/c/Users/Greg/Documents/ndless2/arm'
rm -rf *.o *.bin *.elf *.xml *.zip
rm -rf ../calcbin/ndless_installer*.tns ../calcbin/ndless_resources.tns
make all in tests...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/arm/tests'
rm -f *.o *.elf
rm -f ../../calcbin/tests/ndless_tests.tns
rm -f ../../calcbin/tests/ndless_keys.tns
rm -f ../../calcbin/tests/ReadMe.txt
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/arm/tests'
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/arm'
Clearing in samples...
make[1]: Entering directory `/c/Users/Greg/Documents/ndless2/samples'
Clearing in hella...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/samples/hella'
rm -f *.o *.elf
rm -f ../../calcbin/samples/hella.tns
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/samples/hella'
Clearing in hello...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/samples/hello'
rm -f *.o *.elf
rm -f ../../calcbin/samples/hello.tns
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/samples/hello'
Clearing in particles...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/samples/particles'
rm -f *.o *.elf
rm -f ../../calcbin/samples/particles.tns
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/samples/particles'
rm -f ../calcbin/samples/ReadMe.txt
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/samples'
rm -rf calcbin
rm -rf bin lib
make all in tools...
make[1]: Entering directory `/c/Users/Greg/Documents/ndless2/tools'
make all in build...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/tools/build'
cp nspire-gcc nspire-ld nspire-as ../../bin
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools/build'
make all in MakeLoader...
make[2]: Entering directory `/c/Users/Greg/Documents/ndless2/tools/MakeLoader'
gcc -W -Wall MakeLoader.c -o ../../bin/MakeLoader.exe
make[2]: gcc: Command not found
make[2]: *** [MakeLoader.exe] Error 127
make[2]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools/MakeLoader'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/tools'
make: *** [subdirs] Error 1
Greg@GREG-WIN7 /c/Users/Greg/Documents/ndless2
$
-
Hmm, nope, still complaining about MakeLoader. ???
-
Hmm, you did install MinGW alongside MSYS, right? I just realized it can't be your Yagarto installation, because MakeLoader is a x86 program, and not ARM.
I remember having tremendous issues getting MinGW/MSYS to work the first time around, but at the same time I also wrote a .txt file for myself noting what I did (well, it's mostly copy-paste from other assorted documents, plus a few personal notes), just so I could do it again if I had to reinstall Windows for some reason. It might help, it might not, but here it is anyway:
The total size of the installation of MSYS/MinGW is around 110 MB. Be sure to have enough space on your hard disk.
If you haven't already installed MinGW on your system, install MinGW in C:\MinGW. It is better to not install it in the same directory than MSYS, though there should be no problem since MSYS 1.0.11. In the installer, choose "Download and install", then "Current" (it will install gcc 4.4.0).
Install MSYS 1.0.11. I usually install it in C:\msys\1.0, but you can use any directory that you prefer.
Check http://sourceforge.net/projects/mingw/files/ for more recent versions of all these files.
Next, the post install process will ask for the directory where MinGW was installed to. Enter "c:/mingw". If you make a mistake, you can change it by editing the "C:\msys\1.0\etc\fstab" file, make sure to use 'LF line endings. An example fstab may contain:
c:/mingw /mingw
c:/java /java
Install MSYS DTK 1.0 in C:\msys\1.0.
Install MSYS Core 1.0.11. It is an archive. Untar it in C:\msys\1.0.
Set the environment variable HOME to C:\msys\1.0\home
Update GCC to 4.5.0 using the gcc-core-4.5.0-1-mingw32-bin package
-
ok, it got farther this time, however, no more MakeLoader problems, however, heres a new one.
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/libndls'
make all in arm...
make[1]: Entering directory `/c/Users/Greg/Documents/ndless2/arm'
nspire-as -Os -nostdlib -Wall -W -Wno-strict-aliasing -D _NDLS_LIGHT -D STAGE1 -mthumb-interwork -mthumb -D OS_VERSION=1_7 -D OS_VERSION_INT=17 -c bootstrappe r.S
nspire-gcc -Os -nostdlib -Wall -W -Wno-strict-aliasing -D _NDLS_LIGHT -D STAGE1 -mthumb-interwork -mthumb -D OS_VERSION=1_7 -D OS_VERSION_INT=17 -c stage1.c
nspire-gcc -Os -nostdlib -Wall -W -Wno-strict-aliasing -D _NDLS_LIGHT -D STAGE1 -mthumb-interwork -mthumb -D OS_VERSION=1_7 -D OS_VERSION_INT=17 -c ints.c -o ints_light_thumb.o
nspire-gcc -Os -nostdlib -Wall -W -Wno-strict-aliasing -D _NDLS_LIGHT -D STAGE1 -mthumb-interwork -mthumb -D OS_VERSION=1_7 -D OS_VERSION_INT=17 -c syscalls.c -o syscalls_light_thumb.o
nspire-gcc -Os -nostdlib -Wall -W -Wno-strict-aliasing -D _NDLS_LIGHT -D STAGE1 -mthumb-interwork -mthumb -D OS_VERSION=1_7 -D OS_VERSION_INT=17 -c utils.c -o utils_light_thumb_os-1.7.o
nspire-gcc -Os -nostdlib -Wall -W -Wno-strict-aliasing -D _NDLS_LIGHT -D STAGE1 -mthumb-interwork -mthumb -D OS_VERSION=1_7 -D OS_VERSION_INT=17 -c syscalls-l ight_ncas-1.7.c
nspire-gcc -Os -nostdlib -Wall -W -Wno-strict-aliasing -D _NDLS_LIGHT -D STAGE1 -mthumb-interwork -mthumb -D OS_VERSION=1_7 -D OS_VERSION_INT=17 -c syscalls-l ight_cas-1.7.c
nspire-ld --no-startup -nostdlib bootstrapper.o stage1.o ints_light_thumb.o sys calls_light_thumb.o utils_light_thumb_os-1.7.o syscalls-light_ncas-1.7.o syscal ls-light_cas-1.7.o -o ndless_installer_os-1.7.elf
"/c/YAGARTO/bin/arm-none-eabi-objcopy.exe" -O binary ndless_installer_os-1.7.el f ndless_installer_os-1.7.bin
../bin/MakeLoader ndless_installer_os-1.7.bin Document.xml
'ndless_installer_os-1.7.bin' successfully created (22528000 bytes written)!
rm -f ndless_installer_os-1.7.tns ndless_installer_os-1.7.zip
"" a ndless_installer_os-1.7.zip Document.xml
/bin/sh: : command not found
make[1]: *** [ndless_installer_os-1.7.tns] Error 127
make[1]: Leaving directory `/c/Users/Greg/Documents/ndless2/arm'
make: *** [subdirs] Error 1
Yeah, I cant get the whole thing pasted in without being rediculously long, isnt it suppposed to be compiling ndless 2.0? not v1.7?
-
Ok, I give up :banghead:, can someone please just like, email me a copy? I dont expect any special treatment, but this is just rediculous, when will this go into beta anyway?
-
Could any of these issues be specific to OS version and if you got 32 or 64 bits? I am curious if Ndless compilers are cross-OS compatible.
As for Ndless 2.0 final version it should take between one week and 3 years to go out of beta, according to the time between Ndless 1.0 and 1.7 final releases. You have to be patient as the creators got something called a life.
Also don't double-post, use the modify button when it has been a short amount of time between posts. Most TI-Nspire users live in different timezones, so it can take a few days before replies sometimes.
-
merauder, I believe you have to add the root directory of 7zip to your path.
Seconding DJ's comments as an Nspire developer myself, work on projects, especially those as tedious as Ndless, can take a long time to get working. Ndless 2 is available for download for developers so they can update their projects to be compatible with newer versions and so they can provide good bug reports. The reason why you have to be able to build Ndless youself is because it is assumed that you are a Nspire Developer if you are able to build it.
At Omninmaga, I, along with many other members, will be perfectly willing to give you help in building Ndless, but, if we were to give one person a copy, everyone would start expecting one for themselves too. :)
-
Yeah, sorry, just got a tad frustrated, thats all :-[, yeah, I understand, I can wait for it to come out of beta, also, I did add 7 zip to the path, still no luck, ah well.
I do appreciate all the help I do get here on the forum though. Thanks
EDIT: Oh yeah, I am on a 64 bit system, that might be it, I dunno. Also, I didnt use edit b/c the editing doesnt work well with extremely long posts
-
Thirded. Ndless is pretty interesting, but it's extremely alpha - you should expect nothing (and only nothing) to work.
SVN repository code is usually very volatile (basically, extremely likely to have broken stuff), and Ndless is no exception. (The only SVN that isn't too bad is TiLP, which sometimes has major fixes not found in the regular releases. However, it's probably volatile right now, since libusb-1.0 support is being added.) Exploit discovery and internal probing is one of the major things that make Ndless what it is, and that takes *quite* a while. Then you got to set up an environment for developers to play in - basically, letting people like apcalc and you make programs for the calc without resorting to extreme hacking. And then you gotta make it stable - crashing every time doesn't sound too good, right? ;)
As you can see, it takes a LOT of work to produce a product. Plus the addition of life, it's not going to be fast. However, the end result is a MUCH stabler end product, and more happy people (and developers)! :D
Granted, if you are a serious developer that is willing to help (and not just toss it onto your Nspire and expect things to work), you're free - in fact, ENCOURAGED to compile and help out! :) Otherwise, compiling and installing it may not be a good idea, since as I've said, the code is volatile, and it's going to crash a LOT, not mentioning a possibility of bricking. (I emphasize this a lot - you will need to buy a new Nspire if it does indeed brick, and it's not cheap.)
-
Ok, thanks, honestly, I only have a small amount experience in developing, Im actually just getting into programming in a serious way now(I only know a little C++, C#, and Python), I just figured calculators are the best place to start, since, looking at some of the code, I actually sorta grasped some of it (iphone jailbreaking code, ehh, not so much). Im going to start taking classes in C and ARM assembly soon, so this is why I wanted to set up the dev environment (that and the DOOM thing), I probably wont be able to contribute much, since im fairly new to coding.
Also, to me, bircking a calculator isnt a concern, I've un-bricked an iphone, a wii, an xbox 360, im sure an nspire will be no problem if it does.
Well, I hope ill be at least somewhat useful once I figure out this setup.
Oh yes, I do understand that "developers have a life too" concept, believe me, I do
-
Yeah, its added in the Windows system path, it and Yagarto's stuff are added, here my system path:
C:\Program Files (x86)\ATI Stream\bin\x86_64;C:\Program Files (x86)\ATI Stream\bin\x86;%CommonProgramFiles%\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\yagarto\bin;C:\Users\Greg\Documents\ndless2\bin;C:\Program Files (x86)\Common Files\GTK\2.0\bin
I think thats correct.
the path to 7zip is missing...
therefore it fails when it tries to zip ndless
I guess it is; C:\Program Files\7-Zip
-
No, sorry, I changed it, thats not my current one, here it is:
C:\Program Files (x86)\ATI Stream\bin\x86_64;C:\Program Files (x86)\ATI Stream\bin\x86;%CommonProgramFiles%\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files\TortoiseSVN\bin;C:\Users\Greg\Documents\ndless2\bin;C:\Program Files (x86)\Common Files\GTK\2.0\bin;C:\YAGARTO\bin; C:\7Zip
-
Make sure the folder contains 7z.exe.
-
As you might have guessed, merauder75, getting things set up under *nix is probably easier than getting them set up under Windows.
alberthrocks:
The only SVN that isn't too bad is TiLP, which sometimes has major fixes not found in the regular releases. However, it's probably volatile right now, since libusb-1.0 support is being added.
The experimental libusb 1.0 support has not been committed yet, it's just available under the form of a patch (not complete yet) to be applied on top of SVN HEAD. And anyway, it defaults to disabled, so there's no volatility :)
The libusb 1.0 backend is needed because most Linux distros aren't shipping the full versions of both libusb 0.1 and libusb 1.0 anymore, they're shipping libusb 1.0 + the 0.1 compat layer for 1.0 (which does not work for the purposes of libticables) instead.
-
Yes, the folder does contain 7x.exe, also, I tried the linux setup( I have a triple boot of 7, XP, and Linux Mint), and it was even worse.
There is zero compatibility with Mint, even though its just ubuntu with a different UI.
-
Beta binaries (http://ourl.ca/9367) are now available to avoid wasting your time.
-
Yay! :)
Oh, I can do any testing with the touchpad if you want
-
Yay! :)
Oh, I can do any testing with the touchpad if you want
I likewise can do touchpad testing too. :)
-
I currently need more development workforce than testing. How about implementing the Touchpad keypad protocol from Goplat's spec (http://hackspire.unsads.com/wiki/index.php/Keypads)? :)
-
I currently need more development workforce than testing. How about implementing the Touchpad keypad protocol from Goplat's spec (http://hackspire.unsads.com/wiki/index.php/Keypads)? :)
I may give that a try tomorrow...(and probably fail epic at it :p)
but this line I can contribute now:
#define KEY_NSPIRE_FRAC KEYTPAD_(_KEY_DUMMY_ROW, _KEY_DUMMY_COL, 0x1A, 0x100)
that key is still missing in common.h, even though I doubt that somebody will use this one in near future
-
Thanks! Just commited to the trunk.
-
Well, I cant code really, but Im totally willing to risk my nspire for testing
-
I currently need more development workforce than testing. How about implementing the Touchpad keypad protocol from Goplat's spec (http://hackspire.unsads.com/wiki/index.php/Keypads)? :)
Did you want to implement the I2C code? It might be easier to just make syscalls for the OS functions for read/write. Quick example of usage: (for OS 2.0.1 non-CAS)
#include <os.h>
// returns 0 on failure, 1 on success
// addresses are for 2.0.1 non-CAS
#define touchpad_read ((int (*)(unsigned char start, unsigned char end, void *buf))0x10174A48)
#define touchpad_write ((int (*)(unsigned char start, unsigned char end, const void *buf))0x10174B38)
static inline void clearScreen() {
memset(SCREEN_BASE_ADDRESS, 0xFF, SCREEN_BYTES_SIZE);
}
static inline void setPixel(int x, int y, int color) {
unsigned char* p = (unsigned char*)(SCREEN_BASE_ADDRESS + ((x >> 1) + (y << 7) + (y << 5)));
*p = (x & 1) ? ((*p & 0xF0) | color) : ((*p & 0x0F) | (color << 4));
}
int main() {
int cpsr;
struct {
unsigned char width[2];
unsigned char height[2];
} size;
int width, height;
// be sure to turn interrupts off when accessing a different touchpad page
// TI's interrupt handler expects it to be set to page 4
asm ("mrs %0, cpsr" : "=r" (cpsr));
asm ("msr cpsr_c, %0" : : "r" (cpsr | 0xC0));
touchpad_write(0xFF, 0xFF, "\x10");
touchpad_read(0x04, 0x07, &size);
touchpad_write(0xFF, 0xFF, "\x04");
asm ("msr cpsr_c, %0" : : "r" (cpsr));
width = size.width[0] << 8 | size.width[1];
height = size.height[0] << 8 | size.height[1];
clearScreen();
while (*(int *)0x900E001C & 0x80) { // loop until ESC pressed
struct {
unsigned char contact;
unsigned char proximity;
unsigned char x[2];
unsigned char y[2];
} cur;
int x, y;
touchpad_read(0x00, 0x05, &cur);
if (cur.contact) {
x = cur.x[0] << 8 | cur.x[1];
y = cur.y[0] << 8 | cur.y[1];
x = x * 319 / width;
y = 239 - (y * 239 / height);
if (x >= 0 && y >= 0 && x < 320 && y < 240)
setPixel(x, y, 0);
}
}
return 0;
}
-
Great! I like it.
I suppose Ndless should both make available the current isKeyPressed() function to detect left/right/... and a new touchpad-specific scanning function. Touchpad-based games may be fun to play!
-
I really wish I had a touchpad. Manipulating the clickpad to play nDoom and a few other games can be annoying sometimes. X.x
-
Hey, ive just tested nDoom with a clickpad and a touchpad, the clickpad doesnt entirely work, it spazzes out on exit and the right arrow key doesnt function.
The touchpad works alright, I just hope you guys get the touchpad jeys mapped sooner or later. No rush though
-
On the clickpad, as I reported in the nDoom thread, the clickpad worked but the game froze when I shot and moved at the same time.
-
I suppose Ndless should both make available the current isKeyPressed() function to detect left/right/... and a new touchpad-specific scanning function. Touchpad-based games may be fun to play!
Indeed, I think that there should be a mode providing direct access to the touchpad.
In addition to this, perhaps left/right/up/down/click should be removed from the key macros used with isKeyPressed(), and pushed to a new way of checking those keys, which would make it easier to abstract Clickpad vs. Touchpad ?
-
I currently need more development workforce than testing. How about implementing the Touchpad keypad protocol from Goplat's spec (http://hackspire.unsads.com/wiki/index.php/Keypads)? :)
Did you want to implement the I2C code? It might be easier to just make syscalls for the OS functions for read/write. Quick example of usage: (for OS 2.0.1 non-CAS)
Ok, I now have both isKeyPressed() working with an emulated Touchpad, and a Touchpad API for x/y coordinates scanning.
But I should I detect a click?
[edit]Also I see that the OS doesn't call touchpad_read() until a key is pressed. Would there be a lighter way to just check if the Touchpad is currently touched (to update Ndless's any_key_pressed())?