Software Forum Discussions

Hello,

   

PSoc creator has an issue where so-called unused variables are optimized out despite the fact they are written to more than once. C compilers are not supposed to do this. Is there something I can do without having to turn off optimization?

Show Less

Several of the forum posters suggest periodically added features that

   

would be nice in Designer or Creator. But I do not see any Cypress

   

person responding, yay, nay, to the posts. At least a "we saw it....."

   

 

   

Would it be possible to do this ?

   

 

   

Regards, Dana.

Show Less

Hi,

My target is the Hitex XMC HiLight board which is XMC4500F144x1024 so I though I should be OK up to 0x100000 bytes of flash However when I construct a simply program that goes beyond 0x3FFFF I end up with a bus fault.

I've constructed the simplest example I can think of, flashing one LED

#include //Declarations from DAVE3 Code Generation (includes SFR declaration)

#define RED_LED_HANDLE IO004_Handle0

/* This value is OK */
static const char dummyArray[0x3DFFF] = { };

/* This value fails */
//static const char dummyArray[0x3EFFF] = { };

void delay()
{
int i;

for (i=0; i<10000000; i++)
{
}
}

int main(void)
{

DAVE_Init(); // Initialization of DAVE Apps

while(1)
{
IO004_TogglePin(RED_LED_HANDLE);
delay();
}
return 0;
}

Am missing something obvious like a linker option?

Best regards,

Andy Show Less

I had work some weeks on a SD Card interface module for PSoC 3, the module is not stable yet, i get read and write operations, read operation work always fine, but write operation sometimes corrupt the file system. In this post you can find a binary hex file to program the PSoC 3 module in the CY8CKIT-001. The firmware contains a test program for any sd card capacity, the test program list the directories and files on the root directory, no write operation is implemented in the test program to avoid cases where any sd card could be damaged. All the information is transmited using the serial port in the development kit, working at 115200bps.

   

To get the test program working and dont damage the SD Card the development kit MUST be working at 3.3v. The SD Card pins can be conected directly to the pins of the PSoC. The pin conection im using looks like this:

   

SDCard DO pin to P0(1)
SDCard SCK pin to P0(3)
SDCard DI pin to P0(4)
SDCard CS pin to P0(6)

   

RX to P1(6)
TX to P1(7)

   

Get the program running is easy, you only have to program the PSoC 3 device, plug the RS232 port to the PC open a terminal, push the reset button and the directory listing will start.

   

Im sorry that source code is not avaliable because a commercial project is being developed using the module im creating, i hope psoc creator comes soon with the SD Card module by default, will be nice to have a customizer for easy configuration.

   

 

   

Victor Andres

Show Less

Hello there!

Just as a little introduction, this week I have been trying to port lwIP 1.4.0 for the XMC4500 (when I have the current version working we can discuss that) with FreeRTOS and I have been stuck. I have arrived to a state in which I just copied the Dave generated lwIP (its a previous version) and just tried to mimic the results I get with Dave code generation, but with FreeRTOS.

My status now is:

I have a DAVE CE project in which I entered the ETH004 app and dependencies, just configured it to get an address via DHCP and called the stack initialization. As expected, it does DHCP, gets and address and answers to my pings.

I have another non DAVE CE project in which I just have FreeRTOS working. I copied the apps I need (just the Ethernet ones), replaced the Timer App functionality by FreeRTOS timers (and checked it works) and copied the generated initialization. It all seems to work the same, I even get the DMA interrupt when sending, but it is not actually sending anything (checked with Wireshark).

I am using the Hexagon development board and I have been trying to get this working for the last 5 days without success. Obviously there is some initialization or something that I am not seeing, because the problem is pretty low level.

I include the project, if someone has some experience on this and can check it I would be very grateful. You will notice there are two lwip directories under Ethernet; one of them is 1.4.0 with sys_arch implemented for FreeRTOS and some little modifications I have been doing to try to get it working. If we can solve first the problem with the DAVE included version 1.4.0 can probably be solved too.

https://www.dropbox.com/s/0mm7zgc89ouwt1d/Project.zip?m

P.S: I know doing the timeouts from FreeRTOS timers is not a good idea because I the have two different threads accesing the stack, NO_SYS mode. But in this demo there is nothing more and it is jut to simplify and discover the problem, the idea is working with a newer lwIP (it manages timers itself) and with NO_SYS=0

Thank you Show Less