Projected Completion

Late January - Early February

Work Items

Please understand that the time projections are in man-days, not business days, so they will not translate directly into a calendar time period.

!!!! Code Downloader

Progress: 0% Projected Time: 2-3 days

This is the component of the IDE that allows new programs to be downloaded to the JwiK™ via a
serial connection. It will use a simple block transfer protocol. Currently, we are including the
customized class file in a header and compiling it for testing.

Remote Debugger

Progress: 70% Projected Time: 14-16days

This component will allow the user to remote run and stop the program as well as set breakpoints and inspect variables.
In the first release, a subset of these features will be available and will include run, stop, and a
window to print debug messages from the Java application. Subsequent releases will include
break points and variable inspection.

Update 1/20/2013 - the code downloader and the remote debugger tasks have been combined into one. A new specification document for this feature has been created and defines the debug features and how they will operate. In addition, all of the debug functionality will be released in the first released. Using the debugger, the developer will be able to load a new application, start and stop execution, set breakpoints, reset the VM, single step through code, examine object values, and examine the stack.

Hardware

Progress: 95% Projected Time: 2 days

Both the Brik and Jduino boards will require one more board turn to fix a couple of problems. Right now, there are some blue wires on the boards and the Jduino pinout is wrong and will not work with off-the-shelf Arduino shields.

OpenRF™

Progress: 90% Projected Time: 14 days

This is the item we are currently working on. It is the low power, FHSS radio protocol that makes JwiK™ so awesome. When complete, it will support point-point, point-to-multipoint, and multipoint to multipoint communications: pretty much anything you might require. It will be configurable and, with the right configuration and application, can achieve very long battery life. Apart from JwiK™, this is being used in other projects, including contract projects we are working on for other customers. Therefore, it is a top priority work item for us right now.

--------------

Updates

This is where a chronological list of updates will be recorded. If you have any comments or questions, use the discussions tab.
-------------
2/3/2013 - I made a lot of progress on the debugger features this week. New applications can be downloaded from inside the IDE over USB/Serial. Applications are downloaded in 1024 byte pages and programmed into a special area in Flash one at a time.

The application can be started and stopped within the IDE as well.

Single stepping, breakpoints, and variable inspection are all that are left and the debugger will be complete. In the interest of getting this out, I am going to pause the debugger work here and finish the remaining work items. In its current state, new programs can be developed, compiled, linked into a VMFILE, downloaded to the target and remotely started and stopped. That is sufficient for application development. Once the other feature sets are finished, I will come back to single stepping, break points, and variable inspection.

I have some pictures:


This is a picture of the JDuino™ board populated with a protoshield for testing. It shows connection to a SDR spectrum analyzer, logic analyzer, and USB debug adapter. The USB debug adapter is only needed for debugging the VM: it will not be needed to debug Java applications on production boards.

This picture shows the IDE in its current state. This is the plain vanilla IDE that is intended for cross platform use with Linux and Mono. The IDE is written in such a way that the GUI is separated from the IDE logic so that multiple IDE GUIs can be written for different platforms. A powerful Visual Studio like IDE based on WPF will be available at some point in the future.
-------------
1/20/2013 - While I have not knocked off a todo item completely in the last month, I have made a lot of progress. I have defined the debug support that JwiK" will offer and documented it; that document should make it on-line in the next week or so. Based on that design, I have upgrade the debug feature to include source level debugging such as breakpoints and single stepping in the initial release instead of subsequent releases. The code is about 75% complete on the embedded side and 50% on the IDE side. I think that this next week we will see a working debugger where we can upload applications over the serial port, start and stop execution, set breakpoints, and inspect object values and the stack.

The bulk of the work being done this last month has been on the OpenRF" wireless protocol stack. I am happy to say the code is essentially done; there is some debugging left but the core feature set is complete. This means that JwiK" devices can communicate with each other over the wireless link using FHSS and 100mW TX power for long range, all from within a Java application.

I will try to have some short demo videos up this week that shows off some of these features and pictures of the current hardware so you can get a feel for yourself where we are at. Thanks.
-------------
12/18/2012 - I apologize for the lack of updates for the last couple of months. We have been working and making progress and I thought we had communicated by e-mail with anyone interested in an update, but it was made clear to me today that we are evidently missing some people. In any event, I promised updates here and from now on there should be one every week or two as we make progress. Today, I have added a work items list to the top of this page to show what is left to be done and what our progress is on each item. You should be able to use that to track the project.

Our status today is that we have the hardware working, but the BriK and Jduino boards will both require a new board turn. The Java virtual machine is complete and working well. The OpenRF™ protocol is what we are working on diligently now. It is the item that has delayed our delivery: that and the increased project work load we have had over the last couple of months.

9/9/2012 - Good news today! We got our first run of PCB for the BriK and Jduino last Friday and built a couple up today. I am still not done testing everything out, so there is a lot of work left to do. Also, I got a lot done on the cross platform IDE; I should have the code updates up later today. I think we are on track to ship in late October or early November; all without Kickstarter. Thanks again to all of those who are supporting this project. Remember that you can pre-purchase boards and kits on our website to help us get this to the finish line.



9/2/2012 - Well, as you probably already know, we failed to make our funding goal on Kickstarter. No big deal though because we are going to continue the project anyways. In fact, we just ordered the first round of printed circuit boards for the BriK™ and JDuino™ boards. They should come in next week and we will start working with them. How fast this proceeds will depend on how much financial support we get. If you are interested in supporting the project, you can still do so by pre-purchasing boards and kits. We have a kit for every reward level available on our website at www.d6labs.com. Keep checking back to see how we are doing and feel free to ask questions via the discussion tab above. For those of you that have already pre-purchased, thank you.

8/27/2012 - I have established this page to be the primary location of updates in the event that the KickStarter project doesn't meet its funding goals. The project will continue and we will be pre-selling boards and kits in packages equivalent to each reward level on our website if KickStarter does not work out. - SJM

Last edited Feb 4, 2013 at 4:35 AM by stevetherfguy, version 13

Comments

No comments yet.