56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

Hi there, My interrupts work in ExRam mode but are undefined in Flash mode. Any suggestions? schmighty

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

Where are all the DSP and Motorola experts? "schmighty" , I would like to help you, but as you can see, I have a lot of questions myself! Did you go to the Motorola support site and post your question there as well? Kind Regards Roelof Oelofsen Telkom Development Laboratories Telkom SA >>> "schmighty80222" <> 05/22/02 08:22PM >>

______________________________
New Code Sharing Section now Live on DSPRelated.com. Learn about the Reward Program for Contributors here.



(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )

Good morning, Motorola had a presentation here a month ago and this is the link that I have received from them: The helpline address is I have not tried this link myself yet, so I do not know how valid the link is. I do not know if some of the letters should be capital letters as well. To come back to the rest of your reply: How can I use the PWM interrupt to read the ADC on every 4th interrupt? Can I do this by using the sync pulse? The learning curve on the chip is quite long, especially if you are fairly new to DSP as well. (I am used to 8-bit PIC's). On the other hand, to optimize a DSP is no childs play either, so you can expect the learning curve. The purpose of the SDK (my opinion and replies from this newsgroup) is to get you up and started relatively quickly and then later worry about the nitty-gritty stuff like optimization, memory allignment, etc. You do not have to be a DSP boffin as well. Take for example the DTMF detection library. I do not have to worry about FFT's and that stuff at this stage to detect the tones, I can just use the DTMF_det library. I have come across a few problems lately though, but generally I would still use the SDK later on as I get used to the chip. I will, however, combine C and/or assembly and/or the SDK. (See the periphMemWrite, periphMemRead, etc. commands in the SDK for direct register access) Regards Roelof Oelofsen >>> "schmighty80222" <> 05/24/02 02:43AM >>> Hi Roelof, I didn't realize that Motorola had a support site. Could you list its link. I have the EVM56807 also. As far as your PWM to ADC troubles, at first thought, maybe you can use the PWM interrupt to read the ADC on every 4th interrupt. There's sort of a learning curve on this chip, isn't there? I'm wondering what the advantage is to using the SDK for some of the basic stuff like led workings, pwm use, etc. I'm in the current mindset to try and activate everything in C or assembly. Can anyone tell me why I should use the SDK for PWM for example verses programming it up in C or assembly (not counting portablity to the other family members)? I will appreciate the SDK when I need the vector/matrix functions. Schmighty PS: Maybe the usual responders are on vacation?

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )