So, JavaLoader & Barry progress...
I have just posted a new patch : http://www.progweb.com/modules/blackberry/bjavaloader/ This patch is import : - fopen / fclose functions are removed from the barry library. (bjavaloader tool read the file) - add new doc file about COD format - add structure definitions in src/cod.h To send an Java application, I need to understand the COD format. That's why I have added the doc file. Now, I think that the barry library (about JavaLoader) is OK and finished) => This part can commited. Of course, you can modify my code. Now, I work into the bjavaloader tool. bjavaloder has to read the COD file to determine the size of packets... (almost for big module) I notice that the rapc toolchain split a COD file in severals COD files with a size lower that 0x7F8 bytes. Each COD file has got an header. Regards, Le dimanche 11 janvier 2009 à 12:18 +0100, Nicolas a écrit : > So, > > It isn't very easy, but I think that I'm going to reach the aim ! > > I need to reverse the format of COD file... > > Regards, > > Le samedi 10 janvier 2009 à 16:59 +0100, Nicolas a écrit : > > Hi, > > > > Now, I have understood how send big java code... > > > > Packets sent : > > > > Init : > > 04 00 08 00 64 00 00 00 > > 04 00 08 00 70 00 01 00 > > 04 00 05 00 00 > > > > for (k=0;;k++) { // Application size = k * 0xMMLL > > 04 00 08 00 67 01 04 00 > > 04 00 08 00 00 00 MM LL > > > > for (n=0;;n++) { // 0xMMLL = n * 0xmmll > > 04 00 08 00 68 00 mm ll > > 04 00 fc 07 de c0 ff ff 00 00 ... > > } > > } > > > > For each 'k' value, MMLL can change. Sample : > > 0xCE30 > > 0xB334 > > 0x9C88 > > 0xB204 > > 0xBF54 > > > > http://www.progweb.com/modules/blackberry/traces/ > > > > Traces for big application : > > javaloader-metro.log > > > > Regards, > > > > > > Le samedi 10 janvier 2009 à 05:52 -0500, Rick Scott a écrit : > > > I have added the JavaLoader protocol to the kernel module. It > > > multiplexes/demultiplexes the protocol into /dev/bbloader[0-9]. The > > > protocol amounts to 2 bytes, to indicate how many bytes follow, followed > > > by that many bytes. It can be used at the same time as the desktop and > > > modem. I have also added a javaloader program that uses it. So far it > > > retrieves the device info, maybe more by the time you see this :) > > > > > > Interestingly the device info includes what they call a Hardware Id. > > > This same number seems to appear in the blob that we get the ascii > > > device description from. This will probably be a good way to determine > > > device capabilities. > > > > > > Anyway, off to write some more javaloader stuff .... > > > > > > ------------------------------------------------------------------------------ > > > Check out the new SourceForge.net Marketplace. > > > It is the best place to buy or sell services for > > > just about anything Open Source. > > > http://p.sf.net/sfu/Xq1LFB > > > _______________________________________________ > > > Barry-devel mailing list > > > Barry-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/barry-devel -- Nicolas VIVIEN ------------------------------------------------------------------------------ Check out the new SourceForge.net Marketplace. It is the best place to buy or sell services for just about anything Open Source. http://p.sf.net/sfu/Xq1LFB _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
