Messages

46

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 27, 2010, 10:51:29 PM »

Now if utasker wasn't already cool enough, you had to go and put tricks like that in it. Simply drag and drop to the simulator when the simulator is paused, and you can see about any thing you want. Nice. I can't wait to try it out.

47

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 27, 2010, 11:44:01 AM »

The problem is that the ARM-USB-OCD device produces 5V/200mA, my meter claims it's using 204mA. So I've got a noisy supply for sure, and the fact that it works at all shows that the programmer MFG didn't push the spec to the absolute min.

Right now, I can assert the SPI pin high and low after doing the above noted setup. So that's looking good. I can also get the below code to compile.

Code: [Select]

CS_CLR_PORT = CS0_LINE;// assert CS low before starting 0001111 containing 00111010
SSPDR_X = 0x8f;//AIS226 PDF pg 18 SPI read bit 8 = 1, pg 21 "who am I" read only at 0001111 containing 00111010
while (SSPSR_X & (SSP_BSY | SSP_RNE)) {                          // wait for transfer to complete and clear rx buffer
volatile unsigned long ulDummy = SSPDR_X;                                     
}
CS_SET_PORT = CS0_LINE;//CS0_LINE;//ulChipSelectLine; // assert CS high end of trans
I believe that code should send 0x8f via SPI, then receive one byte which should contain 0x3A However, I don't know how to get that unsigned long to display on the LCD and I'm not sure I have this buffers and such correct. So what I receive in the unsigned long might be buggered in some manner. Perhaps it might say 8F3A, I'm not exactly sure. Is there a hex2bin until or similar that will let me see raw hex or raw binary?

So I changed gears for a minute and tried the LED PWM thing. I can make that LED PWM pin go low with this line.

Code: [Select]

PINSEL3 |=  1<<21;The simulation window claims that pin is set for PWM. I suspect the screen went blank because the PWM is 0% duty for some reason. So I first wanted to look at PCONP to see if PWM was turned on. I set a break point and tried to figure out how to poke registers to see what's going on inside, but I couldn't figure out how to see whats going on on PCONP or any other register for that matter. Can I see the internal registers in the simulation after a break point?

48

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 26, 2010, 11:36:11 AM »

Things are moving along nicely now. I have code that I think is almost working and it compiles. I'm doing things a bit more low level than I was doing it before. I'm currently testing it piece by piece. The first piece is to make sure I can assert PO.6 SSEL1 low and high. I see the simulation noted it's was an input. I also found fnConfigSPIFileSystem in LPC23xx.C. It appears I needed to change the CSO line to PO.6 so I modified this line in app_hw_lpc23xx.h.

Code: [Select]

#define CS0_LINE            PORT0_BIT6                                  // CS0 line used when SPI FLASH is enabled
I then copied and modified the apparent setup script like this.

Code: [Select]

POWER_UP(PCSSP_X);                                                   // {10} power up the SSP used
CONFIGURE_SPI_PINS();
CONFIGURE_CS_LINES();
SSPCR1_X = 0;                                                        // ensure disabled (master mode)
SSPCPSR_X = 2;                                                       // set clock prescaler (even prescale 2..254)
SSPCR0_X = (FRS_FREESCALE_SPI | DSS_8_BIT | (0 << SSP_SCR_SHIFT)); // set exact frequency and mode
SSPCR1_X = SSP_SSE;                                                  // enableNow the simulation notes P0.6 is an output, and it's typically high. Also when I run this command

Code: [Select]

CS_CLR_PORT = PORT0_BIT6;// assert CS low before startingIt changes to low instead of high. So things appear to be moving along nicely. Then I had to go to work.

While I'm posting, is there a way to dim the LCD display? I'm using the 5V supply from my Olimex ARM-USB_OCD programming device. It appears to work fairly good, but it also appears my PC's USB port keeps blinking power. After a while it will reset. I suspect the PC is having trouble providing enough power and backs it down from time to time. Perhaps letting a chip cool down somewhere. If I can decrease the power draw from the LCD, I think that will make this work more reliably. If I can't decrease the power by dimming the display, I can connect it to an external supply, but that's kind of big and clunky, and it would be nice and compact if I can keep using the OCD device.

