Re: [Kicad-developers] Updating Paths

Hi, Seth I can merge the kicad-symbols and kicad-footprints MRs later today when we're OK to go. Reviewing those two, the kicad-symbols MR contains many files. I don't think that one looks correct. Given that we're tidying this up, the repo for 3D models is kicad-packages3D but the folder is 3dm

[Kicad-developers] Timestamps in footprint library files

Hi, I've recently noticed (sometime in the past few months) that the footprint library file format has changed to include a timestamp on each of the elements (e.g. each line, each pad), rather than just a timestamp (tedit) per footprint. I guess this was taken into account but it makes "diifs" ve

Re: [Kicad-developers] Auto-generated backup files: are they useful?

This possibility to save the last N backups would be useful. It is what Altium does more or less and it has proven useful to me in the past. Especially if you change your mind after 2h working on something which is not going anywhere :) Thanks, Diego On Tue, 30 Jun 2020 at 15:15, Wayne Stambaugh

Re: [Kicad-developers] DRC rules

completely re-do this UI at some point once we know what the actual DRC >> implementation will be. >> >> We're not doing that yet because the new system is still very much in >> flux. >> >> On Wed, May 20, 2020 at 3:22 PM Diego Herranz < >> diegoherr...

Re: [Kicad-developers] DRC rules

Hi, It's nice getting a powerful rules system. Thank you for all the work. Just because it is slightly related to this. I find misleading that opening Inspect > Design Rules Checker, you get access to modify Minimum Track Width, Minimum via size and minimum uVia size. That is a subset of the Cons

Re: [Kicad-developers] Minimum Boost version

A man can dream xD On Mon, 21 Oct 2019 at 23:15, Jon Evans wrote: > > On Mon, Oct 21, 2019 at 5:53 PM Diego Herranz < > diegoherr...@diegoherranz.com> wrote: > >> >> It looks like by the time 6.0 is out, Ubuntu 16.04 may still be >> officially supported. Just

Re: [Kicad-developers] Minimum Boost version

orted. Just something to have in mind. Cheers, Diego On Mon, 21 Oct 2019, 21:11 Nick Østergaard, wrote: > You can still run 5.1 on 16.04. If you want bleeding edge, don't lock > yourself down with a "stable" system. > > On Mon, 21 Oct 2019 at 21:37, Diego Herranz &

Re: [Kicad-developers] Minimum Boost version

sed when looking at whether our supported OS's had Boost > 1.59 were the dates given here: > http://kicad-pcb.org/help/system-requirements/#_gnulinux. On that page, > it says that our support for 16.04 ended in April. > > -Ian > > On Mon, Oct 21, 2019 at 8:03 P

Re: [Kicad-developers] Minimum Boost version

I wasn't getting any nightly package update lately and checking [1] I've just noticed this boost bump has left Ubuntu 16.04 (Xenial) out. Ubuntu 16.04 will be supported until April 2021 [2]. Was this overlooked when checking distros? Or was it a deliberate decision? Is there anything that can be d

[Kicad-developers] CERN Open Days

Hi, all The CERN Open Days (https://opendays.cern/) will be held this weekend. I'll be there on Sunday. Will any developer or librarian be there? Or any of the guys working at CERN? Just for a quick hello and putting faces to names. Thanks. Cheers, Diego

Re: [Kicad-developers] [PATCH] Board statistics dialog

l > usage would be to estimate he complexity (and cost) of pcb routing. I'm > asking myself if Alexander's code can be extended to be used also in > eeschema, so that we can have an almost identical "statistics" window there > with minimal effort and consistent interfa

Re: [Kicad-developers] [PATCH] Board statistics dialog

etailed area" of a board based on any polygonal outline. > >> Is there any value in it this way? PCB manufacturing charges are > generally per-square area because ultimately the price is on panel space > you are using. > >> > >> On Sat,

Re: [Kicad-developers] [PATCH] Board statistics dialog

, > > Wayne > > On 7/27/19 5:06 AM, Diego Herranz wrote: > > I've been testing this dialog and I think it is a nice addition. Thanks! > > > > There seems to be something wrong with the area calculation, though. See > > image below: > > area.png > &g

Re: [Kicad-developers] Bus upgrades merge

Thanks, JP. I've created https://bugs.launchpad.net/kicad/+bug/1838140. Cheers, Diego On Sat, 27 Jul 2019 at 15:03, jp charras wrote: > Le 27/07/2019 à 14:35, Diego Herranz a écrit : > > Hi, all. > > > > I'm using nightlies and facing a weird bug with buses. I w

Re: [Kicad-developers] Bus upgrades merge

Hi, all. I'm using nightlies and facing a weird bug with buses. I was wondering whether it can be related to these bus upgrades. I've got a bus: ROW0, ROW1, ROW2, ROW3, ROW4, ROW5, ROW6, ROW7, which on the PCB layout becomes ROW0, ROW0, ROW0, ROW0, ROW0, ROW0, ROW0, ROW7 ??? It seems to be semi-r

Re: [Kicad-developers] [PATCH] Board statistics dialog

I've been testing this dialog and I think it is a nice addition. Thanks! There seems to be something wrong with the area calculation, though. See image below: [image: area.png] Thanks, Diego On Tue, 23 Jul 2019 at 11:18, Ian McInerney wrote: > Alexander, > > Instead of declaring the 2 static v

Re: [Sdcc-user] pic14 users: Please test the pic14 branch!

>> I think the right way to go here should be to consider obsolete and discourage this way to define values for the configuration words and implement it through pragmas (as pic16 already does), and extend it to also support ID locations. +1. It would be good to make pic14 and pic16 as similar as p

Re: [Kicad-developers] Ratsnest options

>> As far as Preferences, I agree that it’s the right place for curved/straight (well, actually I’d be inclined to just offer curved, but I already lost that fight) Quick question: is curved ratsnest the default? I think it looks much better so I'd vote to make it the default if it isn't, especiall

Re: [Kicad-developers] [PATCH] Option to not render 3D models for footprints

>> Maybe a better option would be to have footprint variations similar to >> aliases. >> Something with a new name, new 3d model path and new description but the >> same land pattern. This would be great and ease the libraries development quite a lot. Diego On Mon, Mar 25, 2019 at 8:50 PM Rene

Re: [Kicad-developers] Why we chose to put libraries in directories?

My 2 cents. Having separate files is very convenient when dealing with Pull Requests on the git libraries repos. On the kicad-symbols repo (1 file contains many symbols) there are many more merging conflicts than on kicad-footprints (1 file per footprint). Having said that, I understand that zipp

Re: [Kicad-developers] Some of our symbols currently still have invisible power pins. We want to fix this but want to give you guys a chance for input first.

Hi, Rene. Thanks for bringing this up. I've never liked hidden power pins. In my opinion, the python philosophy applies here too: "Explicit is better than implicit." How many libraries will need this? I'm asking because, if we went for option 3 (or 2), will we end up with a lot of nearly identica

Re: [Kicad-developers] 5.1 UI feedback

gt;> > >>>> I second this motion. I didn't find the right click trick so I fell > >>>> back to cvpcb which is overkill to change the footprint of a single > >>>> symbol. A tooltip might be useful here as well. > >>>> > >>>> On 7/1

Re: [Kicad-developers] 5.1 UI feedback

Hi, I've started to test these changes and, on the Symbol properties dialog, I found it hard to assign a footprint. Before, there used to be a button to open the Footprint selector window. Now you seem to need right click on the footprint field and "select footprint" and that only works if you're

Re: [Kicad-developers] Fabrication Outputs and Plot

Gentle reminder. Thanks, Diego On Tue, Feb 27, 2018 at 12:16 AM, Wayne Stambaugh wrote: > This looks fine to me. Does anyone else have any objections to this > change? > > On 02/25/2018 03:17 PM, Diego Herranz wrote: > >> Thanks for your replies. I think there's a

Re: [Kicad-developers] Fabrication Outputs and Plot

keby.ie>>> wrote: >> >>> >> >>>Plot SVG and Export SVG are different. The former goes >> >>>through the Plot code while the later goes through the >> Print >>

[Kicad-developers] Fabrication Outputs and Plot

Hi, Now that so much work is happening on re-structuring menus, I've remembered something I have always found weird on pcbnew. "Plot", from wihch you can obtain Gerbers is not inside "Fabrication Outputs", but on its own. I find it weird to have the drill option inside "Fabrication Outputs" but n

Re: [Kicad-developers] Schematic symbol chooser clarification

I can relate to this issue. It happened to me as well and I thought my library setup wasn't right. Then I found out it was showing power symbols only. +1 to make it more evident. At least changing the dialog title? Thanks, Diego On Mon, Feb 5, 2018 at 1:22 PM, kristoffer Ödmark < kristofferodmar

Re: [Kicad-developers] desired layer sequence for pcb technical layers

Regarding Front vs Top, I see it called Top everywhere else, but back to the original question: +1 for Top/Front first. Thanks, Diego On Thu, Jan 11, 2018 at 5:52 AM, Andrey Kuznetsov wrote: > Why is it Front and Back, as opposed to Top and Bottom? > Front/Top should be first. > > On Wed, Jan 1

Re: [Kicad-developers] Migrating old designs best practice

Thanks for the tip. I'll use it to check schematics wiring. Diego On Sun, Nov 26, 2017 at 6:53 PM, jp charras wrote: > Le 26/11/2017 à 19:15, Diego Herranz a écrit : > > It's interesting that only happen if I rescue symbols. > > > > Anyway, thanks for the help a

Re: [Kicad-developers] Migrating old designs best practice

nagement code. > Eeschema used to allow degenerate connections like that, where an L was > superimposed to a wire, connecting into a junction. > > On Sun, Nov 26, 2017 at 4:59 AM, Diego Herranz < > diegoherr...@diegoherranz.com> wrote: > >> Please ignore the previo

Re: [Kicad-developers] Migrating old designs best practice

Please ignore the previous attachments. They should have been these. Thanks. On Sun, Nov 26, 2017 at 10:55 AM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > Hi, Nick > > Changes like: (- is removed, + added) > > -Wire Wire Line > - 12550 700 12600 700 >

Re: [Kicad-developers] Migrating old designs best practice

(after.png). Maybe it wouldn't have happened if the connections were nice in the first place, but I wasn't expecting them to break. Thanks! On Sat, Nov 25, 2017 at 9:15 PM, Nick Østergaard wrote: > What modifications are made to the wires? > > 2017-11-25 21:28 GMT+01:00 Diego Her

Re: [Kicad-developers] Migrating old designs best practice

Hi, Related to this, I'm migrating an old design (~2 month old nightly) to the current master. First I faced some problem with '/' characters ( https://lists.launchpad.net/kicad-developers/msg31705.html) but there have been some improvements since then so I'm trying again. When opening the schema

Re: [Kicad-developers] New symbol table: problems with '/' characters?

but it will take me a while to get it the way I want it. > > Cheers, > > Wayne > > On 11/18/2017 08:00 AM, Diego Herranz wrote: > > Thanks. I'll chase that bug. > > > > Diego > > > > On 18 Nov 2017 11:35 am, "Nick Østergaard&quo

Re: [Kicad-developers] New symbol table: problems with '/' characters?

Thanks. I'll chase that bug. Diego On 18 Nov 2017 11:35 am, "Nick Østergaard" wrote: > See https://bugs.launchpad.net/bugs/1732236 > > 2017-11-18 11:42 GMT+01:00 Diego Herranz : > >> Hi, >> >> I'm testing a recent build (41f9c19b) on Ubuntu

[Kicad-developers] New symbol table: problems with '/' characters?

Hi, I'm testing a recent build (41f9c19b) on Ubuntu 16.04 64 bits. When opening a schematic made with a nightly build ~2 months old, the remapping dialog shows up. So far so good. I've followed the recommendations in http://kicad-pcb.org/post/symbol-lib-table/ and most things seem to be working

Re: [Kicad-developers] KiCad Libraries (again)

Hi, I've just submitted a pull request ( https://github.com/KiCad/kicad-website/pull/236) trying to make a bit more clear when/why you need to update the libraries. Also adding links to github lib repos. Comments welcome :) Thanks, Diego On Sun, Nov 5, 2017 at 10:33 PM, Diego He

Re: [Kicad-developers] KiCad Libraries (again)

Thanks, Rene On 4 Nov 2017 4:06 pm, "Rene Pöschl" wrote: On 03/11/17 21:34, Diego Herranz wrote: > First of all, I think all the recent work around the libraries is great! > Thanks to everyone involved. I think sometimes libraries are underestimated > (not just in KiCad).

Re: [Kicad-developers] KiCad Libraries (again)

First of all, I think all the recent work around the libraries is great! Thanks to everyone involved. I think sometimes libraries are underestimated (not just in KiCad). If KiCad manages to have extensive, high-quality and clearly arranged libraries, many more users will end up using it. Having sa

Re: [Kicad-developers] GitHub Plugin (my nemesis)

I completely understand Oliver's view on maintaining every individual repo even if they are submodules of a kicad-footprint repo. Even from an a user perspective (which is clearly easier than the maintainer one), I like knowing what progress is being made, so I'd like to subscribe for updates of a

Re: [Kicad-developers] New feature: support for Gerber job file.

Hi JP, Is this something new in GerberX2? I had never seen Gerber jobfiles before... I've given it a try (export and then load on GerbView) and seems to work OK, it loads every layer by just loading the jobfile. Any other gerber viewer which supports it to give it a try? gerbv

Re: [Kicad-developers] ATTN: Package Maintainers - RFC: Library Reorganization

want to merge them into a single kicad-footprints > > repo but this will require a lot of work because we have to maintain > > support for users who use the GitHub plugin to access repositories > > individually. I have yet to develop a clear plan to address this. One > > thing at

Re: [Kicad-developers] ATTN: Package Maintainers - RFC: Library Reorganization

Hi, Oliver. When I started using KiCad I got confused with the repos for symbols, footprints and 3D models. I think it's getting better and this will make it easier. Thinking of naming, should we use "kicad-packages3d" to keep the same format (kicad-symbols)? On a separate note, how does this wo

Re: [Kicad-developers] [PATCH] correct text inside two importantplot windows

Hi, Random comments for a few of the topics discussed or proposed: - "Format" -> "Coordinate Format": The Gerber standard uses Coordinate format for this, so I think this change is OK. - "solder mask" vs "s

Re: [Sdcc-user] New STM8 OpenOCD and gdb debugger available

Sounds interesting, thanks for letting us know. Any plans on submitting your changes to the different upstream projects (OpenOCD, SDCC, etc.)? Any reason not to? Cheers, Diego On Mon, Mar 6, 2017 at 1:34 PM, Åke Rehnman wrote: > For all interested in STM8 and gdb debugger I hereby announce the

[Kicad-developers] [PATCH]: Calculator: Simplify color code tolerance chooser + typo

eate another patch for the typo only. Thanks, Diego From 03ee65284fdb24aea5eb8499b0044b3e56747ac7 Mon Sep 17 00:00:00 2001 From: Diego Herranz Date: Sat, 25 Feb 2017 06:22:17 + Subject: [PATCH] Calculator: Simplify color code tolerance chooser + typo Since for this tool the only difference f

Re: [Kicad-developers] [PATCH] Pcbnew, plot dialog: grey out advanced net attributes if Gerber X2 is unchecked.

od to me, I pushed it. Thank you for your contribution to > KiCad. > >>> > >>> It's easy for patches to slip through the cracks - in the future, don't > >>> be afraid to bump a patch a bit sooner, say within a week or two. > >>> Apologie

Re: [Kicad-developers] [PATCH] Pcbnew, plot dialog: grey out advanced net attributes if Gerber X2 is unchecked.

Hi, Did anyone have a chance to look at this? Many thanks. Regards, Diego On Tue, Nov 22, 2016 at 8:10 AM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > > m_useGerberNetAttributes is useless if m_useGerberX2Attributes is not > checked. > So disabled (greyed out) w

[Kicad-developers] [PATCH] Pcbnew, plot dialog: grey out advanced net attributes if Gerber X2 is unchecked.

m_useGerberNetAttributes is useless if m_useGerberX2Attributes is not checked. So disabled (greyed out) when Gerber X2 gets unchecked to make it clear to the user. --- pcbnew/dialogs/dialog_plot.cpp | 20 pcbnew/dialogs/dialog_plot.h| 3 ++- pcbnew/dialogs/dialo

Re: [Kicad-developers] [PATCH] Pcbnew: fix plot dialog tip text

Thanks! By the way, I just spotted the "PLEASE DO "NOT" EDIT THIS FILE!". Oops! Thanks for fixing it the right way :) Diego On Sat, Nov 19, 2016 at 9:31 AM, jp charras wrote: > Le 19/11/2016 à 00:12, Diego Herranz a écrit : > > > > I guess this was a liter

