Friday, November 15, 2013

Windows USB drivers for Galaxy Note 2 SGH-T889 phone

Drivers from samsung for my Note 2 phone

Hopefully will allow ADB connect up from development laptop.

raspberry pi jtag

This example is for using an raspberry pi as a run control, not for using jtag ON the raspberry pi.  An example below is for debugging arm devices.

TJTAG part copied here for reference.

UPDATE: TJTAG with RPi support is now available and it’s preferred to this version.
The updated README should have all the information you need to build this on Pi and let it help save your day. But if you’re lazy like me, here’s a quick guide:
  1. Connect the boards as per the wiring diagram above.
  2. Power up your router.
  3. On your Pi:
    $ cd ~
    $ git clone
    $ cd hairydairymaid-wrt54g-pi
    $ CFLAGS='-D RASPPI' make
    $ ./wrt54g -probeonly
    If it gets stuck, try adding /noemw option.
There are many guides elsewhere describing how to use this tool to restore your router to an operational state. For more just google for it. There is a document that comes with this program as well (not written by me)—be sure to read it before doing anything.

Lauterbach spec for arm jtag interface.

Here is a link to an example ARM debug port spec. 

More examples (not for this rpi example, but for standalone jtag)

For JTAG dongle look simple Wiggler:

and free OCD Commander (Windows and Linux)
Free GNU Toolkits for OCDemonTM BDM/JTAG Devices


Embest Online Flash Programmer 2190K

Embest Online Flash Programmer user guide 430K

Wednesday, November 13, 2013


javascript virtual linux notes for jor1k emulator.

requires vde2, virtual distributed ethernet package.

this requires libtool, libpcap-dev, libssl-dev to make.   make it on machine hosting the jork emulator.

This supports an ethernet adapter on the jor1k platform.

Websockets (mentioned in network, tornado)

Tuesday, November 12, 2013

Getting wireshark going on Snow Leopard

 tep 1
Download Wireshark from here. Mount the .dmg file.
Step 2
Drag the Wireshark application icon to the handy dandy Applications alias the fine developers at Wireshark provided for you in that disk image. Then, open up the Utilities folder in the disk image, and drag the ChmodBPF folder into the StartupItems alias sitting below it. After that, open up a new finder window and navigate to /usr/local/bin. Open up the Command Line folder in the disk image (under /Utilities) and drag those contents over to /usr/local/bin. You’ll probably have to authenticate at that point, so do so.
Step 3
Open up a terminal window and type in the following commands:
cd /Library/StartupItems
sudo chown -R root:wheel ChmodBPF

You’ll probably be asked to enter an su password. Do so. Then exit terminal.
Step 4
Go to Applications and click on Wireshark. When the application opens you’ll probably see a another window open up along with it containing a bunch of errors. Close that window. Next, select Edit then Preferences from the Wireshark application window. Select Name Resolution, and click the Edit button next to “SMI (MIB and PIB paths”. Click the new button, and enter /usr/share/snmp/mibs/ in the little Directory Path popup window. Click Apply, and then Close.
Step 5
Exit Wireshark and reboot.
All should be well in network protocol analyzer-ville.
Editor’s note: special thanks to Nick Kleinschmidt and Dan Hale for helping out here.
UPDATE: Please note that these instructions applied to Wireshark Version 1.2.2 (SVN Rev 29910), and several comments have suggested that newer versions of Wireshark may no longer support libSMI. For this issue I can only suggest checking the Wireshark user guide and/or the wiki.

running multiple instances of Yawcam

running multiple instances of Yawcam

 by malun » Sat Jan 02, 2010 12:17 am
Yes, you are right, didn't think of that. Yawcam uses the settings located in the home directory for the user running Yawcam. There is however a workaround...

1) Install the first yawcam instance as usual and run it like usual.
2) Make a copy of the yawcam program directory (typically: C:\Program Files\Yawcam) and name the copy Yawcam2. You will now have two program directories for Yawcam:
C:\Program Files\Yawcam
C:\Program Files\Yawcam2
3) Create a new directory c:\yawcamsettings
4) Create a new directory c:\yawcamsettings\yawcam2

Now it's time to edit two files in here:
C:\Program Files\Yawcam2
If you are using windows xp or 2000 you can edit the files with notepad as usual, so jump to step 8 below.
If you are using windows vista or 7 you have to run the editor as an administrator, so continue at step 5.

5) Click on the windows start button and type "notepad" in the search field.
6) In the result list, right click on Notepad and choose "Run as administrator"
7) Now open the file in Notepad by clicking "File -> Open..." and browse to the file.

8) Edit the file C:\Program Files\Yawcam2\service_profile.cfg to contain one line like this:
9) Edit the file C:\Program Files\Yawcam2\launcher.cfg
Add the word service on the last line. If it's correct the last line will end with: yawcam.Main service

10) Start the second instance of Yawcam by running:
C:\Program Files\Yawcam2\Yawcam.exe
This version will now use settings located here:
Browse to this path and see that the .yawcam directry has been created.
11) You now want to create a text file disablerunningcheck.txt here:
to get rid of the question when starting the second instance of Yawcam.

I hope the explanation was clear enough...


Wednesday, November 6, 2013

Raspberry Pi running Ipfire notes

The ipfire firewall is built on a linux system running as a router and firewall, similar to ipcop.  Ipfire is a fork of the ipcop firewall.

history is here

Installing ipfire for use on the raspberry pi is covered elsewhere, this covers notes relative to bringing up the firewall options that are useful on ipcop on ipfire.

port change 444 to other.

On ipcop you use setreservedports to change 445 to another.

On ipfire you have to edit two files in the apache config, and restart apache:

ipfire listens by default on port 81 (non ssl ) and 444 (ssl).   the ports are listed in

/etc/httpd/conf/listen.conf  Edit them as needed and save.

The server hosts are defined in


the ssl one has the definition for 444 (default) and the other defines 81.  Both listen and these file have to be changed.

set up ipfire box as an openvpn client (use the ipfire pi as a field hot spot router, for example)

quoting entry:

I'm currently struggeling to get my IPFire server working as OpenVPN client. The machine is set up inside a rather closed-down network and I would like to connect to an external server using OpenVPN.

However, all the help I can find either helps one configure the IPFire machine as an OpenVPN server or the help for a client configuration is rather limited.

Can anyone please help me out (or point me in the right direction) to get my IPFire machine working as an OpenVPN client?

Thanks in advance.

SOLVED: After running openvpn with the created configuration file:
/usr/bin/openvpn --config /var/ipfire/ovpn/client.ovpn
it created the network "tun0"

All I needed to do after that (I have a network) is:
iptables -t nat -A POSTROUTING -s -o tun0 -j MASQUERADE

to make sure all the traffic on my network (starting with a 10.13 IP address) goes through the tun0 interface

Friday, November 1, 2013

Bad google (Setting up Gregarius online RSS aggregator to replace iGoogle)

I used iGoogle for reading a variety of page feeds, otherwise know as RSS feeds and now it is gone.  I didn't use the other features, which resemble apps on Android, or plugins  in  Chrome.  I don't think they realized how useful the rss aggregation was when they obsoleted it.  

I could go to this page from any device and have my own sites all summarized with one liner entries, which was updated with refreshes.  The Google backend handled all the rss reading and formatting, not my local device, so the only heavy lifting required by the device was when I clicked thru to a page to read it.

I found this aggregator and struggled to get it set up on linux, there were a couple of vague references I had to do a bit of experimenting with to get going.

the setup I elected is to run it on a LAMP (Linux, Apache, MySql, PHP) server.  It can be run with apache and php standalone on a local device.

it lacks individual user support near as I can tell, so you get a single list of pages batched up from this server.  At least I have a central place for my pasteup and i can export the web page from my local system to any of my devices.

These are notes on how to set up the system filling in the gaps I found in the instructions.  I have found a couple of nice pages explaining the setup, but they suffered in assuming I knew what they were talking about in setting up the database and a few other details.

Gregarius is a bit of a puzzle to set up.  It can be downloaded here gregarius

there are some assumptions which for some are maybe simple for some, but baffled me a bit.

here is a tutorial for setting up the thing


not obvious is the database creation.

I used mysql, and the setups were pretty plain for that.  However they asked for username and password in the install script, and also for admin password.

The install can be run via a gui or you can create a database init yourself manually.  If you are running by gui a file with the dbinnit  is created for download to your apache server.  Once you have that, and install it in the rss file you can create the sql with another script, install.php

Turns out the admin password and account asked for in the gui are for the mysql so it can encode the mysql output with proper passwords for the setup it outputs. 

A script called schema.php has to then be run to output a sql configured for your database, account system and tables.  That file can then run and create the database and configure it.

another problem is some of the weblinks don't pass back to the rss pages on apache. 

Individual feeds when you access it w/o any apache work go thru to the target sites, but the "group" jumps which the aggregator creates result in a 404.  Searching for that.  Looks like it is pointed at /rss (my sublocation on apache) and the apache isn't redirecting.

This may be the fix for that (from link above)

After you've created some feeds and you attempt to view them (below), you may find that you are getting 404 errors. The most likely reason for this is that your server is not running the Apache mod-rewrite module, so the short url's Gregarius uses by default are not being accepted. Simply go to Admin/Config and change the rss.output.usemodrewrite setting (second from the bottom) to false (screenshot).