Thanks for the help mark, you've been a great help.

49

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 26, 2010, 12:34:35 AM »

I'm getting more syntax errors that I don't understand. Here's the current compile problem.

Code: [Select]

Compiling...
application.c
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(57) : error C2143: syntax error : missing ';' before 'type'
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(63) : error C2065: 'SPI_FLASH_Danger' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(63) : error C2109: subscript requires array or pointer type
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(65) : error C2065: 'SPI_FLASH_Danger' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(65) : error C2109: subscript requires array or pointer type
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(67) : warning C4013: 'fnSPI_command' undefined; assuming extern returning int
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(74) : error C2065: 'ucCommand' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(91) : error C2065: 'SPI_FLASH_Danger' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(91) : error C2109: subscript requires array or pointer type
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(94) : error C2065: 'READ_MANUFACTURER_ID' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(94) : error C2051: case expression not constant
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(98) : error C2065: 'ucTxCount' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(101) : error C2065: 'ucCommand' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(102) : error C2065: 'ucTxCount' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\spi_acc_lpc_ais226.h(105) : error C2065: 'ucTxCount' : undeclared identifier
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(797) : error C2143: syntax error : missing ')' before 'constant'
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(797) : error C2143: syntax error : missing '{' before 'constant'
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(797) : error C2059: syntax error : '<Unknown>'
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(797) : error C2059: syntax error : ')'
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(800) : error C2059: syntax error : 'if'
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(810) : error C2059: syntax error : '}'
Creating browse information file...I copied C:\uTaskerV1.4_LPC\Hardware\LPC23XX\spi_flash_lpc_atmel.h and put it under C:\uTaskerV1.4_LPC\Applications\uTaskerV1.4\spi_acc_lpc_AIS226.h such that it was in the include path, and I could get it to actually include. By leaving it in the original directory, the compiler complained it didn't exist.

I added this to the config.h file

Code: [Select]

#define SPI_AIS226and this is the part I have added to application.c under the fnApplication function.

Code: [Select]

#define _PORT_NMI_CHECK                                                  // {53}
    #include "Port_Interrupts.h"                                         // port interrupt timer interrupt event handling - ranges
#undef _PORT_NMI_CHECK
//8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888
//8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888
//#if defined SPI_INTERFACE
#if defined  SPI_AIS226
#include "spi_acc_lpc_AIS226.h"                                         // port interrupt timer interrupt event handling - ranges
#endif
fnSPI_AIS226_command(READ_STATUS_REGISTER); // read busy status register
    fnSPI_AIS226_command(READ_MANUFACTURER_ID); // read MFG register
    //while (SSP0SR & SSP_BSY) {};                                    // wait for transfer to complete
if (E_LCD_READY == ucInputMessage[0]) {
GLCD_TEXT_POSITION text_pos;// = {PAINT_LIGHT, 2, 0, FONT_NINE_DOT};
text_pos.ucMode = PAINT_LIGHT;
text_pos.usX = 2;
text_pos.usY = 40;
text_pos.ucFont = (FONT_FIVE_DOT);
text_pos.ucMode = (REDRAW | GIVE_ACK);                   // an ack is requested when this has been completely displayed
    fnDoLCD_text(&text_pos, "application.c sais hellow");
}
}

extern void fnSetDefaultNetwork(NETWORK_PARAMETERS *ptrNetPars)Here's a snippet from spi_acc_lpc_ais226.h starting at line 51.

Code: [Select]

#define CONTINUOUS_ARRAY_READ    0xe8