[Kicad-developers] [PATCH] Pcbnew: fix plot dialog tip text

I guess this was a literal translation from French "Ne plus..."? Signed-off-by: Diego Herranz --- pcbnew/dialogs/dialog_plot_base.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pcbnew/dialogs/dialog_plot_base.cpp b/pcbnew/dialogs/dialog_plot_base.cpp ind

[PATCH] doc: usb: Fix typo in gadget_multi documentation

It tries to "match" drivers for each interface (not "much"). Signed-off-by: Diego Herranz --- Documentation/usb/gadget_multi.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/usb/gadget_multi.txt b/Documentation/usb/gadget_multi.txt in

[PATCH] doc: usb: Fix typo in gadget_multi documentation

It tries to "match" drivers for each interface (not "much"). Signed-off-by: Diego Herranz --- Documentation/usb/gadget_multi.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/usb/gadget_multi.txt b/Documentation/usb/gadget_multi.txt in

[PATCH] doc: usb: Fix typo in gadget_multi documentation

It tries to "match" drivers for each interface (not "much"). Signed-off-by: Diego Herranz --- Documentation/usb/gadget_multi.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/usb/gadget_multi.txt b/Documentation/usb/gadget_multi.txt in

Re: [Sdcc-user] [sdcc-devel] SDCC 3.5.0 Released

