THE WAKE UP CHANNEL
Go to bottomPage: 123456
TOPIC:
#2262
Re:R&D and Open-source support 9 Months, 1 Week ago Karma: 3
There is no good reason not to use the Zilog Z8 or other compilers, they're free and they are the most mature offering.

Additionally, the Z8 is a completely different micro from the z80 or z180. They are related only by the manufacturer and nothing else.
MR (User)
Expert Boarder
Posts: 81
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Location: South Florida
The administrator has disabled public write access.
 
#2261
Re:R&D and Open-source support 9 Months, 1 Week ago Karma: 1
markmalanum wrote:
For Open Source, I think SDCC or Small Device C Compiler is an open source compiler for Z80 and Z180 which uses Linux Operating System.

SDCC is a good compiler when targeting the Z80, Z180 or Z8051. But it doesn't have a Z8 backend (there is no specific reason - just that no one ever wrote one).

Philipp
Dr. Philipp Klaus Krause (User)
Fresh Boarder
Posts: 6
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#2240
Re:R&D and Open-source support 1 Year, 3 Months ago Karma: 3
It is indeed sad to have to resort to testing message to see if it's still alive

I see Littelfuse is now the umbrella .. interesting.
MR (User)
Expert Boarder
Posts: 81
graphgraph
User Offline Click here to see the profile of this user
Gender: Male Location: South Florida
The administrator has disabled public write access.
 
#2239
Re:R&D and Open-source support 1 Year, 3 Months ago Karma: 0
testing
Testing (Visitor)
Fresh Boarder
Posts: 1
graphgraph
User Offline
The administrator has disabled public write access.
 
#1907
Re: R&D and Open-source support 5 Years, 9 Months ago Karma: 0
Unless Zilog specifically develops for a Wine target, and did validation testing on Wine, I think running ZDS II under Wine is a crap shoot. It has been more than 10 years since I first started using ZDS II, and I used ZDS 3.68 before there were eZ80 and Z8 Encore. And, I did multiple production designs based on eZ80 and Z8 Encore.

I met some of the Zilog XTools engineers back in 2002 during a visit to Zilog headquarters in San Jose. At the time, there were grand ideas of migrating to a single toolchain, which ideally would run under Eclipse. But that never happened. At this point, I think if Zilog really were interested in a solid solution which would run under Linux, they would be wise to first target CrossOver (from Codeweavers) for their development and testing, with their existing ZDS II code base. But beyond that, there are very slim choices for running solid native apps on Linux (or FreeBSD for example).

Since 2002, the Atmel AVR overtook the Z8 Encore (which at the time was revolutionary with its level of peripheral integration), because there was a binutils port and eventually GCC for the AVR. I still can't understand why there was never any apparent effort (by anyone, nor by Zilog for that matter) to bring up binutils for Z8 Encore, or eZ80, or ZNEO product lines -- and especially GCC. Even today, it would still give these products a much better fighting chance for sales, design wins, and continued/increased success.

Anyway, for a programming solution, I think someone could use pySerial (pyserial.sourceforge.net/) with much better results. However, you'd need to invoke it post-build, assuming the compiler and linker work as expected in the hybrid Wine environment. Unfortunately, I think Zilog has really fallen short on involving or facilitating any 3rd-party integration or plugin facility for ZDS-II in particular. For example, when I inquired specifically about this (recently, within the past 2 years or so), I was told I would need to talk to their VP of Engineering. Meanwhile their web pages listing 3rd-party consultants have also completely vanished.

There's another possibly related thread, 'Integrating ZDSII with 3rd party tools/ Eclipse' here:
www.zilog.com/index.php?option=com_forum...;catid=5&id=1905

And really, I'm not just ranting -- I have done multiple Zilog-MCU-based production designs, and developed custom programming solutions for the Zilog ZDB serial interface for 2 separate employers in the past 10 years. The first one I did a reference implementation in C, which was later converted to C# in a multithreaded configuration, which would program up to 16 devices concurrently, in tiled windows, and flash when the corresponding cable was ready to be plugged to the next un-programmed board. The second one was a Java Webstart application which used the Java SerialPort library (from Serialio.com), and could be started/run either from a network within our facility or externally from a web portal by a contract manufacturer.

