ferenczy @ home

S3CC410 single-chip CMOS microcontroller is designed for high-quality audio platform. It uses Samsung's newest 16-bit microcontroller, CalmRISC16 and 24-bit DSP engine, CalmMAC24.

The CalmRISC16 is a 16-bit low power RISC microcontroller. The CalmRISC's basic architecture follows Harvard style, that is, it has separate program memory and data memory (both up to 4 MB). Both instruction and data can be fetched simultaneously without causing a stall, using separate paths for memory access. It can operate up to 100 MHz alone or up to 80 MHz, when operating with a MAC24 coprocessor. The instruction set provides no instruction for writing to the program memory.

There exists the CalmRISC16 development environment from the AIJI System called CalmSHINE16.

Memory mapped I/O

original / mirror

OP decoding

original / mirror

• 2.0.13J [268 kB]
• 2.0.17 [268 kB]

• Linux, Cygwin on Windows or Mac OS X (I used Cygwin on Windows 2000, but Linux procedure should be same)
• download binutils (the assembler, linker and stuff), GCC (the GNU C Compiler) and optionaly gemoss (Gmini tools, emulator) sources from web or rather CVS (without password):
  
  binutils - download, mirrors, info
  GCC - download, mirrors, info

  cvs -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/gemoss login
  cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/gemoss co binutils-2.15
  cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/gemoss co gcc-3.4
  cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/gemoss co -P gemoss

• prepare directories, for example unpack (or copy from CVS) binutils into "~/binutils" and GCC into "~/gcc" (~ means user's home directory)

  ~> mkdir build
  ~> cd build
  ~/build> mkdir binutils
  ~/build> mkdir gcc
  

• choose installation location - directory for all files that will be created. I chose "/home/ferenczy/calmrisc", so replace it with your own path everywhere, you'll find it. You can also use "configure" without the prefix option, then files will be stored in a common location.
• build binutils. Note that there's currently a bug with the binutils (tex)info install for CalmRISC16. It can be safely skipped with "make -k install" (-k option skips errors).

  ~> cd build/binutils
  ~/build/binutils> ../../binutils/configure --target=calmrisc16-unknown-elf --prefix=/home/ferenczy/calmrisc
  ~/build/binutils> make
  ~/build/binutils> make -k install
  

• build GCC. It requires to set up newly built binutils into the PATH variable:

  ~> export PATH=/home/ferenczy/calmrisc/bin:$PATH
  ~> cd build/gcc
  ~/build/gcc> ../../gcc/configure --target=calmrisc16-unknown-elf --prefix=/home/ferenczy/calmrisc --enable-languages=c
  ~/build/gcc> make
  ~/build/gcc> make install
  

• Now you should have fully functional CalmRISC16 development toolchain on your system. Now, it's good time to build the Gmini tools. Just choose your prefix or left blank.

  ~> cd gemoss
  ~/gemoss> automake -a
  ~/gemoss> ./configure --prefix=/home/ferenczy/gmemu GMINIMODEL=mt-500 LOADADDRESS=10000
  ~/gemoss> make
  ~/gemoss> make install
  

  The GMINIMODEL and LOADADDRESS are completely irrelevant at the moment. There is developed a GUI with wxWidgets for the Gmemu emulator.
• If you would like to set PATH variable to the CalmRISC and Gmemu binaries permanently, you should add necessary lines ("export PATH=/new/path:$PATH" without quotes) to your shell configuration file (when using bash, it's ".bashrc" in your homedir).

~> mkdir reverse
~> cd reverse
~/reverse> calmrisc16-unknown-elf-objcopy -I ihex -O elf32-calmrisc16 firmware.hex firmware.elf
~/reverse> calmrisc16-unknown-elf-objcopy -I elf32-calmrisc16 -O binary firmware.elf firmware.bin
~/reverse> pack firmware.bin firmware.aaz 2000 MUNKEE MASTER
~/reverse> disasm firmware.aaz