Example when creating a volume the the field looses focus and whatever I type doesn’t show up unless I type one letter maybe two at a time then re-click on the text box to gain focus, and of course if I forget to click again or hit the right arrow first it over writes what I already typed….SO did you decide to write your own dashboard and if so who do I have to to get a copy?ģ) I have a second DBP that was non-functional when I bought it I’m going to try the dual serial connection fix I read somewhere to try and get it working again. so what help am I looking for…Ģ) I have stupid problems with the dashboard.
I would like to convert my DroboPro (DBP) to DroboFS (I Think) I’m a hardware guy I think my dyslexia (not joking) makes programing more difficult.  I was just lucky enough to have another one to examine to get the config back 🙂  I think I need to see if I can find a way to reload the firmware again as it appears I may have damaged something else as it is still not showing up quite right in the Drobo dashboard, but at least it is back to running the file server and so on 🙂 Posted by daniel NovemPosted in Hardware, Reverse Engeneering Tags: drobo, DroboPro, firmware, hacking Post navigation  Don’t make the same mistake I made as it will frag all of the custom set up and leave you with a boat anchor. The thing I did wrong was try out another of the custom commands tdsetup.  Using the saveenv command is not enough however, it is necessary to call another custom command updateFlashToken to have the vxWorks side of things take notice of the new value.
#Old versions of drobo dashboard serial number
 It is then possible to track down the variable containing the serial number and change it to the desired value.  This shows all the environment variables. So, how do I go about changing the serial number reported by the firmware?  After a bit of messing around in the uBoot environment I discovered the printenv command.  It turns out the device type is the 5th from last digit, so if your serial number is TDBxxx7xxxx you have a Drobo FS for example.  It definitely uses the serial number reported by the Drobo to determine the type unit it is talking to. I also figured out what is up with the Drobo dashboard app.  After doing this the vxWorks side started working again 🙂  From there I was able to read the Drobo FS uBoot config and use that to guess what the values needed to be for the DroboPro.  I was able to disassemble that (I didn’t even break the waranty void sticker) and gain access to the serial ports on the main board.
 Fortunately I have another Drobo, in this case a Drobo FS. I’ve been playing around with my old DroboPro and in the process managed to frag the uBoot config rendering the unit basically useless as the vxWorks side didn’t boot the special disk applications required for correction function.
0 kommentar(er)