A roll-your-own programming solution is probably a few days of effort from scratch if you have a Z8 Encore data sheet, and study the protocol specs.
Douglas Beattie (User)
Fresh Boarder
Posts: 4
graphgraph
User Offline Click here to see the profile of this user
Location: Greater Salt Lake Area, Utah, USA
The administrator has disabled public write access.
 
#1898
Re:R&D and Open-source support 5 Years, 11 Months ago Karma: 2
An update to this thread for completeness:

I have had another go at running ZDS II Encore IDE under Wine in Linux and believe I have solved connecting to the Serial Smart Cable. Details as follows:

Linux distribution: Mint Release 13 (Maya)
Linux kernel: 3.2.0-23-generic running on AMD Athlon II X2 260
Wine version: 1.4
ZDS II Versions tested : eZ8 Encore 4.11 and 5.0

Initially, the PC was powered up first, the smart cable connected and then the target board powered up. However, the IDE would not connect to the Serial Smart cable at all.

After some searching, I realised that for Wine to connect Windows COM1 to the Linux serial port (/dev/ttyS0), wine had to be correctly configured. I went into the appropriate wine directory which contains the dos device mappings:

Code:

$ cd .wine/dosdevices


and then listed the symlinks showing the mapping ("user" will be replaced by your actual login name):

Code:

user@user:~/.wine/dosdevices$ ls -l
total 0
lrwxrwxrwx 1 user user 10 Apr 23  2011 c: -> ../drive_c
lrwxrwxrwx 1 user user 10 Apr 23  2011 com1 -> /dev/ttyS0
lrwxrwxrwx 1 user user 10 Apr 23  2011 com2 -> /dev/ttyS1
lrwxrwxrwx 1 user user 11 Apr 23  2011 d: -> /media/disk
lrwxrwxrwx 1 user user  9 Apr 23  2011 d:: -> /dev/sdg1
lrwxrwxrwx 1 user user  9 Sep 22  2011 e:: -> /dev/sdd1
lrwxrwxrwx 1 user user  8 Dec 23  2012 f:: -> /dev/sr0
lrwxrwxrwx 1 user user  1 Apr 23  2011 z: -> /
user@user-desktop:~/.wine/dosdevices$ 



As can be seen, COM1 is correctly mapped.

As I still could not connect, it occurred to me that I had to belong to the same group as the serial port. This is checked via the ls command:

Code:

$ ls -al /dev/ttyS*
crw-rw---- 1 root dialout 4, 64 Jul 17 22:42 /dev/ttyS0
crw-rw---- 1 root dialout 4, 65 Jul 17 19:17 /dev/ttyS1



I attached my user ID to the dialout group:

Code:

$ sudo gpasswd -a user dialout


I fired up Wine and ZDS II again and this time, I was at least able to get ZDS to detect the smart cable but was unable to connect to the target. Any attempt to connect would get an instantaneous error message:

Code:

Target read/write error. (ERR_DTLI_SERIAL_ERROR)


I then logged out and back in and found that this time, ZDS would try and connect with the progress bar getting to 38% before the same error message would appear. I tried various serial port speed settings in the Project/ Settings/ Debugger menu in ZDS without luck using the "setserial" command in Linux to check the serial port settings matched ZDS:

Code:

$ setserial -a /dev/ttyS0
/dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4
Baud_base: 115200, close_delay: 50, divisor: 0
closing_wait: 3000
Flags: spd_normal skip_test



This appeared to have no effect and I eventually switched off the PC after many failed attempts.

I returned to try my luck again today and this time, the target board and serial smart cable were powered up and connected to the PC before switching the PC on. The system worked first time with ZDS detecting the serial smart cable, connecting to the target and set up ready for debugging the already loaded code (Blinking LED test program). Apparently, the Debugger serial port speed settings don't affect connecting to the target.

In summary:

1. Power up smart cable and target board before switching PC on.
2. Check that wine correctly maps COM1 to your selected Serial port.
3. Make sure you belong to the same group (usually "dialout") as the serial port.
4. Check that the serial port exists and is configured correctly using the "setserial" command.

If someone can verify what I have done, then it would make this a workable solution for ZDS under Linux/ Wine.
MK (Visitor)
Senior Boarder
Posts: 74
graphgraph
User Offline
The administrator has disabled public write access.
 
Go to topPage: 123456
The Sample Center is managed separately
from Zilog's Customer Support services,
and therefore requires a separate login.
Acknowledged! Take me to the Sample Center.
Disable this pop-up in the future.