Monday, March 17, 2008
a) get uboot build to work from SRAM with basic uart support, probably usb later on if i can port the gadget driver from linux kernel.
b) configure clocks and get SDRAM up and running.
c) attempt kernel bootup - now, this i expect to be a pain...
d) support nand
e) support nor, and get support for SDP (low in personal priority currently - but should be a no-brainer hopefully).
Schedule is going to go thru one file a day(or atleast a week depending on my "office work" load)..
Today is going to be start.s lets see if we can get a concensus or flame war on the list.. this is critical as most boards share the same code.. as long as it is V4 ISA, things should be fine.. I would not dream of thumb in this peice of code.. by the way, Sascha Hauer is the custodian for uboot-v2 as I was told on the uboot irc.
Sunday, March 16, 2008
1) “Hacking” to get the vendor id and product id:
I dont own a Catc or a usb monitor.. so just plugged in the board to my laptop and dumped the syslog ;)
$ cat /var/log/syslog
Mar 16 15:26:23 coyote NetworkManager:
Voila!! 3430 is nothin but,
VendorId = 0x0451
DeviceID = 0xD009
2) Trigger an external program to download image:
Would you believe it, last time i was working in the kernel, hotplug was still working.. it seems that greg and others made hotplug obsolete! damn.. i have been out of kernel development for too long.. :(.
Anyways, I will need to create a scenario where on connection, the device will need to trigger some mechanism to initiate the downloads. I need to give some image fast as I see the following(putting couple of info points at probe and disconnect):
Mar 16 15:26:23 coyote kernel: [161173.293707] /home/nmenon/Src/Omap-Linux-Per/omap_peripheral.c: probe
Mar 16 15:26:23 coyote kernel: [161173.593413] usb 5-3: USB disconnect, address 15
Mar 16 15:26:23 coyote kernel: [161173.593534] /home/nmenon/Src/Omap-Linux-Per/omap_peripheral.c: discon
that is around 300ms to do everything and get out.. else we will get chopped in b/w. :(.
Looking at the same thru udevmonitor:
udevmonitor: throws out the messages that the system feels when I plug in/disconnect a device
udevmonitor will print the received events for the device connection and disconnect events:
nmenon@coyote:/etc/udev/rules.d$ sudo udevmonitor --env
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent
UEVENT[1205699933.731375] add /devices/pci0000:00/0000:00:1a.7/usb5/5-3 (usb)
in short, the technique in the code link given above is based on the following:
install a driver which will provide read/write and usbdevfs entries,
use udev rules to detect a plug in event, and route the message accross to a second script
the second script will check for a config file and get the second file name from it, send the same to a perl script which will break it down to usb sized writes to the driver's fop write function.. bingo.. our image is going straight to SRAM.. (depends on the load address which i hacked into the perl script.. u can modify the same if you like)...
Not a tooo convinent a method + not portable to Windows, but has anyone considered libUSB ?
that might be interesting to try some day...
Sunday, March 09, 2008
http://www.reuters.com/news/video?videoId=77483&videoChannel=6 - a lifeOS+ the sensory network..
The real one: Morph from Nokia and Manchester univ.: http://www.reuters.com/news/video?videoId=77681&videoChannel=6
Some thing to moot on -> nano tech and capabilities that it brings in.. wearable computing, technology more integrated with humans.. sounds like science fiction.. but a bit of Google later on specific tech.. we might be surprisingly closer than expected...