compilers

1.cross compilers , host x, target y -- executable x, object-file y
2.cross debugger, host x, target y --- executable x, interprets y

linux kgdb basic idea

1.enable kernel hacking serial option ,select serial hardware
2.change kernel boot parameters,kgdbwait
3.when kernel boots it waits
4.on host open cross debugger,open vmlinuz from the kernel source root,set source path connect
5.to test if working set a well know system entry break point
6.press continue
7.it should hit the breakpoint
8.system.map is not necessary on target, it is used to resolve symbols in case of crashes on the kernel

arm board(beagle clones) - how to see it

1. has both wince and linux support
2. has 2 boot options .. from nand and mmc/sd
3. mmc/sd serves the purpose of floppy on desktop
4. with a bareskeleton nand , mmc booting can be used to flash other components to it
5. with a zero nand content , special techniques of using serial null modem cable to set it up for
basic booting
6. binaries used for mmc/sd booting .. MLO,uboot,kernel,rfs .. for nand XLOADER,uboot,kernel rfs
7. another important component the environment variables .. they are stored on the nand
8. there is separate section for mmc/sd env and nand env .. inaddition on the nand there are some other basic data
9. rfs can be on nand or sd interchangebly
10.some useful system running over it wince,0xdroid,rowboat etc

code.google.com

1.use eclipse for easier usage
2.install svn,openssh,git-core,git-svn on ubuntu
3.precreate google project
4.add repository path in eclipse
https://prototest.googlecode.com/svn/trunk
5.goto team option in the elclipse project,click on share project
6.when asked for username and passwd goto
https://code.google.com/hosting/settings
7.select files and commit

c++, protocol

1.common class to keep reference count
2.common class to stackup or organize similar objects
3.common class that helps to minimize operations, and demux all operations through a single interface
4.contexts to define an operations ... the operation parameters will be symmetrical across but the context determines what is done

1.context contains src,sink and signature routine that is overloaded and takes a event pointer or void args
2.it moves the data in units , minimal transition in a system
3.All layers are contexts,has a default signature functions
4.a layer has a chain of contexts each having the signature function
5.when the source to signature function is null the signature function may be in a demux context

code.google.com

it has its own repository either svn or mercurial

to add code , local system needs svn or mercurial installed

git and mercurial are alike because they allow collaboration better

there is also a way in which your personal repository can be mirrored on code.google.com.so the
original remains with you and what you see on the web is a mirror.In addition it provides all the
flexibilities of the hosted site

c++ -- protocols

1.the protocol system boundries will have n number of static classes
2.these statics are meant to link the new calls to entry points and in way sync into c++
3.at entries event object that has a span across the layers have to be created
4.if there are 3 layers, the event thus created together with polymorphism ,a single pointer
has to be casted to get appropriate layer data structures
5.physical medium better to design half duplex objects

java abstract, interfaces

concept of abstract === nterface
both needs implementations in the included classes
interfaces can be extended independently