jsolarski-backup

I only ever print out the first 20 pages of the datasheets, right before all the data and graphs start. And for the user guide, I only print modules that I am using....eventually you will have most of the modules printed as you learn each one. And I agree, I like having a datasheet printed, so I can make my notes.

Hmm, do you have another 2452 to test? or re-flash the default 1Mhz? I can test the code in a day, i have some un used g2452 lying around.

success ... Rickta' s code works with the 5510.....lol I am so happy right now!!!

I just recieved Rickta's usb code he was working on and it works!!! Now to incorporate it into the newer usb dev api. full project to be posted after this weekend

I think its a great tool to learn Arm and stellaris....Which opens the door to be able to create your own stellaris board for specific applications, or move on to bigger HW

use the crystal fault code to check your crystal. other wise your best bet is to connect it up to the debugger, then run it till you get the error and see where it is screwing up.... Sorry havent used NJs code yet

can you post a link to your project, Right now I am working on porting over usb dev API to mspgcc (cdc, hid, msc) and I would like to see what you did

Excellent! This will make things a bit easier. I will in the future work with the 20bit msp430s, but for now I will stick with the 5510 port of the code

I would improve it by having the ADC just transfer the data to the variable automatically. so when the Timer ISR happens you can run your map function and change the pwm with out any real cpu usage outside of the isr. But otherwise I like your code, Simple and short and works

one step closer...it now compiles but still won't enumerate on the host. i still have descriptors to edit and a bunch of debugging to do.

Thanks pabigot for the info! is the f5510 a 20 bit msp? pabigot, is mspgcc-20120406, 20bit aware?

From IRC -- Rickta __SFR_FARPTR is not jsut a function pointer. It' sprimary purpose is to represent a monolithic 20 bit value, as opposed to a long int value that is represented as 2*16 bit on assembly level. When stored to 'normal' memory, both are 4 byte size. But a normal long int will be put into 2*16 bit registers while an __SFR_FARPTR will be stored in a single register in a special 20 bit mode. Only this way, a 20 bit address can be properly

I am having errors compiling some USB code on mspgcc, the code that I am having issues with is #ifdef __REGISTER_MODEL__ /* for IAR */ # if __REGISTER_MODEL__ == __REGISTER_MODEL_REG20__ # define __DMA_ACCESS_REG__ (void __data20 *) # else # define __DMA_ACCESS_REG__ (unsigned short) # endif #else /* for CCS */ # define __DMA_ACCESS_REG__ (__SFR_FARPTR)(unsigned long) #endif It affects how DMA0DA = __DMA_ACCESS_REG__ dest; //set destination for DMAx DMA0SA = __DMA_ACCESS_REG__ source; //set source for DM

@Iceman85 you should be safe from deletion, you have more then enough posts and are somewhat active.

not all traffic lights are the same. what about ones on poles, or hanging from cables strung across the road. The umbrella is an interesting idea, but what about wind? here in chicago, wind will blow and make snow stick to the side of the traffic lights.