Archive

Archive for February, 2011

Using Flash and structs on the Altera DE2 board

February 24th, 2011 No comments

For my DMX project on the Altera DE2 board I need to load devices and chasers from the DE2’s Flash memory. I found out that information about this is very hard to find, especially in combination with NIOSII. The, by Altera provided testcode for the DE2 shows a simple routine which reads and writes integer data from and to the Flash memory. This code is listed below.

alt_u32 test_flash( void ) {
	alt_u32 i, errors = 0;
	alt_u32 in_buff[FLASH_MAX_WORDS], out_buff[FLASH_MAX_WORDS];
	alt_flash_fd* flash_handle;

	flash_handle = alt_flash_open_dev( FLASH_NAME );

	/* Create data buffer to write to Flash memory */
	for( i = 0; i < FLASH_MAX_WORDS; i++ ) {
		in_buff[i] = i + 1000000;
	}

	/* Write data to Flash memory */
	alt_write_flash( flash_handle, 0, in_buff, FLASH_MAX_WORDS*4 );

	/* Read data from Flash memory */
	alt_read_flash( flash_handle, 0, out_buff, FLASH_MAX_WORDS*4 );

	/* Check output from Flash memory */
	for( i = 0; i < FLASH_MAX_WORDS; i++ ) {
		if( out_buff[i] != (i+1000000) )
			errors++;
	}
	alt_flash_close_dev( flash_handle );
	return( errors );
}

This simple test routine generates data which will be written to the Flash memory. After writing the routine reads back the data and checks it for errors. Unfortunately, this routine doesn’t show how to deal with structs. For my project I keep track of devices and chasers by storing them into an array of Device and Chaser structs. After some toying around with the built in HAL functions I found out that writing structs to the Flash memory is pretty easy as well. I will show you by a simple example.

First of all we need to define our struct. Note that the alt_u16 and alt_u8 are integer types provided by the HAL.

typedef struct Device {
	char name[MAX_NAME_SIZE];
	alt_u16 unique_id;
	alt_u16 startchannel;
	alt_u8 channels;
} Device;

Now we need to be able to communicate with the Flash memory. Therefore we need to open the device using the built in functions defined in sys/alt_flash.h.

alt_flash_fd* flash_handle;
flash_handle = alt_flash_open_dev( FLASH_NAME );

As you can see in the code above the flash_hanle variable is of the type alt_flash_fd. This is a built in struct and should be used to refer to the flash chip. My SOCP flash object is called flash. To be able to load the corresponding device use FLASH_NAME.

With the device opened we can now communicate with it. With our previously defined struct we create an instance of Device:

Device flash_device;
strcpy(flash_device.name, "FLASH DEVICE");
flash_device.startchannel = 151;
flash_device.channels = 3;

Writing it to Flash is not that hard:

/* Write data to Flash memory */
alt_write_flash( flash_handle, 0, &flash_device, sizeof(flash_device) );

The first argument is the opened flash device handler. The second is the data offset (where to start writing in memory). As third argument we enter the start address of the previously instantiated Device object. The fourth and last argument is the length of data to be written. We enter the size of our Device object instance here.

Of course we want to be able to read back data from Flash as well. The HAL also provides us with a function for that. We need to create a new object to load our data into. I chose to create the object data_out. After reading the data we can print some information in the struct to standard out.

// Output object
Device data_out;

/* Read data from Flash memory */
alt_read_flash( flash_handle, 0, &data_out, sizeof(flash_device) );

printf("Name: %s\n", data_out.name);
printf("Startchannel: %i\n", data_out.startchannel);

The function alt_read_flash takes care of reading the data from the Flash chip. As with the alt_write_flash function the first argument of this function is the Flash device handler. The second is again the data offset. The third argument is the start address of the data object to be filled. We enter the same read length as with the alt_write_flash call. I’m not sure yet about detecting the end of a struct. I’ll maybe update this post with that information later.

The only thing we officially need to do after using the Flash device is closing it.The first and only argument to this function is the Flash device handler.

alt_flash_close_dev( flash_handle );

Well, thats probably it for now. When I find out more useful information about the Flash device I’ll post it here.

Post to Twitter

Categories: Electronica, Technologie Tags: , , , , ,

DMX lightcontrol using FPGA and RS-232 to DMX converter (part 2)

February 22nd, 2011 No comments

The last month I’ve been working hard on my last assignment for my Technical Information Sciences education. The project consists of a DMX light controller built on a Altera DE2 board. It uses an RS-232 to DMX converter so I don’t need to deal with the actual DMX protocol. I focused on building a user interface wherein the user will be able to add devices and connect devices to built in chasers. The project also helps me improving my C programming skills. I found out that programming in C requires a completely different mindset compared to the programming languages I’m more familiar with. In Java, Perl or PHP, the languages I’ve more experience with, I don’t need to deal with memory allocation for example. Apart from Perl I never used pointers in my software. In C I needed pointers many times. It’s a completely different experience, but I enjoy it. The only things I needed was a good C reference manual, a lot of coffee and a quiet room to study. An important pitfall which I had to avoid is “Going too fast and willing to make things too fancy”. This makes the software too complex for my, still developing C skills. I had to keep it simple. Take it easy, learn from others and do small assignments and tests before implementing functionality in the final product.

Now the project is almost finished. I enjoyed developing my C programming skills as well as working with the Altera DE2 board and DMX controlled lights. Like I mentioned in my first post about this project, setting up a proper NIOSII core was a real challenge. I’m glad that I managed to get it working.

Like I said, the software works with devices and chasers. These objects are stored in arrays of structs. A device has a name, start address and a number of channels. Chasers consist of a name, active flag, reference to devices used by the chaser (array of device objects) and a number of required devices. The chasers itself are defined and initialized in code. It was simply too much work to build a system wherein the user can build his own chasers. However, the system can easily be expanded by such functionality. Devices can be added by the user. The menu provide this option by letting the user enter a device name, start address and number of channels. Devices can be connected to chasers in the ‘Chaser’ menu.

I can probably tell a lot more about the setup and code behind the system, but I thing a short video is a much better solution. Sorry for the bad quality. Phone camera…

I called the system ‘DMX Master’. There’s no reason for that other than that I liked it :). The pushbuttons are located on the right part of the DE2 board. C stands for return, M for menu or enter and the < and > buttons… well that’s obvious. Scrolling through the menu only works from right to left. I didn’t had enough time to implement the other direction as well. The most left switch is the reset switch. This one should be enabled at all time. 4 Chasers are built in at the moment which can be set by enabling switches 1 to 4. The fifth switch starts the selected chaser.

Post to Twitter

Categories: Electronica, Technologie Tags: , , , , , ,