Hi Brian, You wrote: > > LCP class. If Roger is game it looks like there are Java things in the > list > he could take on. Maybe Juan? (Eclipse plugin) >
Is Juan Antonio on this developers list? >> What would you like me to work on next? Apart from fixing bugs and making >> things more robust, I am thinking of working on 6 and 7. > > Yes, I think a persistant text menu that allows you to upload to it and > delete files would be the most important thing to aim for at the moment. > (If > the menu can delete files, do you still need an explorer interface on the > PC?) Currently I have not got delete on the menu, as I was following Roger's suggestion of a while back and just executing programs from the menu. He suggested other file management was better done from the PC. If I do put delete on the menu, then the easiest way is program to have a top level menu with Delete files, and Execute files as options. Selecting a file first and then displaying a small menu with Execute Program, Delete File is possible. What do you think is best? > Making it understandable to users how to upload the menu - are we going > to treat this as part of firmware? Maybe a batch file that gets the > "firmware" (menu etc...) on the brick. > I mentioned this in a previous email. Currently it is built into the firmware in a C header file - java_binary.h. There is a tool that creates this from a .bin file. You then have to rebuild the VM with GNU ARM tools. I could keep the menu separate in its own area of flash memory, so that it could be updated independently of the VM. fwflash could then flash either the VM, the menu or both. We would need to allocate a fixed flash area to the menu - say 16kb. Do you prefer this? It makes developing the menu independently of the VM simpler, and makes it easier to support different menus. > One thing I'm wondering about is, does the Official LEGO firmware reside > in > Flash memory or in the 64 kb RAM area? If not 64 kb area, what do they use > that for then? It would be nice to use that area for what ammounts to our > firmware (menu system, LCP, etc...) but I assume it isn't persistant > memory. > Like our flash version, it resides in flash, but when it starts it creates dynamic data in RAM. I don't think Lego published their build files, so its hard to see how much they put into RAM. With the gnu loader you can create a steering file that says exactly which code and data is put into RAM. Currently our flash version has nearly all code executed from flash memory, and just the flash routines copied into RAM. When the Lego firmware executes a user program, I think it executes the "code" from flash but again creates data areas in RAM. We currentkly copy the whole Java binary into RAM. I am having a lot of problems with the flash version of lejos at the moment, which I am trying to get Charles to help with. (He is willing, but busy). To make the menu persistent in the sense I think you mean, we need the flash version to work reliably. >> Do you have any thoughts on how to use iCommand for this sort of thing. >> Should we include the iCommand jar file and the third party jar files and >> dlls with lejos NXJ. We have this issue for both the file explorer and >> command line utilities. > > If we can help it, let's not go there yet. iCommand has issues with using > RXTX and other third party COMM programs that I don't want to get into > now. > We'll need to research options so users don't have to download other > classes > to make leJOS work. And I really don't want to get into USB support for > iCommand for the next release. Our priority should be to get the > persistant > menu system, consolidate those changes and do a release. > It would be nice for users to have some way to upload programs over Bluetooth. Are you suggesting that we have a nxjupload utility that just works over USB, not Bluetooth? Lawrie ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Lejos-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lejos-discussion