// SPI AIS226 hardware interface
//
//#ifdef SPI_AIS226
static void fnSPI_AIS226_command(unsigned char ucCommand)
{
    #define ulChipSelectLine CS0_LINE  //po6 moso / mosi?
    #define iChipSelect 0
    unsigned char ucTxCount = 3;

    if (SPI_FLASH_Danger[iChipSelect] != 0) {                            // check whether the chip is ready to work, if not wait
        volatile unsigned char ucStatus;
        SPI_FLASH_Danger[iChipSelect] = 0;                               // device will no longer be busy after continuing
        do {
            fnSPI_command(READ_STATUS_REGISTER); // read busy status register
        } while (!(ucStatus & STATUS_READY));                            // until no longer busy
    }I then hit F7 and get the errors noted on the top of this post. I've tried build clean, just in case, but no dice. I'm baffled about what the syntax issue is. I renamed the functions to make them unique because I found that the compiler "go to declaration" option was bringing me to a different piece of code than what I expected. Getting SPI_FLASH_Danger to include is something I can worry about after this basically compiles.

When in spi_acc_lpc_ais226.h and I right click the fnSPI_AIS226_command function, then "go to definition", I get an error message that notes it's not defined. So I believe there must be a syntax error relative to including this file. However the compiler found it, and produced error messages. It appears that application.c worked OK relative to the include, it also complained about the syntax, not that it couldn't find the fnSPI_AIS226_command function. So I believe that's being found OK. Line 798 in application.c is this line.

Code: [Select]

fnSPI_AIS226_command(READ_STATUS_REGISTER); // read busy status registerI'm not sure what the syntax issues is, or how to get this to compile correctly.

50

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 25, 2010, 12:23:30 PM »

I had done several tests that I felt I had correctly removed. Basically learning curve attempts that I then commented out. So I copied that old dir to a new name, and started over. At this point, I've changed some defines in config.h, change the splash screen and initialized screen in application_lcd.h and added this new code to applicaiton.c. I also made a backup copy of the basic config for my board and activated the LCD, so I can get back to a copy I haven't beat to bloody heck.

I found the same error message, but then I moved GLCD_TEXT_POSITION line into the if statement, and all is happy now. I don't know why that might have been the case, I don't see why it wouldn't be able to be stated one line higher in the code, but I guess it can't be done that way. I then found what appears to be some kind of conflict with fnDoLCD_text in both the initialized application_LCD.h code and my application.c code. So I commented out the initialized code in application_LCD.h.

Now that I'm running the LCD from applicaiton.c instead of the .h files, I should be good to try SPI com's. 
So the next step is to copy spi_flash_lpc_atmel.h, get it included while working in application.c then modify it for access to my proto board.

51

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 22, 2010, 03:00:01 AM »

Thanks for pointing out the GLCD thing. I think I'm much closer to getting this to work.

A while back I modified if (E_LCD_INITIALISED == ucInputMessage[0]) { to show a custom splash screen, I also modified else if (E_LCD_READY == ucInputMessage[0]) { to include another small chunk of text, which I believe indicates it's initialized and working normal. Right now my key problem is that I'm not able to correctly initialize the struct in application.c Closest I've been able to get this struct setup is at the top of fnApplication, I've tried it closer to my code lower down the page, but it failed to compile.

Code: [Select]

extern void fnApplication(TTASKTABLE *ptrTaskTable)
{
//#include "config.h"
//#include "application_lcd.h"                                             // {46} LCD tests
typedef struct stGLCD_TEXT_POSITION {
unsigned char  ucMode;
unsigned short usX;
unsigned short usY;
unsigned char  ucFont;
//} GLCD_TEXT_POSITION;
} text_pos;

Lower in that function, this is how I have it drafted.

Code: [Select]

#define _PORT_NMI_CHECK                                                  // {53}
    #include "Port_Interrupts.h"                                         // port interrupt timer interrupt event handling - ranges
#undef _PORT_NMI_CHECK

//8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888
//8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888
//8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888
//8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888
//8888888888888888888888888888888888888888888888888888888888888888888888888888888888888888888

//    GLCD_TEXT_POSITION text_pos;// = {PAINT_LIGHT, 2, 0, FONT_NINE_DOT};
if (E_LCD_READY == ucInputMessage[0]) {
//typedef struct stGLCD_TEXT_POSITION {
// unsigned char  ucMode;
// unsigned short usX;
// unsigned short usY;
// unsigned char  ucFont;
//} text_pos;

text_pos.ucMode = PAINT_LIGHT;
text_pos.usX = 2;
text_pos.usY = 45;
text_pos.ucFont = (FONT_FIVE_DOT);
//text_pos.ucMode = (REDRAW | GIVE_ACK);                   // an ack is requested when this has been completely displayed
    fnDoLCD_text(&text_pos, "Starting...");
}
}

extern void fnSetDefaultNetwork(NETWORK_PARAMETERS *ptrNetPars)You can see the declaration of text_pos is currently commented out in this location, I've tried putting it at the beginning of this file, at the beginning of the function, and some other places. Where it currently resides, is the only place I can get it to compile without generating syntax errors. However I get these lines, so it appears I'm not declaring it correctly.

Code: [Select]

c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(816) : error C2143: syntax error : missing ';' before '.'
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(817) : error C2275: 'text_pos' : illegal use of this type as an expression
        c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(517) : see declaration of 'text_pos'I've also tried GLCD_TEXT_POSITION like how it was done in application_lcd.h. However, these attempts flopped. Right now and the most common way it flops is with a message very similar to those syntax messages.

There's apparently something I don't understand about the syntax formating. I think it's getting closer, but I'm still snagged on something.

52

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 21, 2010, 03:20:37 AM »

I'm learning a bit more.

utasker.c appears to indicate that a task table is setup, and that fnApplication from application.c is one of these tasks that is run often. I think I can call an application_LCD.h function(s) from with in the fnApplication function. However my attempt is currently flopping. Here's my attempt to make this function call.

Code: [Select]

#define _PORT_NMI_CHECK                                                  // {53}
    #include "Port_Interrupts.h"                                         // port interrupt timer interrupt event handling - ranges
#undef _PORT_NMI_CHECK

fnDoLCD_com_text(TASK_LCD, "test", 4);And here's the flop error.

Code: [Select]

Compiling...
application.c
c:\utaskerv1.4_lpc\applications\utaskerv1.4\application.c(799) : warning C4013: 'fnDoLCD_com_text' undefined; assuming extern returning intI suspect that TASK_LCD is incorrect in this location, I was trying different things to see if it would compile. I think it's trying to declare itself at this line, and assumes it's something that it's not. I called it similar to how it's called a couple lines lower in application.c. I don't see any extra #includes or anything like that for those function calls. So I'm a bit confused about what I'm doing wrong.

Also am I on the right trail about calling this function from this area in application.c, and expecting to get some text to display on the screen?

53

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS / MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 19, 2010, 02:08:59 AM »

I was working in the header, because I know I can get the LCD to update based on what is put in that section of code. I'm familiar with why headers are use, that's not the area where I'm ignorant about the compiler. I also understand #include or #define statements can be used to make pieces of code viewable or not viewable when compiling.

I'm more than willing to move my code to application.c, but I don't know how to write something there that will update the LCD from that location. Hmmm, perhaps fnDoLCD_text in application_lcd.h can be called from application.c to display text on the screen from the SPI device? So I create an infinite loop at the end of application.c to make my main loop?  I tried this at the end of application.c.

Code: [Select]

#define _CAN_INIT_CODE
    #include "can_tests.h"                                               // CAN initialiation code and transmission routine
#undef _CAN_INIT_CODE

if (1) {
// text_pos.usY = 45;
// text_pos.ucFont = (FONT_FIVE_DOT);
// text_pos.ucMode = (REDRAW | GIVE_ACK);                   // an ack is requested when this has been completely displayed
// fnDoLCD_text(&text_pos, "application");
}
Ug, why does that produce a syntax error? If I comment out the if and the }, it compiles just fine.

I also tried it with our the loop attempt, and with only the four lines to update the LCD. That also produced several syntax errors.

54

NXP^TM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK

« on: May 18, 2010, 03:59:05 AM »

I've got the proto board on hand now and I'm trying to get back into this SPI eval thing. The SPI device  is attached to UEXT connector, and I had the LPC board displaying custom text via application_lcd.h's E_LCD_INITIALISED if statement.

I seem to be having some trouble figuring out this compiler. For example, in application_lcd.h, if I try to make the grey go away by commenting out the #if and matching #endif statements for this LCD section that includes code I know is being compiled, it will format correctly with green and blue, ect. However it won't compile. I get lots of syntax errors, and misc junk.

So I leave the define, statement, and the grey, and chock it to ignorance about why this is happening.

Then I copy most of spi_flash_lpc_atmel.h into applicaton_lcd.h below the if E_LCD_INITIALISED statement. Theory being that I can cut it down to something simple. My first goal is to simply read the status reg out of the AIS226 chip. I believe that's the same as the datasheet's noted STATUS_REG (0x27) which should read 0000. After a bit of chopping, I see SPI_FLASH_Danger which appears to be a first check before trying SPI stuff. I see it's defined in LPC23XX.c, however spi_flash_lpc_atmel.h file doesn't have an #include statement in the code. So I guess there must be some compiler config file that's allowing it to resolve when it's called in spi_flash_lpc_atmel.h. Another indicator that I don't understand how this compiler gets to point B. I tried to add an include file in my code just before it's called, but that really blew up. Again another indicator that I'm ignorant about this compile process.

So I try it another way. I copied spi_flash_lpc_atmel.h to spi_flash_lpc_AIS226.h in the same dir. Then started hacking out #define options I don't need. When I #include spi_flash_lpc_atmel.h in application_lcd.h, it compiles fine, but when I change that #include to spi_flash_lpc_AIS226.h, it produces a large pile of errors. It would appear that when I stripped out the define stuff, I took something important. It also looks like I can't declare things correctly. Line 5 is the first non-comment in the spi_flash_lpc_AIS226.h file, and looks like this.

Code: [Select]

static unsigned char fnCheckAIS226(void);I get this error.

Code: [Select]

c:\utaskerv1.4_lpc\hardware\lpc23xx\spi_flash_lpc_ais226.h(5) : error C2143: syntax error : missing ';' before 'type'It would appear to me that when it was behind the #define statement before, that changed the compile process, such that it could compile. However, I removed the #define's so it's broken.

So I should ask if using an #include statement in application_lcd.h is an appropriate method, or should I be calling fnSPI_command_AIS226 from spi_flash_lpc_AIS226.h a different way? If calling it that way is an OK theory of operation, how do I fix this syntax error?

55

NXP^TM LPC2XXX and LPC17XX / Re: AIS226DS SPI evaluation on LPC2378-STK

« on: March 07, 2010, 03:40:08 PM »

I think it's time to start my next step. In this case, I'm looking to get data out of a chip using utasker's SPI capabilities, then display a number on the lpc2378stk LCD.

I have changed the plan some from what I mentioned above. I was looking to evaluated the MOD_SMB380 accelerometer from Olimex. I now have a better accelerometer in the works. So I guess I'll change my plan to work with that one. This new board is being assembled from a fellow that works at Sparkfun. Sparkfun tech support suggested him, and he been great to work with while making this breakout board. I believe he'll put these boards up for sale when they are done, so I'll put in a plug for him, if anyone is interested. He's posting the schematics and such, they can be found here.

http://www.aamicron.com/_jh_aamicron_proto_v10.html

It uses the AIS226DS from STmicro. Here's a link to it's data sheet.

http://www.st.com/stonline/products/literature/ds/15164/ais226ds.pdf

The AIS chip is currently set at evaluation status by STmicro, and is up for normal release in Q1 of 2010. ST was kind enough to send me samples for development purposes. It's a 14 bit .25mg/bit resolution 2 and 6 g scale SPI digital 2 axis accelerometer. This break out board is designed to work with Olimex's SPI bus on the Uext connector. However, it is also being setup such that it can be bread-boarded or other. It's a fairly flexible layout.

I looked over the flash tutorial, and I read the other thread where seulater was working with a 2378 and SPI. I don't have a flash device to experiment with, but with luck will have the AIS board in about a month perhaps less. Now that it's time for me to hurry up and wait, I figured it's time to start drafting code to read data from the AIS chip via SPI. I've already played with the LCD, so I feel confident I'll be in good shape for displaying this info once I get it out of the chip.

Are there any suggested SPI starting points that might be nicer than others? Perhaps there are already generic SPI read / write commands available that I'm not familiar with. From the PDF's I was thinking of copying parts of the SPI boot-loader, modifying them to get the right packet structure for the AIS chip. However, it feels like I might overlook something and wipe out the program. Perhaps there is an easier starting point.

56

NXP^TM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK

« on: February 25, 2010, 02:23:49 AM »

What do you know, even though it's grey, I can add break points to that section. Also when I change it, the text on the screen changes. Seems like I'm back up and running. That should keep me occupied for a bit. Thanks.

57

NXP^TM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK

« on: February 24, 2010, 12:15:54 PM »

Now that I've wondered through the initial demo, I'm starting to play with GLCD stuff such that I can get live data out of the device, then eventually I can get I2C data out of the device.

I'm trying to follow the GLCD code, but I'm having trouble. I think I should find the demo code in application_lcd.h. On the LCD screen I see some the text "tasker glcd" and it's only found in this header file. Sounds good, however, the section is grey and it won't let me add a break point. I believe it's gray because it requires an OLED define. I didn't define that because I don't have an OLED display. So this running demo code has to be somewhere else. When I look up and down this file, it's basically all grey. Indicating that the demo code is coming from a different file. By searching for NOKIA_GLCD_MODE I think I see the code in the LCDSim.cpp file.

To me it seems like there is probably a define some where that I should uncomment to make it run a different chunk of code. I don't think I should be modifying the LCDSim code. I tried creating a define for HANDLE_LCD_MESSAGES such that it would run the code under application_lcd.h, but no dice.

Any thoughts on how to get a chunk of LCD code where I can add or modify strings of data?

58

NXP^TM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK

« on: February 20, 2010, 02:40:51 AM »

Works great. I had to clean both the debug build, and the gnu build. I now see exactly the same thing on the LCD as I do in the simulation. Looks good.

With some luck, I'll be able to start the I2C tutorials on Sunday.

59

NXP^TM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK

« on: February 19, 2010, 12:21:46 PM »

You hit that right on the head. I disabled the SD card and off it went. I finished the tutorial. I changed Build_LPC23XX.bat to include this line SET PATH=%PATH%;C:/gccfd/yagarto/bin which matches the yagarto gcc install I got from the default Olimex install. Compiled just fine and I was off to the races. I'm currently experiencing some mild power supply issues. Perhaps a ground loop with the USB and Ethernet or something like that. I'm currently powering this off the 5V ARM-USB-OCD device. I let someone use my bench supply, and I plan to pick that up this evening. With luck I'll have that power supply straightened out and I'll be back in business.

One thing that struck me as odd. I made a brief attempt at the GLCD thing. I defined SUPPORT_GLCD which failed with an error message. I then commented out CGLCD_GLCD_MODE and defined NOKIA_GLCD_MODE. Here's my application.c snippet.

Code: [Select]

//#define SUPPORT_LCD 

blah

#define SUPPORT_GLCD                                                   // enable the task for interfacing to a graphical LCD
#if defined SUPPORT_GLCD
    #define BIG_PIXEL                                                    // display double size in the simulator
  //#define OLED_GLCD_MODE                                               // use an OLED in GLCD compatible mode
  //#define TFT_GLCD_MODE                                                // use a TFT in GLCD compatible mode
    #define NOKIA_GLCD_MODE                                              // use Nokia 6100 LCD in compatible mode
    //#define CGLCD_GLCD_MODE                                              // use colour LCD in GLCD compatible mode

I compiled with the simulator compile process, and got this error message.

Code: [Select]

LPC23XX_ports.cpp
Linking...
GLCD.obj : error LNK2001: unresolved external symbol _CollectCommand
.\Debug/uTaskerV1-4.exe : fatal error LNK1120: 1 unresolved externals
Creating browse information file...
Microsoft Browse Information Maintenance Utility Version 9.00.30729
Copyright (C) Microsoft Corporation. All rights reserved.
Build log was saved at "file://c:\uTaskerV1.4_LPC\Applications\uTaskerV1.4\Simulator\Debug\BuildLog.htm"
uTasker - 2 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========
I took a quick look at uTaskerLCD.PDF, and at least on a quick scan, nothing special jumped out at me. The build log basically tells me it built a bunch of stuff. Perhaps I need to define something. Not sure at this point. I ran out of time while looking for where this GLCD.obj object is being created. I see TFT.c and LCD.c, but no GLCD.c. Should I have a file like that?

60

NXP^TM LPC2XXX and LPC17XX / Re: MOD-SMB380 I2C evaluation on LPC2378-STK

« on: February 19, 2010, 03:00:59 AM »

Turns out my software firewall was blocking the ping ICMP data. It also appears that I have to disable the firewall to allow port 80 to pass through. Seems my PC is set to not operate as a gateway, and that type of traffic is blocked.

Now my problem is with the web page. I can get that orange 404, and I've got what appears to be a successful list of comments from the Copy_all.bat file. However, the simulation is still serving the 404 pages. I'd tried this with crtl, alt and shift reload, to flush the cache. No luck. Well it's off to bed tonight. I'm sure tomorrow with be filled with more delights. From what I've seen of this software, it's great.

Here's a snippet from my copy sequence.

Code: [Select]

drwxr-xr-x 1 502 502 0 Jan 03 2010 dir1
-rw-r--r-- 1 502 502 2219 Jan 00 1980 bmenu.htm
-rw-r--r-- 1 502 502 1146 Jan 00 1980 CTFT.htm
-rw-r--r-- 1 502 502 1689 Jan 00 1980 jstats.htm
-rw-r--r-- 1 502 502 2600 Jan 00 1980 dlan.htm
-rw-r--r-- 1 502 502 2007 Jan 00 1980 fback.jpg
-rw-r--r-- 1 502 502 3077 Jan 00 1980 HI_O.htm
-rw-r--r-- 1 502 502 2339 Jan 00 1980 kserial.htm
-rw-r--r-- 1 502 502 2365 Jan 00 1980 madmin.htm
-rw-r--r-- 1 502 502 1269 Jan 00 1980 ndynamic.htm
-rw-r--r-- 1 502 502 1723 Jan 00 1980 ohelp.htm
-rw-r--r-- 1 502 502 1534 Jan 00 1980 pemailse
-rw-r--r-- 1 502 502 30335 Jan 00 1980 hboard.jpg
-rw-r--r-- 1 502 502 2498 Jan 00 1980 2logo.gif
-rw-r--r-- 1 502 502 2603 Jan 00 1980 6_0menu.HTM
-rw-r--r-- 1 502 502 1114 Jan 00 1980 7LCD.htm
-rw-r--r-- 1 502 502 2600 Jan 00 1980 8lan.htm
-rw-r--r-- 1 502 502 2007 Jan 00 1980 alogo.jpg
-rw-r--r-- 1 502 502 2984 Jan 00 1980 CI_O.htm
-rw-r--r-- 1 502 502 1687 Jan 00 1980 estats.htm
-rw-r--r-- 1 502 502 2340 Jan 00 1980 fserial.htm
-rw-r--r-- 1 502 502 2268 Jan 00 1980 hadmin.htm
-rw-r--r-- 1 502 502 1338 Jan 00 1980 imultabl
-rw-r--r-- 1 502 502 1584 Jan 00 1980 jhelp.htm
-rw-r--r-- 1 502 502 1548 Jan 00 1980 kemailse
-rw-r--r-- 1 502 502 0 Jan 03 2010 imultabl
-rw-r--r-- 1 502 502 1338 Jan 00 1980 imultabl
-rw-r--r-- 1 502 502 1548 Jan 00 1980 kemailse
-rw-r--r-- 1 502 502 1338 Jan 00 1980 imultabl
-rw-r--r-- 1 502 502 1548 Jan 00 1980 kemailse
226 OK.
ftp: 1460 bytes received in 0.39Seconds 3.74Kbytes/sec.
ftp> quit
221 Bye

C:\uTaskerV1.4_LPC\Applications\uTaskerV1.4\WebPages\WebPagesLPC23xx\WebPagesDemo>