Touchpad Touchstone Dismantled
Visuals of Inside a HP Touchpad Touchstone
Visuals of Inside a HP Touchpad Touchstone
So it seems the touchpad is quite a powerful little device under to hood, a few kernel changes, config changes to pulseaudio and USB audio support is added, better sound out of the touchpad than the headphone port.
To get this working it required an OTG micro USB cable, powered USB hub that feeds power back to the source usb plug, and some form of usb HID sound device, pretty much any usb sound card that uses the line “No Drivers Required” with the support of MacOS is a dead giveaway this is what it is, i came across this http://www.TurtleBeach.com/products/sound-cards/audio-advantage-micro-ii.aspx USB with optical output on the cheap, waiting for it to arrive to see how well this device works.
With the help of @therealsconix and his PulseAudio Settings App in Preware switching to usb audio after a bit of testing became simple
last thing that is left is getting the USB audio support included in the Kernels in Preware, until this time if you want my uberkernel with this working let me know
New workspace is so exciting, enclosed long single car garage is much better than a car port, now onto that list of work the mightyboy needs, damn it’s a big list, oh well, motorvation is needed to go spend endless hours out in the cold garage in the middle of winter.
Sandblasting of the engine bay and removal of the subframe next on the list, free time where are you..
Problem: The Boot timeout (in the redboot boot loader) is too short to successfully flash the devices with a non Ubiquiti Firmware. So before you can flash a new firmware we need to increase the timeout.
Ingredients: You are going to need the following files in a folder of your choosing
· putty.exe – download from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
· open-mesh-flash.exe – downloaded from http://open-mesh.com/
· breakin.bat and redboot.txt – grab the text below, Note – copy everything BETWEEN the denoting lines, but NOT the denoting lines themselves
— breakin.bat —
echo off
:start
rem ————————————————
ping 192.168.1.20 -n 1 -w 1 > NULL
echo .
IF ERRORLEVEL 1 goto start
rem ————————————————
break
putty.exe telnet://192.168.1.20:9000 -m redboot.txt
— end —
— redboot.txt —
^C
— end —
Method: The idea behind the script is that it will ping the PicoStation2 until it responds and then it launches a telnet session with putty and sends the Control+C command to stop the boot process and give you a terminal.
With that in mind, fire up a command prompt on your windows machine and start running the breakin.bat script.
Once the script is running, plug your PicoStation2 into the network. It should only take a few seconds for the script to break into the boot process. If after 20 seconds you do not have a putty telnet session window open, unplug the device, wait for 20 seconds and try again.
Now that you have a putty telnet session open, you should see similar to the following:
== Executing boot script in 0.090 seconds – enter ^C to abort
^C
RedBoot>
Now that you have a command prompt, you need to run the fconfig command and change the settings. Note: To delete a character, use Control+H (^H) – It does not delete the character on screen, but it does delete the character! Note: Use the enter key to get to the next line (setting)
Here is a screen dump of me changing the config on one of the devices
== Executing boot script in 0.090 seconds – enter ^C to abort
^C
RedBoot> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
Enter script, terminate with empty line
>>
Boot script timeout (1000ms resolution): 1^H2
Use BOOTP for network configuration: false
Gateway IP address:
Local IP address: 192.168.1.20
Local IP address mask: 255.255.255.0
Default server IP address:
Console baud rate: 9600
GDB connection port: 9000
Force console for special debug messages: false
Network debug at boot time: false
Update RedBoot non-volatile configuration – continue (y/n)? y
… Erase from 0xa87e0000-0xa87f0000: .
… Program from 0x80ff0000-0×81000000 at 0xa87e0000: .
RedBoot> reset
So now you have a PicoStation2 with a two second boot timeout it is time to flash it. Use the following steps to get your device flashed. 1. Determine the interface your device it attached to (run the open-mesh-flash.exe without parameters to see a list)
2. Run the open-mesh-flash.exe specifying your interface
3. Plug your PicoStation2 in
4. Watch the magic happen!
Full instructions can be found at this URL http://support.open-mesh.com/activekb/questions.php?questionid=24
Run Breakin.bat
== Executing boot script in 0.090 seconds – enter ^C to abort
^C
RedBoot> fconfig
Run script at boot: true
Boot script:
.. fis load -l vmlinux.bin.l7
.. exec
== Executing boot script in 0.090 seconds – enter ^C to abort
^C
RedBoot> fconfig
Run script at boot: true
Boot script:
..
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xA8000000 0xA8000000 0×00030000 0×00000000
linux 0xA8030000 0×80041000 0×00660000 0×80041000
FIS directory 0xA87E0000 0xA87E0000 0x0000F000 0×00000000
RedBoot config 0xA87EF000 0xA87EF000 0×00001000 0×00000000
RedBoot> fis init
About to initialize [format] FLASH image system – continue (y/n)? y
*** Initialize FLASH Image System
… Erase from 0xa87e0000-0xa87f0000: .
… Program from 0x80ff0000-0×81000000 at 0xa87e0000: .
RedBoot> fis list
Name FLASH addr Mem addr Length Entry point
RedBoot 0xA8000000 0xA8000000 0×00030000 0×00000000
FIS directory 0xA87E0000 0xA87E0000 0x0000F000 0×00000000
RedBoot config 0xA87EF000 0xA87EF000 0×00001000 0×00000000
RedBoot>
Attempt a reflash with openmesh
added more sheets of dynamat, into the doors, on the rear wall of the cabin and along the inside of the outer sheet of the rear of the ute
So the Mightyboy got attacked with a Bulk Pack of Dynamat
there was nothing left of the Bulk Pack and this is what it covered
Todays update added a black coat to the Engine Bay after way too much wet sanding to get a smooth finish.