Hi Manjunathan K,
I'm not aware that anyone has made videos - and most everything we do like that would be based on HalCoGen.
But you can and should start with HalCoGen IMO. It provides a framework to boot the device and load your own custom
program into the HET with only a few clicks:
Above is the picture from HalCoGen's HET Tab. If you check the "Enable Advanced Config Mode" checkbox, and browse to the .H and .C file that are OUTPUT by the HET IDE - from your custom HET program - then when you call hetInit() your own program will be loaded into HET and started.
So I'd say start w. the HET IDE. It has a 'code pallette' with basic PWM functions. You can simulate on the HET IDE, and if you upgrade Synapticad you can even provide stimulus that you simply 'draw' in the waveformer and feed to the HET simulation. Or you can use Synapticad to get stimulus from a piece of test equipment like a logic analyzer or scope and feed this to the HET model. (Or you can enter stimulus by hand... harder this way but ok for simple tasks)
When you are happy in the HET IDE, which includes the HET assembler - you can move to HalCoGen to test your program on real silicon.
FYI HET IDE includes HET assembler, HET assembler takes .het (HET assembly) and outputs -> .h, .c files. The .h and .c files that it outputs are for your ARM code / application. The HET program is turned into a C structure which is copied to HET RAM during hetInit(), and a data structure is created so you can access locations in your het program symbolically. You need this because when you want to set a PWM frequency for example you do this by writing to the data field of some instruction in HET RAM. If you put a label on that line of HET code in the HET assembler, then the .h that is created will allow you to refer to that line symbolically - so even if you add/remove instructions and the address of the instruction moves during development - the driver code you write on the ARM will stay in sync (as long as you rebuild the ARM code using the latest .h file).
