NetBurner Community Forum

The table is a little deceiving and doesn't exactly count from lowest to highest. You'll notice it goes higher from 0x00 to 0x1F then resets again and 0x20 up to 0x3F. The values for 0x1C, 0x1D, 0x1E, and 0x1F are 2304, 2560, 3072, and 3840. I think 2560 is your best bet as 125MHz/2560 = 48.8kHz. Gi...

Hm...There really haven't been any notable changes to the SD card system between the two versions that we're aware of. I've run the same test as you here in the office with a nano and a nano carrier board running a clean version of 2.8.4 and the EFFS-BASIC app on a FAT32 formatted micro-SD card. The...

I'm not exactly sure what it is you're trying to accomplish, but I'll try to elaborate on the example and the PWM behavior. For more precise information, see the MCF5441x reference manual chapter 34 Motor Control Pulse-Width Modulation (mcPWM) in your /nburn/docs/FreescaleManuals directory. Basicall...

Yup. If you read through our interrupt routine, it should be fairly obvious where you're going in the tree. Best of luck developing your protocol driver.

The interrupts are triggered anytime the wires are toggled on the I2C lines basically is the way to think about it. Are we trying to send information out and wrote something to the data register? The interrupt is triggered. Are we trying to do a read and tried to get the byte from the data register ...

Every time I read through that logic, I think it's a little odd looking, but I can't really think of a better way to write it that adds clarity so I haven't changed it. The while loop is while(num > 1) not while(num >= 1), so you'll have read everything into the buffer except the last byte. Why read...

That's right. The SendBuf and ReadBuf commands are meant to be the default library functions. In those functions, all of the underlying read, write, start, restart, and stop commands are used without using the registers i2c explicitly. You'll notice in the ReadBuf command the calls roughly look like...

The answer to your question is two-fold. Yes, the hardware will support an SD driver that runs with the 4 separate data channels. No, the software does not currently support that feature. As of this writing, creating a driver for the SD Host Controller to run SD cards is on the future development li...

I have the square hole as practically in line with the J1 header (further away from the nearest board edge by 5.5 mils (0.14mm)) and down 338 mils or 8.58 mm away from pin 50.

These numbers come straight from the design.

The multichannel I2C drivers currently work in master only mode. You can use 0 and 1 or more modules. I believe the problem we were having with this thread dealt with the I2C macros I2C_SR and I2C_CR which require defining the pointer to i2cModule before use. For instance, to use I2C_CR, you would j...