J
Jim Meyer
I got in on a good deal from Cypress. It's their CY8C27443 on a small
board with a USB connection for programming it. Included is fully
operational PSoC designer software with an M8C core C compiler. I've
only looked at the examples so far, but I'm very impressed.
Now for the bad news... The designer software includes a
debugger but it expects to be connected to an ICE with a pod for the
target chip.
With only a target system and a programmer, it looks like I'll
have to debug the old fashioned way;
code-compile-burn-crash-recode-burn-crash-recode, and so forth.
Anybody here have any hints for making program development a
little less painful? I know, "get an ICE", but that's painful in the
wallet.
I suppose I could build a small monitor to run over or under my
application that I could talk to the chip with a serial link. A lot
of older development systems were put together that way. Like the
BUFFALO monitor on the old Motorola eval boards.
Jim
board with a USB connection for programming it. Included is fully
operational PSoC designer software with an M8C core C compiler. I've
only looked at the examples so far, but I'm very impressed.
Now for the bad news... The designer software includes a
debugger but it expects to be connected to an ICE with a pod for the
target chip.
With only a target system and a programmer, it looks like I'll
have to debug the old fashioned way;
code-compile-burn-crash-recode-burn-crash-recode, and so forth.
Anybody here have any hints for making program development a
little less painful? I know, "get an ICE", but that's painful in the
wallet.
I suppose I could build a small monitor to run over or under my
application that I could talk to the chip with a serial link. A lot
of older development systems were put together that way. Like the
BUFFALO monitor on the old Motorola eval boards.
Jim