Thank you very much Maarten and all the SDCC developers for keeping this great project! Cheers! On Wed, Jun 24, 2015 at 10:55 AM, Maarten Brock wrote: > Hello SDCC friends, > > Today a new release of SDCC was made. We are now at version 3.5.0. > You can get it at: > http://sourceforge.net/proje

Re: [Sdcc-user] CONFIG in PIC18F4550

Since every protection (code, eeprom, etc) seems to be disabled, why don't you ask your user to read back what he programs so you can compare? Regards, Diego On Fri, May 8, 2015 at 7:10 AM, Kustaa Nyholm wrote: > On 08/05/2015 08:58, "KHMan" wrote: > > >Has that been > >ruled out? > > Good poi

Re: [Sdcc-user] ANNOUNCE diolan-plus2 bootloader

Thanks a lot Kustaa. I think this can be useful to many people. Regards, Diego On Sat, Jan 31, 2015 at 11:03 AM, Kustaa Nyholm wrote: > Hi, > > > I'm happy to say that now my diolan's bootloader works with standard > instructions > set and the code compiled with SDCC works with it too! > > I've

[Desktop-packages] [Bug 1391508] [NEW] Newer version available message shoudn't be shown

Public bug reported: Using pitive 0.93-3ubuntu0.1, I get a message saying "Pitivi 0.94.0 is available". IMHO that message shouldn't be shown if pitivi has been installed from repositories. It may lead to confusion to users which will try to install new version (maybe from the pitivi website) whil

