Nzc

Hi Nzc,


Before doing the compare in SAM-BA, did you add a few zeros to the "size" value? If not, it will only read the first small bit of FLASH and since the size isn't big enough it will give you a verification failure.

Regarding EK vs AU... -EK means "evaluation kit" and is the name of the main development board for AT91SAM7X512-AU. It uses the same chip as Netduino which is why we use its script to flash the Netduino. Since they both use the same chip, they both flash using the same configuration.

Chris

Yes, I make sure to read enough bytes to make the comparison. I had a closer look at the data, and it's always the same bit that appears to be 1 when sometimes it should be 0, and only in one memory block. Can it be that the flash memory is corrupt? At least the file I read back is always the same, but different from what I try to write

When I reset gold pad - 3.3V, I can always get back to the CDC connection, and scripts and downloads always run fine, I just don't get the right code in the flash. When reconnecting after the flash, the USB gives a low-level error, and I don't see any info, not even the usual vid/pid stuff.

I'm running SAM-BA 2.12 on Win7-x64, and that works fine. I can do the reset, connect to the Netduino and run the scripts. However, when I flash the bootloader (TinyBooterDecompressor) and then read the file back, there are always differences. Strange thing is, when using the memory spy from the SAM-BA tool, not all errors are visible... I am wondering whether the flash in the Atmel is maybe damaged, or whether there is a problem with the different revisions (EK vs. AU)?

Hi to everybody.
You know I'm a software guy, so, after having been helped so many times here, I try to give something back, even if I know I don't have the electronics expertize to be sure that I'm going in the right direction.
So I invite you to read the readme, and, if you want, take a look at the code: I would like to receive some feedback by the experts, to understand if I'm going on the right direction, or if I'm missing something important, like performance, memory size, and I don't know what else...
Andrea

Hehe, nice to see my evening projects have some use for other people Bit busy lately, but I'll check it out!

If you find any bugs, please send them through, I'm still working on it My current target is the daisy chaining of multiple Tlc-s. The code is very minimal, I'll post an update here when I get it to work. Just a side note: I was discussing this with a colleague here at work, and he told me that these type of PWM drivers usually aren't designed to provide a lot of power to external components. He usually inserts a transistor of FET driven by a high power source. For me, I drive the LEDs from the 5V from the power supply, and then I see a nice 5V block on the scope. If I drive the LEDs from the Tlc, the voltage collapses and I get a block of only ~2V (depending on the exact components of course) About the dot correction: I think it mentions in the datasheet somewhere that by default, the correction factors are 1.0, stored in the Tlc-s EEPROM. You need to explicitly overwrite them by using DCPRG and VPRG. Maybe you hit that accidentally?

One small remarks about the code I posted: when setting up the SPI port, keep the communication speed down to 20 MHz (20000 in the constructor) or so. When I set this to 40 MHz, I see a noticeable flicker when switching. At 20 MHz, all is smooth.