1. Doing stuff on uClinux
EE590 Autumn 2004

2. What to do, what to do…
Hardware works & runs bundled apps, because John rules
Now we want it to do what we say
It’s simpler than I thought
What follows is a uClinux apps howto
Much is straight from:

3. Get the code tree
The hardware works, so now you need software to run on it
Follow directions on uClinux for Microblaze site for a starter tree from CVS
Will form basis for uClinux image and give lots of code samples

4. Write your stuff Jeremy’s code and code tree are great starters
Use normal microblaze function calls; there’s no MMU to get in the way
Be sure to modify uClinux-dist/include/asm-microblaze/mbvanilla.h for your board

5. Make the uClinux image Add your app to the image build list
Copy into new directory in uClinux-dist/user/ with header files and everything
uClinux-dist/
Documentation/Adding-User-Apps-HOWTO
“make menuconfig” settings:
Vendor: Insight; Product: mbvanilla_net (this will use your modified registers; you could make a whole new entry if you wanted, in uClinux/config)
LibC version: uClibc, check both “Customize Kernel Settings” and “Customize Vendor/User Settings”

6. Make the uClinux image In the first menu: In the second menu:
Make changes necessary for hardware
In the second menu:
Check the box next to your program
make dep; make
Note: may need things like libxil.a
You’ll get a make error, “cannot find –lxil”
Get from hardware files: projectname/mblaze/lib and drop into uClinux-dist/lib
Provides stuff like print, putnum, xil_printf

7. Download the image Build hardware on FPGA
Make sure bootloader code from mbvanilla is right (has correct memory addresses), download bootloader to FPGA
Linux: use dl.sh script that comes with mbvanilla
Windows: open script in text editor and replicate the commands to xmd (run xmd through main xilinx shell somewhere)
Go get a snack

8. Go to town Boot the image, run your program
Add program to boot-time with uClinux-dist/vendors/Insight/mbvanilla_net/rc
Be sure to background it: foo &
Other methods can be used to run it
Cron: schedule script at startup
Other: add required config files to Makefile next to rc, and copy them next to rc too

9. Prologue Microblaze emulator Problems with continuing this project
Who knows what hardware gets it to work
Problems with continuing this project
ee590.ee lacks ample disk space for many tree copies
Code trees diverge quickly, somehow, even with continual cvs updates

10. Prologue Using codesign tools
Just like normal, determine what should be turned into VHDL and become hardware and what should be software on the microblaze
Take software and point it at your created hardware, probably via GPIO bus
Debug

11. THE END