free-pdk / free-pdk.github.io Goto Github PK
View Code? Open in Web Editor NEWSource of the Free PDK documentation website.
Home Page: https://free-pdk.github.io
License: MIT License
Source of the Free PDK documentation website.
Home Page: https://free-pdk.github.io
License: MIT License
Sorry, the github plugin for VSCODE introduced a very confusing unintential merge when I tried to pull the latestest production branch:
I tried to roll it back but noticed that this actually reverted to an older version, so I reverted the reversion.
Looking into whats going on, I hope the current state is the right one.
Might be nice to remove the .html extensions (like most newer websites are doing).
It already seems to work in the browser, but Jekyll probably needs a configuration change to truly support this:
https://medium.com/@mittalyashu/how-to-remove-html-extension-in-jekyll-efeb48bd725f
I would like to setup netlify for PR previews like discussed in #3
To do that, netlify needs read access to this repository, but a repository admin first needs to approve that (you should've recevied an email).
I don't think we necessarily need both a development and production branch. It adds an extra step of unnecessary complexity and it also breaks the GitHub Action that refreshes the community projects once per day, which always deploys the default (= development) branch. This is why some changes from the development branch are already live at free-pdk.github.io, even though development has not yet been merged into production.
I would therefore like to delete the production branch and rename the development branch to production. Would that be okay with you?
I think it would look better, and we could fit more information, if the following section was converted to a table:
Maybe, something like this:
Padauk MCU | IO (max) | Ins. Set | ROM | RAM | Timers | PWM | COMP | ADC | Special | Datasheet |
---|---|---|---|---|---|---|---|---|---|---|
PFS154 | 14 | 14-bit | 2KW Flash | 128 bytes | T16, T2, T3 | 2x 8-bit, 3x 11-bit | Yes | - | 4x LCD | Datasheet |
PFS172 | 14 | 14-bit | 2KW Flash | 128 bytes | T16, T2, T3 | 2x 8-bit | Yes | 12x 8-bit | - | Datasheet |
PFS173 | 18 | 15-bit | 3KW Flash | 256 bytes | T16, T2, T3 | 2x 8-bit, 3x 11-bit | Yes | 13x 8-bit | 5x LCD | Datasheet |
PMS15A | 6 | 13-bit | 0.5KW OTP | 64 bytes | T16, T2 | 1x 8-bit | Yes | - | - | Datasheet |
PMS150C | 6 | 13-bit | 1KW OTP | 64 bytes | T16, T2 | 1x 8-bit | Yes | - | - | Datasheet |
PMS152 | 14 | 14-bit | 1.25KW OTP | 80 bytes | T16, T2 | 1x 8-bit, 3x 11-bit | Yes | - | - | Datasheet |
PMS154C | 14 | 14-bit | 2KW OTP | 128 bytes | T16, T2, T3 | 1x 8-bit, 3x 11-bit | Yes | - | 4x LCD | Datasheet |
PMS171B | 14 | 14-bit | 1.5KW OTP | 96 bytes | T16, T2, T3 | 1x 8-bit | Yes | 11x 8-bit | - | Datasheet |
How do we feel about adding a link to the datasheet for each IC?
If so, should it be a direct link to the .PDF hosted on Padauk's website (i.e. http://www.padauk.com.tw/upload/doc/PFS173%20datasheet_v105_EN_20200619.pdf), or would we be able to re-host them and link directly?
I could see the link going on the chip's 'detail' page under the 'Official Product Page' link, and also maybe as an icon on the primary page next to all the badges (hopefully to be converted to a table soon).
@cmfcmf - Thanks for adding the datasheet! The layout for the first column is looking a bit cramped now (taking up three lines with three different links). Maybe it would be better to break out the Datasheet and Padauk links into a separate column at this point?
So, first column header would become 'MCU' instead of 'Padauk MCU' and just contain the device name with a link to the chip detail page. And, add a column to the end that is 'Padauk Links' and has the Datasheet and @padauk product page links.
If we are looking for more space to be able to add a new column, we might be able to shrink the 'OSS Support' header down a bit as well.
@cmfcmf, this is how it looks:
hello,
in the chips directory there's a mention of G series paduak mcus with EEPROM support.
thanks
I noticed that the links to the datasheets are outdated on the website. It seems the github action to rebuild the website had been automatically deactivated due to inactivity in the repository for 60 days - two years ago!
I reactivated the scheduled run, but I am not sure that is all there is to it. Let's see if it passes.
PMS171B has easy-pdk-programmer-software support in the development branch.
We should add it to the website as well and make sure we have specs and pinouts available.
@freepdk made a comment here: 1667faf#r40725763
MCU390 is supported by easy pdk prog, I have some at hand.
Looks like MCU39X is a customized PADAUK version from this company:
http://www.zhienchina.com/products/1556.html
The chip comes with SDK for touch sensing: http://www.zhienchina.com/Upfiles/down/%E8%8A%AF%E8%BE%BE%E8%A7%A6%E6%91%B8MCU39x.rarThey also have the XDM varaints (see above) with integrated eeprom (looks like a multichip package - 2 ics in one package):
http://www.zhienchina.com/product/MCU.html
I updated https://github.com/free-pdk/fppa-pdk-documentation/blob/master/PADAUK_FPPA_14_bit_instruction_set.wikitext; how do I get the new data to show up at https://free-pdk.github.io/instruction-sets/PDK14?
I have some PMS15A and when you read them out you can see that infact they are PMS150C (same hardware ID, amount of program memory is same, ...)
PMS15A is just a marketing name of PMS150C. Inside the IC is the exact same silicon. Not a single difference.
Only the PADAUK IDE is limiting the amount of code you can use in case you choose PMS15A. If you choose PMS150C then you can use the complete code memory (1K). Also original PADAUK WRITER happily writes the PMS150C code to a "PMS15A"... and of course, everything is working.
I recently created a new repository for an (old) project, which I had not published in a dedicated repository yet.
https://github.com/cpldcpu/Addressable_7-Segment
Interestingly it is not showing up on the free-pdk page. The reason for that is that it is not showing up in the Github search results despite having the topic "padauk". I suspect that there is some kind of metric that excludes too new repositories or repositories that look like forks.
Curious indeed. I wonder what is triggering this.
Projects created with the official IDE can be recognized by looking for the *.PRJ or *.PRE extension in the repository. There may be a few false positives, so it would be advisable not to use this classifier to segregate files. Instead, a note could be added instead.
One alternative proposal could be to ask to add the topic "Free-PDK" to the repositority if the project is based on the OSS tool-chain and feature those repositories, for example by prioritizing them in the order or by adding flair or similar layout elements.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.