Welcome to our site! EDAboard.com is an international Electronics Discussion Forum focused on EDA software, circuits, schematics, books, theory, papers, asic, pld, 8051, DSP, Network, RF, Analog Design, PCB, Service Manuals... and a whole lot more! To participate you need to register. Registration is free. Click here to register now.
I have found the problem.
At the end of the ISR, I was stupidly doing VICVectAddr0 = 0 instead of VICVectAddr = 0.
After correcting that, it works fine.
Dear Experts,
I am trying to execute LPC2138 ADC in burst mode with interrupt, and here is my code:
int data0, data1;
__irq void intAdc(void){
int ad = AD0DR;
int channel = (ad >> 24) & 0x7;
// AD0CR &= ~(0x1 << 16);
// AD0CR &= ~(0x1 << 21);
if(channel == 0){
data0 = (ad >> 6) & 0x3ff...
Ok - I have found the problem, but don't know how to resolve.
The problem is that "at" - even sent as part of data (as in say d"at"a) is considered a command and SIM900 tries to interpret it!
How to suppress this behavior?
Thanks,
Prerak
Thanks BradtheRad.
It seems to be that but I can't catch exactly what.
If I do a newline after data and then terminate the string, it seems to be ok.
However, my confusion is that the AT command and the message string are sent in two stages as follows
void sendTcp(char* line){
char buffer[256]...
I am using ARM LPC2138 with a SIM900 module. One serial port UART0 is used for hyper term and another to communicate with SIM900
I have developed my own serial protocol wrapping over sim900 commands.
Everything works fine, except for a strange issue.
I am using a command wrapper (e.g. ^6:<my...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
