All I can say is Kudos to you people Eychei, Geezer Kiza, Naldarn, & Tom D.! I haven't done any 'coding' since the Eighties Back in the days of TTL and 6502 CPU's I still have a 8" floopy with ODT on it... I picked up three Cube 3Ds last fall with the intent to donate to my local schools. but their issues proved too problematic for a school environment I settled on a couple of Monoprice Mini's instead.. but now there is new light in the tunnel.. leave breadcrumbs to the new thread with your patched firmware and I will be a happy old fart! I would be happier if Mozilla would quit crashing on me also,, that is why the edited post .....
@Yep_I_bjim "All I can say is Kudos to you people Eychei, Geezer Kiza, Naldarn, & Tom D.! " Thank you for your words of appreciation. Let's not forget Oderbang, After all. it was he who started this thread. Without his daring exploits to perform surgery on the beast, he would not have given me the courage to rip that little sucker apart. Thanks Oderbang! Sorry for the hijack. it just kinda grew. I haven't done any 'coding' since the Eighties Back in the days of TTL and 6502 CPU's I still have a 8" floopy with ODT on it... Ah, the reminiscing of days gone by and the optimism of the future. Remember the Motorola M6800, the Zilog Z80 (grand daddy to Intel), and CP/M before Bill stole it from him? I worked on DEC PDP-11s and got my first prebuilt computer in 1978. A Tandy Trash-80. Cost $2200, I was in manure heaven. The build it yourself IMSAI 8080? A 4Kx1 RAM chip was $46 and you needed 8 of them. It was worse than heroin... Better get off this schtick before the young-in's put us in the Old Folks Home. That 70 in my name is my age. As one old fart to another, it's never too late.
Great to hear we are on the track to proprietary filament independence! Anyone able to forward the IDA files, I would like to continue the deconstruction. I have one of the old Cube 2nd ed I would like to neuter the chips on, and it looked like the firmware listed the cube 2 in it. I also remember the early days, Commodore 64, Apple IIc, early pc with a MFM drive. Had to pay $20 for a 20 Meg hard drive for the pc.
U didnt taste the power of the mighty Sinclair ZX81 48k Spectrum? I still own it in working condition haha Beahre of the HIGH RES GRAPHIC! BWAHAHAHA
Now I'm feeling old... I even recognize a lot of those and I'm not a coder! ...unless programming a commodore vic20 counts
Dang. I'm almost feeling like the youngster around here. IDA somewhat does flowcharts. It ties subroutines together with diagrams. There are "Demos" out there you can download.
I'm an mechanical guy by trade. Very little has changed short of additive manufacturing in my arena. Things sure changed a lot for the EE folk. There was a time when management dreaded adding a circuit board... today they dread having something machined
Do any of you have expertise in taking CAD diagrams of an opensource board and reorganize it to fit CUbe3 specs? Willing to pay for the job.
A lot of people can do this. R'you thinking re-laying out the rep-rap board? Is it just a paper schematic or a data set of the current board?
I'd like to use the recently opensourced CAD files for the SAV mobo and adapt it to the Cube MOBO size and resemblance of placement of the main components so no wires would need to be cut... This way we could fully marlin-ize the Cube in one go.
I would like to reduce the size of the firmware file, and saw a large-ish section is not accessed by the firmware update. It is the web demo for the eval board they used, can I remove it to open up space? The area of interest is 1D0B0B8 thru 1D023FFF.
Yes the webdemo is still in the code. I think you can savely remove it. But hopefully you have a pickit and a backup of your files.
@Naldarn, Also, which is better, the pickit or the chipkit? PICKit3 can only interface via ICSP. Which is a 2-wire propritary Microchip interface. Chipkit is more customized to interface with ChipKit Dev boards. However, can be used on any ICSP interface. I bought the PICKit3 because I figured both are made by Microchip. Should work well together. Kind of unyielding and confusing to work with until all the nuances are figured out. When using MPLAB X the PK3 must programed to the specific PIC chip each time. Big pain. I finally got so frustrated I bought a SEGGER j-Link EDU $60+shipping from Digi-key. Has a plethora of apps that come with it. Upgrade and downloads are free. One of the apps is j-mem which can read and write specific memory without forcing a bank rewrite. It has a GDB server which means you can connect just about any debugger eg IDA to it and debug from the disassembler. It can interface on the ICSP 2-wire, JTAG 4-wire and EJTAG much more flexible. Don't get the knock-off on Ebay. As soon as you update the J-Link's Firmware it bricks. For the price and the apps that run it, It was well worth it to me. Google SEGGER. Glad I got one G70
I have a voucher for Digikey, so how about this? https://www.olimex.com/Products/PIC/Programmers/PIC-KIT3/resources/PIC-KIT3.pdf or this? https://reference.digilentinc.com/_media/chipkit_pgm:chipkit_pgm_rm.pdf
If it helps, I bought three of the darn things, two knock-offs and a genuine one. Total:$80. Guess I'm a slow learner.
This too on the binary debug level only runs in the MPLAB IDE. You can debug AVR sketches through MPIDE which is a IDE environment for the PIC chips The main thing to look for is the chip support provided by each debugger. PK3 only supports PIC chips through MPLAB IDE. It does not support PIC32 chips. PIC32 chips are supported by MPLAB X, which is slow and buggy. Digilent's PGM as a debugging tool is only supported by MPIDE. Not MPLAB IDE or MPLAB X. It can upload to PICs. However, only using the USB port. Look at SEGGER J-Link's website for chip support. Just about everything including PIC32MXs (not yet the PIC32MLs) except AVRs. So, you can debug just every embedded chip for routers, thermostats, refrigerators, cable modems, DVRs, automobiles...Just to name a few. Suuport for AVRs work-a-round is to by a Diligent ChipKit WF32 ($30 on sale right now) which is a PIC32MX695. Or a Wire fire 32 with a PICMX32795 which has CAN support. Use MPIDE to upload the a sketch to the WF32/Wire-Fire and debug with J-Link. Now you have AVR support. This was the config I used for the Cube 3. I uploaded the .ar firmware to the WF32 using the J-Link to upload and debug from IDA, running J-Link's GDB server Since you have a voucher for Digi-key, with this information, I hope this makes it no brainier for you. If not, then you have me to blame.
