propeller-load.cfg entries for ASC

Martin Hodge

Did I get all the important options? Is TV_DEBUG a future feature?

[asc]
    clkfreq: 80000000
    clkmode: XTAL1+PLL16X
    baudrate: 115200
    rxpin: 31
    txpin: 30
    tvpin: 16   # only used if TV_DEBUG is defined

[ascp]
    clkfreq: 80000000
    clkmode: XTAL1+PLL16X
    baudrate: 115200
    rxpin: 31
    txpin: 30
    tvpin: 16   # only used if TV_DEBUG is defined
    cache-driver: eeprom_cache.dat
    cache-size: 8K
    cache-param1: 0
    cache-param2: 0

jazzed

Martin Hodge wrote: »

Did I get all the important options? Is TV_DEBUG a future feature?

Hi Martin.
Yes and No. The option names are correct. TV_DEBUG is not a future feature.

Form more information, please see: http://code.google.com/p/propgcc/wiki/PropGccLoader

TV_DEBUG is only for the loader. You can rebuild the loader if you like with -DTV_DEBUG. Then when the loader starts you will see what it's doing on the TV.

The file propeller-load.cfg only defines how to load/boot a given board. This approach makes the loader easier to maintain, and leaves device definition for the user program. Within the user program, you can insert any device you like. There are hooks for library devices.

The file propgcc/demos/TV/TvText_demo/TvDemo.c shows an example of using both a serial port and TV.

Really, you don't need to define ASP entries, but you can if you like. Without TV_DEBUG the entries you made are identical to HUB and EEPROM.

Thanks,
--Steve