[Bug 1391508] [NEW] Newer version available message shoudn't be shown

Public bug reported: Using pitive 0.93-3ubuntu0.1, I get a message saying "Pitivi 0.94.0 is available". IMHO that message shouldn't be shown if pitivi has been installed from repositories. It may lead to confusion to users which will try to install new version (maybe from the pitivi website) whil

[Ubuntustudio-bugs] [Bug 1391508] [NEW] Newer version available message shoudn't be shown

Public bug reported: Using pitive 0.93-3ubuntu0.1, I get a message saying "Pitivi 0.94.0 is available". IMHO that message shouldn't be shown if pitivi has been installed from repositories. It may lead to confusion to users which will try to install new version (maybe from the pitivi website) whil

Re: [Sdcc-user] stm8 tutorials

I was doing something very similar for the SDCC PIC ports (Blinking LEDs and 7 segment displays for the time being) with the idea of somebody expanding it for the rest of SDCC ports (which I don't know about) so it can serve as an entry point to SDCC. Every now and then I see messages on the maili

Re: [Sdcc-user] gputils-1.4.0 released

Thanks for your work. "The gpdasm shows the names of SFRs and bits, in addition shows the labels in code." Hell yes!! Thanks! On Tue, Oct 14, 2014 at 10:05 PM, Gál Zsolt wrote: > Hello Károly, > > Thank you for a good news! Gputils is better than ever. > > Zsolt > > 2014-10-14 20:08 GMT+02:00 M

Installation of Ubuntu GNOME 14.04 using software RAID

Hi! I had always used Alternate CD installs of Ubuntu to set a software RAID when installing. Now that there's no such a Alternate CD available, how could I install using software RAID? I've read about installing ubuntu-server and then installing GNOME environment but I'm afraid of not obtaining

Re: [Sdcc-user] PIC programmer support

Let me add info of another PIC programmer, it's called USB PIC Prog ( http://usbpicprog.org/) - It's open source (SW and HW) - You can build the HW or buy it (20€) - Works over USB - Works on Windows, Mac and Linux - Graphical or command line interface Maybe the weakest point is not being able to

Re: [Sdcc-user] Banking 101 for 18F PICs

You can simply use variables (global or local/automatic depending on what you need) and SDCC+GPUTILS will place them wherever they consider and instructions for switching banks will be generated automatically when accesing/using those variables. So, unless you need variables to be on specific addr

Re: [Sdcc-user] I want to start working on SDCC

Hi! On Fri, Dec 20, 2013 at 6:49 PM, Masur Jonathan wrote: > Sorry if what I'm asking is dumb. > > I'd like to get started helping to develop SDCC. However the first thing > is that I should understand as well as possible how its internal works. > I downloaded the sources and managed to compile

Re: [Sdcc-user] Bug with PIC18F interrupt routine definition

-Wl-sMylinkerScript.lkr test.c Could you send both .lst files (the working and the not working one) for us to inspect them? Regards, Diego Herranz On Thu, Feb 28, 2013 at 10:25 AM, Butuza Tamas wrote: > Dear sdcc users and developers, > > At the past I used sdcc for 14 bit pic dev

Re: [Sdcc-user] SDCC and PIC18F12220

"Downgrading sdcc will work. But I would recommend upgrading gputils instead." Absolutely. There have been a lot of bug fixes and improvements for PIC port since 2.9.0. On Mon, Nov 12, 2012 at 11:58 AM, Philipp Klaus Krause wrote: > On 12.11.2012 11:54, Soloviov Dmitry wrote: > > Thank you! >

Re: [Sdcc-user] SDCC and PIC18F12220

Yes, crt0i initializes variables, stack, etc and calls main(). You can see what it does more in detail here: http://sdcc.svn.sourceforge.net/viewvc/sdcc/trunk/sdcc/device/lib/pic16/startup/crt0i.c?view=markup . Just an offtopic comment: I would write void main(void) instead of void main(). On M

Re: [Sdcc-user] New sdcc developmentr team member

Hi Károly! Thanks for helping the SDCC community. PIC port users will be very happy with your contributions. Regards, Diego Herranz On Tue, Oct 16, 2012 at 9:59 AM, Alexandre Martins wrote: > Hello Károly! > > I am glad that you will work on adding more PIC support to SDCC. I wish

Re: [Sdcc-user] SDCC 3.2.0 release packages prepared

It looks related to this patch apllied in #8008: http://sourceforge.net/tracker/?func=detail&aid=3539804&group_id=599&atid=100599 On Mon, Jul 9, 2012 at 3:38 PM, Diego Herranz wrote: > I find an error with PIC16 code. I think that it is related with fuses and > CONFIG. RC3

Re: [Sdcc-user] SDCC 3.2.0 release packages prepared

I find an error with PIC16 code. I think that it is related with fuses and CONFIG. RC3 works fine, though. I get the following errors: [..] test.asm:4892:Error[152] Executable code and data must be defined in an appropriate section. test.asm:4895:Error[152] Executable code and data must be def

Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 3

PIC16 (18F4550) tested on linux x86. Exactly the same code generated than RC2. Regards, Diego On Fri, Jun 29, 2012 at 6:56 PM, Borut Ražem wrote: > SDCC 3.2.0 Release Candidate 3 source, doc and binary packages for x86 > Linux, 32 bit Windows and universal Mac OS X are available in > correspon

Re: [Sdcc-user] SDCC 3.2.0 Release Candidate 2

Tested for PIC16 (18f4550) on linux x86. It seems to work fine and code reduction of about 0.3% versus a snapshot 1 month old. Regards, Diego Herranz On Sun, Jun 24, 2012 at 8:54 PM, Borut Ražem wrote: > SDCC 3.2.0 Release Candidate 2 source, doc and binary packages for x86 > Linux,

Re: [Sdcc-user] Debian package for the upcoming Debian release

Great! It would be fantastic to update the stable releases often. Thank you two for the effort. On Wed, Jun 6, 2012 at 12:28 PM, Philipp Klaus Krause wrote: > Am 31.05.2012 17:44, schrieb Diego Herranz: > > Any progress on Debian packages? > > > > Thanks! > >

Re: [Sdcc-user] Debian package for the upcoming Debian release

Any progress on Debian packages? Thanks! On Fri, May 18, 2012 at 11:47 AM, Philipp Klaus Krause wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 18.05.2012 10:54, Gudjon I. Gudjonsson wrote: > > Hi list > > > > Quite soon after the release of sdcc 3.1 I had a package ready for >

Re: [Sdcc-user] Fuse definitions for pic18f46j50.h

Tested. It seems to work like a charm. Thanks again! On Mon, May 28, 2012 at 11:03 AM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > Great. > > I'll test it as soon as the snapshot is built. > > Thank you very much! > > On Mon, May 28, 2012 at 9:24 AM,

Re: [Sdcc-user] Fuse definitions for pic18f46j50.h

Great. I'll test it as soon as the snapshot is built. Thank you very much! On Mon, May 28, 2012 at 9:24 AM, Borut Ražem wrote: > #pragma config accepts underscore characters in svn revision #7797. > > Borut > > > > On Sun, May 27, 2012 at 11:51 PM, D

Re: [Sdcc-user] Fuse definitions for pic18f46j50.h

Great! Thank you. On Sun, May 27, 2012 at 10:47 PM, Borut Ražem wrote: > Yes, the problem are underscores :-(. I'll fix it ASAP. > > Borur > > > On Sun, May 27, 2012 at 1:49 PM, Diego Herranz < > diegoherr...@diegoherranz.com> wrote: > >> Sorry,

Re: [Sdcc-user] Fuse definitions for pic18f46j50.h

Sorry, line 31 was: 31 #pragma config FOSC = HSPLL_HS On Sun, May 27, 2012 at 1:43 PM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > With 18f4550 and sdcc #7792: > > [...] > 26 #pragma config PLLDIV = 1 > 27 #pragma config CPUDIV = OSC1_PLL2 > 28 #pragma con

Re: [Sdcc-user] Fuse definitions for pic18f46j50.h

With 18f4550 and sdcc #7792: [...] 26 #pragma config PLLDIV = 1 27 #pragma config CPUDIV = OSC1_PLL2 28 #pragma config USBDIV = 2 29 30 31 #pragma config FOSC USBDIV = HSPLL_HS [...] Warnings: MIDI_PEDAL_fuses.h:27: warning 191: #pragma config: bad argument(s); pragma ignored MIDI_PEDAL_fuses.h:3

Re: [Sdcc-user] Fuse definitions for pic18f46j50.h

Thanks! On Sat, May 26, 2012 at 10:37 AM, Borut Ražem wrote: > #pragma config is correct. #pragma configure was a mistake in sdccman. I > alredy corrected it. > > Borut > > > On Sat, May 26, 2012 at 3:26 AM, Diego Herranz < > diegoherr...@diegoherranz.co

Re: [Sdcc-user] Fuse definitions for pic18f46j50.h

sdccman says: #pragma config setting=value [, setting=value] but just after: #pragma configure CP0=OFF,OSCS=ON The former is the correct one, isn't it? Thanks On Fri, May 25, 2012 at 9:27 PM, Borut Ražem wrote: > On 25. 05. 2012 18:43, Richard Hughes wrote: > > I've built master, and tried

Re: [Sdcc-user] Debian package for the upcoming Debian release

BTW, do you know the state of gputils package? Is anybody maintaining it? Thanks On Fri, May 18, 2012 at 11:22 AM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > I would really love to see sdcc debian packages updated. > As a PIC16 port user, I'd like to see the sdcc

Re: [Sdcc-user] Debian package for the upcoming Debian release

I would really love to see sdcc debian packages updated. As a PIC16 port user, I'd like to see the sdcc-non-free package too. I hope you find a sponsor. Thanks On Fri, May 18, 2012 at 10:54 AM, Gudjon I. Gudjonsson wrote: > ** > > Hi list > > Quite soon after the release of sdcc 3.1 I had a pac

Re: [Sdcc-user] [PIC16] Exporting full memory range in hex

in case it is useful for somebody. Regards, Diego On Tue, Jan 31, 2012 at 1:22 PM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > I don't need fuses in the file because fuses are determined but bootloader > and you can't change them later. > Fuses are out of the 3

Re: [Sdcc-user] [PIC16] Another way to read/write EEPROM?

I'm starting to think like Kustaa even tough I started this topic. Anyway, I went on testing, and I think that eeprom8_write and eeprom16_write are missing a return asm instruction. If eventually we don't want to have this eeprom pointer access feature, it would be nice to turn it into a library

Re: [Sdcc-user] [PIC16] Another way to read/write EEPROM?

Thanks, I'll test it and let you know. On Sun, Apr 22, 2012 at 2:57 PM, Raphael Neider wrote: > Hi, > > > Testing the eeprom pointer accesses, I think I've found a bug: > > > > Simulating with Proteus VSM: "Attemp to write to EECON2 without setting > WREN > > bit is ignored." > > > > WREN can be

Re: [Sdcc-user] [PIC16] Another way to read/write EEPROM?

On Fri, Apr 20, 2012 at 12:52 PM, Diego Herranz < diegoherr...@diegoherranz.com> wrote: > Thanks Raphael! > > I'll try to test it this weekend and I'll let you all know. > > Thanks a lot! > > > On Fri, Apr 20, 2012 at 8:37 AM, Frieder Ferlemann < &g

Re: [Sdcc-user] [PIC16] Another way to read/write EEPROM?

Thanks Raphael! I'll try to test it this weekend and I'll let you all know. Thanks a lot! On Fri, Apr 20, 2012 at 8:37 AM, Frieder Ferlemann wrote: > Hi Raphael, > > Am 20.04.2012 01:05, schrieb Raphael Neider: > > starting with svn 7610, sdcc/pic16 allows read/write access EEPROM via > > gen

Re: [Sdcc-user] [PIC16] Another way to read/write EEPROM?

Great! I started the implementation of gptr/*.c and I had the same doubt: what to do with EEADRH. Let us know how you do it eventually. Thanks for all your help. Diego On Mon, Apr 16, 2012 at 7:41 PM, Raphael Neider wrote: > Hi, > > > Maybe I could help you with implementation of eeprom reads

Re: [Sdcc-user] [PIC16] Another way to read/write EEPROM?

Hi Raphael! Accesing via generic pointers would be amazing. If you had time, I would love to see it implemeted. The __eeprom keyword can wait, hehe! Maybe I could help you with implementation of eeprom reads and writes. I could start with device/lib/pic16/libsdcc/gptr/*.c which I think that I und

[Sdcc-user] [PIC16] Another way to read/write EEPROM?

Hi! I had always used a library with the following functions to read/write eeprom memory: uint8_t eeprom_read(uint8_t address); void eeprom_write(uint8_t address, uint8_t value); uint8_t eeprom_write_and_verify(uint8_t address, uint8_t value); Reading the SDCC manual again, I started thinking th

Re: [Sdcc-user] [PIC16] __critical working?

Thanks. This improvement is great! I have had no time to test it but I'll let you know as soon as I do. Thanks again! On Sun, Feb 12, 2012 at 8:38 PM, Raphael Neider wrote: > Hi, > > Update regarding __critical: __critical is implemented in SDCC r7307 > both as function attribute and in block-

Re: [Sdcc-user] [PIC16] __critical working?

Thanks for your help. Back to the MACRO, wouldn't it be enough with saving and disabling INTCONbits.GIE? Reading 18F2550 datasheet, GIE disables all interrupts so PEIE doesn't seem necessary here. Is it different with other PICs? Am I missing something? Thanks again On Sun, Feb 12, 2012 at 5:00

Re: [Sdcc-user] [PIC16] __critical working?

Thanks, I think I'll use the MACRO. What about #pragma nooverlay? Is it a nop too? Maybe the manual should say something about it in the PIC16 port section. I'll think where to say it and write it, what do you think? Thank you very much! On Sun, Feb 12, 2012 at 1:36 PM, Raphael Neider wrote:

[Sdcc-user] [PIC16] __critical working?

Hi! I need to disable interrupts for some functions because they are called from main() and from interrupt. I was trying __critical keyword but it seems to be doing nothing. Does __critical work for PIC16 port? If it doesn't, how do you do it? Thanks a lot. ---

Re: [Sdcc-user] [PIC16] Exporting full memory range in hex

I don't need fuses in the file because fuses are determined but bootloader and you can't change them later. Fuses are out of the 32K region. That's why I added them because without padding, I couldn't get the full 32K. Adding fuses, which are out of that range, allowed dd to copy 32K. Exactly, con

Re: [Sdcc-user] [PIC16] Exporting full memory range in hex

ze >dd if=myprog.bin of=readyfordownload.bin bs=4096 > > The 'bs=N' would be the size required by your loader to fill all of > memory. 'dd' > will fill the extra bytes with zeros. > > > I'm just a lurker. > > > HTH, > *brianW

[Sdcc-user] [PIC16] Exporting full memory range in hex

Hi! I want to use a bootloader (Scene Double bootloader) for PIC16 and it requires to export the full program memory range of your application (even unused range), with no eeprom nor fuses. This is the exact text present in the bootloader manual: > Exporting a HEX File from MPLAB > Once you h

  1   2   >