-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
EEPROM ISSUES! #66
Comments
Well, the images in my blog post will certainly help you a little - I just printed a .pdf version that includes them. Hopefully this will work: |
Thank you. Was sick for a while. Just got around to checiing here. At the very least, I can actually see the pictures, which might help. Thanj you! :D |
Update: I have been able to find the UID I believe. 23f6138900000010 is what is printed. However, going to the w1 bus master, 1 for me it is w1_bus_master as opposed to w1_busmaster, 2 xxd -p eeprom does not work, instead I need to go to another location 23x0000008913f6/eeprom which returns the ton of numbers as seen in yours. Now, my new issue is, what do I do with the numbers? As far as I can tell, the UID was stareing me in the face. 23x0000008913f6 but reverse every 2 digits... Or.. Well, 00 10 20 30 would be 30 20 10 00. Anyway, next, I unpacked the zip, but I still don't see a stratasys-cli.py in the exctracted to location. I ran the setup.py and that did do SOMETHING. But still no cli.py... I'm confused.. I also should be making notes.. I had something that I just needed to get the uid for. I forgot all about it. I will continue looking for it, but thought I'd ask incase I can't find it again or I do find it, and it does actually need the cli or something. Anyway, thanks! :D @HaveBlueXST :D (Do @'s work?) |
What I have: |
Well, that guide is over 2 years old at this point, and Benjamin has made a lot of updates to the software in that time (not to mention changes in Raspbian itself since then). Make sure to read through the current readme for information on current usage, since stratasys-cli doesn't exist in the current version. |
YOU SHOULD DO A RE-RE VISIT! Heh. Thank you for your help! |
Funnily enough, I noticed the 'wiki' section in github projects, and figured that would be an excellent spot to put an updated tutorial. Unfortunately, my free time as of late is pretty much zero, so getting around to it may take quite some time. |
Might you have a more recent link to get crypto? I can't seem to get crypto... So you know... Kind of a big part of it. Other than that, I think I'm on the brink of success! Thanks man! :D |
I don't - do you get an error when trying to get the crypto package? |
Ok, trying sudo get crypto, it said I have the most recent version. And thus, I'll post what I get when I put the following command in. stratatools eeprom_decode -t prodigy -e 1000000098316f32 cartridge_dump.bin Traceback (most recent call last): |
From the last line, I'd guess something is not meant to be used with a certain version of something else... |
Note the bolded requires. That's 2 underscores on either side... |
It looks like your package of "six" is too old (1.8.0) and you need >= 1.9.0. Can you try: |
OH OH! Ok, now I've got no file/directory of cartridge_dumb.bin... BUT ATLEAST IT'S FARTHER! YAY YAY YAY. What do I do about cartridge dump? |
I tried |
|
You can also point the command directly to the EEPROM, ie:
|
Thanks so much! :D However, now I'm getting a checksum. |
Tried with another. Checksum again, but diffrent hex numbers. |
A wrong EEPROM uid might also be the culprit of such error. It should usually ends with "23". The UID you are using in a previous comment ("1000000098316f32") is probably wrong. If you want to use "23f6138900000010", then it should be: "100000008913f623". |
OH OH OH OH OH! THANK YOU SO MUCH! |
Do I have to provide everything for the create? Or can I just do |
There is no "update" command. I could probably add one but for now take the output from |
Alright, thanks! One more thing... Should I use sudo? I tried writing, and it failed. No permissions. |
Yes you need to be |
Ok, I got it! reading aver encoding gives this: |
So there's still an issue |
you need to update those fields:
|
where should I run these? |
Serial number can be random? Does it set the chip's serial number as empty on the printer? Why must one redo the date? I want to be able to edit the txt file I convert to the eeprom file directly. |
You can't re-use a serial number that the printer has already seen without editing files on the printer itself. Otherwise, people could simply dump the EEPROM on a new cartridge, use it up, refill with third party filament, then re-flash with the original information. So I just increase the serial number by a few digits when creating a new EEPROM image. |
I'm stuck at a similar point, I was able to create the image using the commands on the README page. However I don't know what I am ment todo after that. I tried haveblue's 'cp' command to write the file however I fear that all that has done is corrupted the eeprom. Anyway I am unable to decode the eeprom to test of it worked. I don't know if anyone has got any suggestions on what todo next. Note: I receive |
Sounds like it could be an electrical/connection problem at that point? I'd suggest creating a .hex file full of 0x012345678ABCDEF type of patterns and writing/reading it to the EEPROM to make sure that reads/writes are working as intended. |
NEW PROBLEM! stratatools eeprom_decode -t prodigy -e 0000007802a723 /sys/bus/w1/devices/w1_bus_master1/23-0000007802a7/eeprom > /home/pi/Desktop/cartdump.txt Then it gives the checksum error. What should it become? I've tried reversing it... Nada... Help pls... thank... (OK sorry, seriously though, help would be appreciated) |
try this:
stratatools eeprom_decode -t prodigy -e
a7027800000023 /sys/bus/w1/devices/w1_bus_master1/23-0000007802a7/eeprom >
/home/pi/Desktop/cartdump.txt
|
Still no :/
|
Any other ideas? |
@bvanheu @HaveBlueXST Hello? Any ideas? Please? |
Sorry, I re-tasked my Raspi to another project, but hopefully I can get another and try things for myself with the latest tools and OS image. |
Hello. I'll get straight to the point; I've got a Raspberry Pi, have a eeprom hooked up, but can't get the program to recognize the chip. I tried to find a solution but was unsuccessful, I've been using a guide on haveblue.org which I only have the html file for, no images or anything (School blocked it due to being a "weapon") and I've gotten a good bit done. I believe I've gotten up to the section of device tree. After that though, kind of just fell apart. Anyway, I honestly don't know how I should do this. Not sure how to ask this... Could someone help me out? I'm not sure what I should ask, and I've honestly have no idea what I'm doing... I should have done more research, but it IS near the end of the school year. Also, sorry, this is the best place I know to ask for help. not sure if I should ask for help here or else where... Thank you, sorry if I'm confusing, Please help... https://haveblue.org/?p=1988
I have a Raspberry Pi B+; Adafruit Raspberry pi B (Not B+) that I've got working; gator chips hooked up and a dimension 3D printer. Sorry, please help, thank you.
The text was updated successfully, but these errors were encountered: