Nishanth' tech rambles

One neat little trick of having an OTG port is the capability to have the board act as any type of device you'd want it to be.. in my case, I wanted to emulate a disk drive for the heck of it.. I found this link particularly useful. g_file_storage.ko which is generated once you enable file storage gadget as a module in the kernel build. Step 1: create the "disk" - essentially a file dd bs=1M count=64 if=/dev/zero of=fs fdisk fs (follow the steps in the link) fdisk -lu fs sudo losetup -o 4096 /dev/loop0 fs sudo mkdosfs /dev/loop0 mkdir r sudo mount -t vfat /dev/loop0 r vim r/hellow.txt (put what ever files we want here) sudo umount r sudo losetup -d /dev/loop0 ensure that fs file exists in the filesystem of the target Step 2: load it up.. insmod g_file_storage.ko file=./fs stall=n where fs is the file which we created in the first place.. and that'z it.. once you connect the musb to a windows PC, it appears as a disk ;)...

NOTE: This is a work in progress yet.. Get Code base: x-loader: git clone git://www.sakoman.net/git/x-load-omap3.git u-boot-v1 - omap3: git clone git://www.sakoman.net/git/u-boot-omap3.git cd u-boot-omap3 git checkout --track -b omap3-dev origin/omap3-dev Updated: see here if this did not work.. u-boot-v2: git clone git://git.denx.de/u-boot-v2.git omap-uboot-utils: git clone git://github.com/nmenon/omap-u-boot-utils.git signGP tool: wget http://beagleboard.googlecode.com/files/signGP.c Compilers: Cross compiler: arm-none-eabi-gcc: 2007q3-53 (4.2.1) Host compiler: x64bit: (Ubuntu 4.3.2-1ubuntu11) Build commands: Before starting the build process, lets set up a simple alias command: alias mymake='make ARCH=arm CROSS_COMPILE=arm-none-eabi- V=1' U-boot-arm: mymake omap3_beagle_config mymake U-Boot-v2: mymake omap3530_beagle_per_uart_defconfig mymake X-Loader: mymake omap3530beagle_config mymake [Update: 2008-12-13 - I completely forgot that we need to sign an image for it to boot ...

The following is thanks to Dirk Behme (based on ubuntu 8.10): Install packages: On Ubuntu, I have done: sudo apt-get install git git-email Stage1: development: set up your GIT variables(probably in ~/.bashrc) export GIT_COMMITTER_EMAIL=yourEmail@somewhere.com export GIT_COMMITTER_NAME='YourName' export GIT_AUTHOR_EMAIL=yourEmail@somewhere.com export GIT_AUTHOR_NAME='YourName' git clone ... or git pull.. etc to get to the latest code. git branch branch_name git checkout branch_name Do changes git commit with commit message in incremental stages.. Stage 2: Generate email-able patch files. git-format-patch -s -n -o origin.. -s will generate the signed of-by -n will generate numbered patches (if you have just a single patch, you can ignore it) - but if you have multiple ones, this is a good idea to use to generate subject auto numbered 1/2, 2/2 etc.. -o is where the output patch files will be stored -> each commit is a separate file. Stage3: Email the patches:(for gmai...

It has been a long time desire to use usb2serial convertors for pserial application. :(.. Anyways, yesterday night, I looped back my usb2serial back to my PCI serial port and tried to write a bit of loopback code.. to figure out the issue with pserial, I wrote a simple little app to print the ttySx flags: #include <sys/types.h> #include <sys/stat.h> #include <fcntl.h> #include <termios.h> #include <stdio.h> #include <string.h> #include <unistd.h> #include <errno.h> /************* VARS ***************/ static int fd; static struct termios oldtio; int main(int argc,char * argv[]) { int ret; int i; if (argc!=2){ printf ( "error no args..%d\n" ,argc); return 1; } printf ( "port: %s\n" ,argv[1]); fd = open(argv[1], O_RDWR | O_NOCTTY); if (!fd) { printf( "terminal is not open!\n" ); return 1; } /* sa...