I took my propeller out of my Ybox2 and installed it in the Wulfden PRC and verified that I could see it and write the bootloader to it.
However, when I put the propeller back into my Ybox2, and power it up, I don't get any lights, noise, and I can't see it with my Wulfden P1 propeller programmer.
I verified that 3.3V is being supplied everywhere it should. I even see it on the RST pin oddly enough.
I checked all my solder joints. I verified all the resistors. etc etc...
Any suggestions? My concern right now is being able to write to the chip with the p1 programmer. I'm guessing whatever is keeping me from doing that, is also keeping it from lighting up and displaying anything.
Can't see prop chip with P1 programmer
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
Okay.
Progress.
I took the Propeller and EEPROM out and installed them in my PRC. I then used the P1 programmer to write the bootloader to the RAM and EEPROM (not sure which I should have done, but I did both for 'good measure.')
I then installed the Propeller and EEPROM back in the YBOX2 and now I have video. "First boot!"
However, it is stuck at the "First boot1" screen, and the LED still doesn't light up. I still can't connect the P1 programmer to the YBOX2 and see the Propeller with the prop software.
I'm not sure what to do next.
Progress.
I took the Propeller and EEPROM out and installed them in my PRC. I then used the P1 programmer to write the bootloader to the RAM and EEPROM (not sure which I should have done, but I did both for 'good measure.')
I then installed the Propeller and EEPROM back in the YBOX2 and now I have video. "First boot!"
However, it is stuck at the "First boot1" screen, and the LED still doesn't light up. I still can't connect the P1 programmer to the YBOX2 and see the Propeller with the prop software.
I'm not sure what to do next.
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
Okay. I modified a sparkfun 3.3v usb programmer to work. Apparently the P1 doesn't work with the Ybox2.
However. After uploading the bootloader to eeprom, I am still looking at "First boot!" and I see nothing about ethernet. I've tried 3 different EEPROM chips so far, all with the same annoying "First Boot!" message.
My LED, speaker, and etherjack leds aren't illuminated. Is this a result of bad programming? Bad hardware?
Did I burn up my enc chip?
I'm at a loss. Please help!
(BTW: I did connect pin7 of the eeprom to vss to see if that would fix it. It doesn't)
However. After uploading the bootloader to eeprom, I am still looking at "First boot!" and I see nothing about ethernet. I've tried 3 different EEPROM chips so far, all with the same annoying "First Boot!" message.
My LED, speaker, and etherjack leds aren't illuminated. Is this a result of bad programming? Bad hardware?
Did I burn up my enc chip?
I'm at a loss. Please help!
(BTW: I did connect pin7 of the eeprom to vss to see if that would fix it. It doesn't)
- darco
- Posts: 118
- Joined: Wed Jun 04, 2008 7:54 pm
Re: Can't see prop chip with P1 programmer
Make sure your EEPROM is a 64kb one. That's the most likely reason for the multiple "First boot!" messages.
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
My EEPROM came from LadyAda's parts list page. I ordered it from mouser. It is a total of 512K.
I have tried an ATMLU716 (mouser sent it and I can't find a spec sheet), and 2 different 24LC512. I have also tried 2 diff prop chips.
All with the same result.
Also, would that cause the LED, speaker, and MagJack LEDs to not work? Do I have to get past the 'first boot' in order for the pop to start powering those devices?
A note from the specs on the 24LC512:
"The Microchip Technology Inc. 24AA512/24LC512/ 24FC512 (24XX512*) is a 64K x 8 (512 Kbit) Serial Electrically Erasable PROM, capable of operation across a broad voltage range (1.7V to 5.5V). It has been developed for advanced, low-power applications such as personal communications and data acquisition. This device also has a page write capability of up to 128 bytes of data. This device is capable of both random and sequential reads up to the 512K boundary. Functional address lines allow up to eight devices on the same bus, for up to 4 Mbit address space. This device is available in the standard 8-pin plastic DIP, SOIJ and DFN packages."
I have tried an ATMLU716 (mouser sent it and I can't find a spec sheet), and 2 different 24LC512. I have also tried 2 diff prop chips.
All with the same result.
Also, would that cause the LED, speaker, and MagJack LEDs to not work? Do I have to get past the 'first boot' in order for the pop to start powering those devices?
A note from the specs on the 24LC512:
"The Microchip Technology Inc. 24AA512/24LC512/ 24FC512 (24XX512*) is a 64K x 8 (512 Kbit) Serial Electrically Erasable PROM, capable of operation across a broad voltage range (1.7V to 5.5V). It has been developed for advanced, low-power applications such as personal communications and data acquisition. This device also has a page write capability of up to 128 bytes of data. This device is capable of both random and sequential reads up to the 512K boundary. Functional address lines allow up to eight devices on the same bus, for up to 4 Mbit address space. This device is available in the standard 8-pin plastic DIP, SOIJ and DFN packages."
- darco
- Posts: 118
- Joined: Wed Jun 04, 2008 7:54 pm
Re: Can't see prop chip with P1 programmer
I'm on vacation so I haven't had a lot of time to think about this, but... If you keep seeing "first boot", it is either because it can't write the first settings or it can't read them. The most likely situation is that it can't write. That narrows down your problem space.
Check the errata - make sure the write protect is tied to VSS on the EEPROM.
Sorry I can't help more right now.
Check the errata - make sure the write protect is tied to VSS on the EEPROM.
Sorry I can't help more right now.
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
I really appreciate all the help.
However, as indicated above, I have already tried tying pin7 to vss. The results are the same.
Also, will this cause the led, buzzer, and magjack to not work? I kinda expect at least the LED to do something during the 'first boot'
However, as indicated above, I have already tried tying pin7 to vss. The results are the same.
Also, will this cause the led, buzzer, and magjack to not work? I kinda expect at least the LED to do something during the 'first boot'
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
It is working!
You won't believe this, but this is how I got it working.
I deleted all references to productURL2, I modified the version string, I changed the printing of productURL to be a new variable I defined as productAuthor. I made all of these modifications in bootloader.spin, recompiled, reuploaded, and all works now.
I want to make it clear that I had re-loaded the default code from the precompiled version that darc posted (bootloader_v788.binary), re-compiled and re-loaded the version from the stock bootloader.spin, and they didn't change anything. I don't know why changing the code fixed it, but it worked. This is after uploading the unmodified code to 4 separate EEPROMs without any positive results.
I am trying to recreate the problem so I can identify exactly where it is at. This appears to be a software bug.
Although I did hear the buzzer make a noise when it wrote, the LED still isn't illuminated. The magjack LEDs are however.
EDIT: Unfortunately it isn't working well. Although it says "DHCP..." on the screen, it isn't actually sending any DHCP requests. I am tcpdumping on another port on the same switch and I don't see the DHCP broadcast datagram. I do have link, and the network activity light is flashing on the magjack. Do I have a fried ENC chip? Would it give link if it was burned? How do I troubleshoot the lack of DHCP datagrams? (I am thinking I need to add code to print debugging information inside of the .spin)
You won't believe this, but this is how I got it working.
I deleted all references to productURL2, I modified the version string, I changed the printing of productURL to be a new variable I defined as productAuthor. I made all of these modifications in bootloader.spin, recompiled, reuploaded, and all works now.
I want to make it clear that I had re-loaded the default code from the precompiled version that darc posted (bootloader_v788.binary), re-compiled and re-loaded the version from the stock bootloader.spin, and they didn't change anything. I don't know why changing the code fixed it, but it worked. This is after uploading the unmodified code to 4 separate EEPROMs without any positive results.
I am trying to recreate the problem so I can identify exactly where it is at. This appears to be a software bug.
Although I did hear the buzzer make a noise when it wrote, the LED still isn't illuminated. The magjack LEDs are however.
EDIT: Unfortunately it isn't working well. Although it says "DHCP..." on the screen, it isn't actually sending any DHCP requests. I am tcpdumping on another port on the same switch and I don't see the DHCP broadcast datagram. I do have link, and the network activity light is flashing on the magjack. Do I have a fried ENC chip? Would it give link if it was burned? How do I troubleshoot the lack of DHCP datagrams? (I am thinking I need to add code to print debugging information inside of the .spin)
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
I just modified wwwexample.spin and defined an IP, subnet, gateway, etc, and it still isn't responding to my requests.
I think something may be wrong with the chip, or a connection to it. I have no clue. The RGB LED still isn't working, even after I put this in the code:
This combined with the strange EEPROM "first boot" problem makes me think something is wrong with the hardware. I just don't know where to look. I have resoldered everything to make sure I don't have a cold solder joint. I wanna smash this thing with a hammer to resolve the problem
BTW, the wwwexample.spin defines the subnet with a 0 in it as a string. This won't compile. The following post details how it can be done:
http://ladyada.net/forums/viewtopic.php ... 136#p39136
I think something may be wrong with the chip, or a connection to it. I have no clue. The RGB LED still isn't working, even after I put this in the code:
Code: Select all
settings.setLong(settings#MISC_LED_CONF,$010B0A09)
BTW, the wwwexample.spin defines the subnet with a 0 in it as a string. This won't compile. The following post details how it can be done:
http://ladyada.net/forums/viewtopic.php ... 136#p39136
- darco
- Posts: 118
- Joined: Wed Jun 04, 2008 7:54 pm
Re: Can't see prop chip with P1 programmer
It will be next week before I can help you diagnose the problem, but don't worry we'll get it straightened out.
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
It is so easy to get overwhelmed and frustrated when troubleshooting something that 'should just work.' The challenges that the troubleshooting present are good ones and shouldn't be overlooked, but it is surely easier to just want it to work.
I want to clarify my prior post about what I did. It appears that if: the same code is running in RAM as is on the EEPROM, it won't get past 'first boot!'
I need to test a bit further, but I am pretty sure that was why I was having such a hard time.
Now, onto the other parts. The ethernet, the LED, these are things that I can't be sure that aren't hardware related. I would love to know if there is any way that a bad LED could cause the ethernet to not send/receive frames. I doubt it. Also, is the opposite true? Can a bad ENC chip cause link to work, send/recv of frames not to, and the LED to not work. Or maybe I just have a few problems. *shrug*
I hope everyone had a great t-day, and look forward to working through these problems.
I want to clarify my prior post about what I did. It appears that if: the same code is running in RAM as is on the EEPROM, it won't get past 'first boot!'
I need to test a bit further, but I am pretty sure that was why I was having such a hard time.
Now, onto the other parts. The ethernet, the LED, these are things that I can't be sure that aren't hardware related. I would love to know if there is any way that a bad LED could cause the ethernet to not send/receive frames. I doubt it. Also, is the opposite true? Can a bad ENC chip cause link to work, send/recv of frames not to, and the LED to not work. Or maybe I just have a few problems. *shrug*
I hope everyone had a great t-day, and look forward to working through these problems.
- darco
- Posts: 118
- Joined: Wed Jun 04, 2008 7:54 pm
Re: Can't see prop chip with P1 programmer
Don't worry, we'll get this straightened out. You have a way to program the EEPROM, so that is great.
I'm gonna summarize your symptoms for clarity:
Now a few questions:
I'm gonna summarize your symptoms for clarity:
- Nothing happened when you put the kit together as instructed.
- Unable to program the EEPROM from the programming header on the board. (You later had success programming with a different programmer)
- You were able to properly program the EEPROM using the propeller by removing both chips and hooking up a simple programming circuit on a breadboard.
- After putting the newly-programmed EEPROM and prop back in the ybox2 board, the video-out started working.
- Every boot was a "first boot". No sound or lights from any LED.
- You've managed to get the network chip working by changing a few unrelated things in the bootloader code. The ethernet LEDs light up, but the status LED still won't. The device is unable to obtain a DHCP address.
Now a few questions:
- What kind of router are you using? Have you tried using a different router?
- What noise is the ybox2 making, and which program is making the noise?
- Have you tried setting the IP address manually? (You can do this by setting the appropriate settings)
- Are you able to make the LED light up by removing the propeller entirely and directly testing the LED pins?
- Are you sure that the ybox2 is not sending *any* DHCP traffic?
- Attachments
-
- bootloader.binary.zip
- (14.28 KiB) Downloaded 306 times
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
"Unable to program the EEPROM from the programming header on the board. (You later had success programming with a different programmer)"
True.
"You were able to properly program the EEPROM using the propeller by removing both chips and hooking up a simple programming circuit on a breadboard."
True
"After putting the newly-programmed EEPROM and prop back in the ybox2 board, the video-out started working."
True.
"Every boot was a "first boot". No sound or lights from any LED."
True.
"You've managed to get the network chip working by changing a few unrelated things in the bootloader code. The ethernet LEDs light up, but the status LED still won't. The device is unable to obtain a DHCP address."
True.
First off, lets get some pictures. If I see something obviously wrong, that can make this whole process a lot quicker.
"What kind of router are you using? Have you tried using a different router?"
I'm using an openbsd firewall. This part isn't important since I am using tcpdump to monitor ALL ethernet frames on the local segment where I placed the ybox2. I am seeing no ethernet frames generated by the reported MAC address on the ybox2. I am also not seeing any DHCP datagrams either from the reported MAC or from any device.
"What noise is the ybox2 making, and which program is making the noise?"
The only noise I heard it make was when I got the first boot to go away, it made the successful write sound. Nothing since.
"Have you tried setting the IP address manually? (You can do this by setting the appropriate settings)"
Yes. I have. It won't respond to arp.
"Are you able to make the LED light up by removing the propeller entirely and directly testing the LED pins?"
I have not tried to do that yet. I was going to test the LED if it was determined to be the possible cause of other problems. Otherwise, I'll just put that issue aside until I get the ethernet working.
"Are you sure that the ybox2 is not sending *any* DHCP traffic?"
Absolutely positive. In my day job I look at packets all day. I am 100% confident that this device is not sending any traffic. Not even if I assign the IP address manually and request ARP from it.
"Also: try the attached bootloader program."
After writing this response, I will move onto trying this version. Is there extra debugging I should look for?
True.
"You were able to properly program the EEPROM using the propeller by removing both chips and hooking up a simple programming circuit on a breadboard."
True
"After putting the newly-programmed EEPROM and prop back in the ybox2 board, the video-out started working."
True.
"Every boot was a "first boot". No sound or lights from any LED."
True.
"You've managed to get the network chip working by changing a few unrelated things in the bootloader code. The ethernet LEDs light up, but the status LED still won't. The device is unable to obtain a DHCP address."
True.
First off, lets get some pictures. If I see something obviously wrong, that can make this whole process a lot quicker.
"What kind of router are you using? Have you tried using a different router?"
I'm using an openbsd firewall. This part isn't important since I am using tcpdump to monitor ALL ethernet frames on the local segment where I placed the ybox2. I am seeing no ethernet frames generated by the reported MAC address on the ybox2. I am also not seeing any DHCP datagrams either from the reported MAC or from any device.
"What noise is the ybox2 making, and which program is making the noise?"
The only noise I heard it make was when I got the first boot to go away, it made the successful write sound. Nothing since.
"Have you tried setting the IP address manually? (You can do this by setting the appropriate settings)"
Yes. I have. It won't respond to arp.
"Are you able to make the LED light up by removing the propeller entirely and directly testing the LED pins?"
I have not tried to do that yet. I was going to test the LED if it was determined to be the possible cause of other problems. Otherwise, I'll just put that issue aside until I get the ethernet working.
"Are you sure that the ybox2 is not sending *any* DHCP traffic?"
Absolutely positive. In my day job I look at packets all day. I am 100% confident that this device is not sending any traffic. Not even if I assign the IP address manually and request ARP from it.
"Also: try the attached bootloader program."
After writing this response, I will move onto trying this version. Is there extra debugging I should look for?
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
Okay, with your bootloader.binary provided above, DHCP is working and I was able to speak HTTP to it.
Weird thing though: No video. I can get video if I switch to pal or ntsc. However, normal boots produce no video. Is that expected?
EDIT: I just recompiled the source and re-uploaded and now it is working. This is so strange.
Weird thing though: No video. I can get video if I switch to pal or ntsc. However, normal boots produce no video. Is that expected?
EDIT: I just recompiled the source and re-uploaded and now it is working. This is so strange.
-
- Posts: 25
- Joined: Wed Oct 08, 2008 1:13 pm
Re: Can't see prop chip with P1 programmer
Okay. Another strange thing.
I just disabled DHCP and set the IP etc etc, and now when it boots it won't print the IP address (just the header and the squiggly line), and it isn't responding to ARP anymore.
Also, it isn't responding to the reset switch.
EDIT: After re-uploading your precompiled .binary it is now booting all the way again. It seems that any time I try to make a change to the eeprom that I have to modify the program as well. Perhaps settings are overwriting program space? What is strange is that simply re-uploading the same code doesn't fix it. I have to go back and forth between the precompiled version you gave me and my version. It behaves this way with 2 different EEPROMs and 2 different propeller chips.
EDITv2: Well, I retract my statement that I have to go back and forth. I can modify settings with your .binary without any problem. However, your .binary doesn't have video. I am going to re-download the source from the repo and see if something got corrupted.
I just disabled DHCP and set the IP etc etc, and now when it boots it won't print the IP address (just the header and the squiggly line), and it isn't responding to ARP anymore.
Also, it isn't responding to the reset switch.
EDIT: After re-uploading your precompiled .binary it is now booting all the way again. It seems that any time I try to make a change to the eeprom that I have to modify the program as well. Perhaps settings are overwriting program space? What is strange is that simply re-uploading the same code doesn't fix it. I have to go back and forth between the precompiled version you gave me and my version. It behaves this way with 2 different EEPROMs and 2 different propeller chips.
EDITv2: Well, I retract my statement that I have to go back and forth. I can modify settings with your .binary without any problem. However, your .binary doesn't have video. I am going to re-download the source from the repo and see if something got corrupted.
Please be positive and constructive with your questions and comments.