Didj BootLoader Firmware Updating

From eLinux.org
Revision as of 00:24, 15 July 2011 by Jrspruitt (Talk | contribs) (OpenDidjConnect)

Jump to: navigation, search

This is a way to manually upgrade your firmware and bootloader.


Programs Needed

Terminal program: Hyperterminal or equivalent

Hardware Needed

Files Needed

  • DIDJ-0x000E0002-000001.lfp (bootloader)
  • DIDJ-0x000E0003-000001.lfp (firmware)

Update With Console Access

Using Built in Tools

This method will use a few built in programs that come with the Didj for updating the firmware and bootloader. You will need to copy, or create a folder, and certain files in it for this to work It is easiest to extract the folder from the lfp archives and modify it as needed.


For firmware this method will install into the opposite partitions, than the one you are on, so if you are on RFS0, the update will be installed to RFS1. And the Didj will be configured to boot from that one.

The firmware folder should be named firmware-LF_LF1000.

Mount your Didj and copy you're prepared folder to the /Didj/Base directory on your Didj.

After loading your folder onto the Didj, its best to run the check program, to make sure it can find it.

On Didj

# fwcheck

This should return the path to your folder, indicating it was found.

Now you can run the actual update program:

# fwupdate /Didj/Base/firmware-LF_LF1000/ > /dev/console
Found /Didj/Base/firmware-LF_LF1000/
Package Integrity Test Passed
Installing kernel.bin in Kernel1 (mtd5)
Kernel install successful.
Installing erootfs.jffs2 in Linux_RFS1 (mtd6)
Rootfs install successful.
Switching from RFS0 to RFS1


The folder must be prefixed with 'bootstrap-' (ex. bootstrap-LF1000).

The only files that are needed are:


Check that the updater can find your folder.

On Didj

# blcheck

Then run:

# blupdate /Didj/Base/boostrap-LF_LF1000 > /dev/console
Found /Didj/Base/bootstrap-LF_LF1000/
Package Integrity Test Passed
Installing lightning-boot.bin in LF1000_uniboot (mtd0)
Bootloader install successful.

Force Update with Custom SCSI Commands

This update can be done with out a console connection, and mimics how LFConnect handles the task. Both updates can be done at the same time. This is exactly like With Built in Tools except we trigger the Didj to run those commands for us, by giving our package a higher version number. This is nice if you do not have console access to the device.

Check out SCSI Commands for how to use SCSI Commands.

If you want to do both at the same time, load both folders into /Didj/Base then run the command to eject.


For bootloader create a folder in /Didj/Base called prefixed with 'bootstrap-' (ex. bootstrap-LF_LF1000)

It should have the same files as the lfp package.

Make sure meta.inf has a version number higher than Version="" or if you've changed the version number in your file system, higher than that one.


For the firmware create a folder in /Didj/Base called firmware-LF_LF1000

It should have the same files as in LFP package DIDJ-0x000E0003-000001

Make sure meta.inf has a version number higher than Version="" or if you've changed the version number in your file system, higher than that one.

Trigger Update

Then run the SCSI Command C6 "Disconnect Ok", which will cause it to say its "Learning New Tricks" before saying its okay to disconnect your Didj.

Then turn the Didj off.

This processes causes the Didj state machine to look for a folder called firmware-LF_LF1000, if its a newer version, which is found in meta.inf and compared to /etc/version on the Didj, it will update the files with the new ones.

OpenDidjConnect This is a program that does the SCSI Commands for you. You just need to give it the action desired, and the drive letter (Windows) or device (Linux).

OpenDidjConnect Latest Version and installation.

Mount your Didj and Assign it a Driver Letter

Prepare your firmware or bootloader folder, just like the SCSI Commands section. But instead of running those commands, use OpenDidjConnect instead.

On Host

$ OpenDidjConnect -d <drive_letter> -c eject


It is possible to cause a major malfunction with your Didj by replacing these files. Familiarize yourself with the procedure using known-good packages first.

You should also be familiar with Didj UART Boot before using these procedures. The UART boot allows non-destructive testing of bootloaders and firmware/kernels; it also provides a recovery method in case a new bootloader or firmware/kernel written to the NAND fails.

When using SCSI commands, check that you are using the correct syntax and that you are sending them to the correct device.