<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[EEPROM:Read from [factory] offset 0x0,length 0x400.]]></title><description><![CDATA[<p dir="auto">This all started when I couldn't see the omega's wifi. I tried to play with the settings through the command line. After a while I decided to reset everything going into failsafe and doing <strong>firstboot</strong>. After that the omega wasn't able to boot anymore.</p>
<p dir="auto">I've read all the other topics in this community, but I couldn't find a solution to this problem.</p>
<p dir="auto">I tried multiple times to upload the firmware and it ends fine, but when it boots it crashes at <strong>EEPROM:Read from [factory] offset 0x0,length 0x400.</strong></p>
<p dir="auto">I'm using the Mini dock so there shouldn't be any power problem involved.</p>
<p dir="auto">Any thought?</p>
]]></description><link>http://community.onion.io/topic/1284/eeprom-read-from-factory-offset-0x0-length-0x400</link><generator>RSS for Node</generator><lastBuildDate>Sat, 18 Apr 2026 03:57:43 GMT</lastBuildDate><atom:link href="http://community.onion.io/topic/1284.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 13 Jan 2017 15:09:45 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 15:09:45 GMT]]></title><description><![CDATA[<p dir="auto">This all started when I couldn't see the omega's wifi. I tried to play with the settings through the command line. After a while I decided to reset everything going into failsafe and doing <strong>firstboot</strong>. After that the omega wasn't able to boot anymore.</p>
<p dir="auto">I've read all the other topics in this community, but I couldn't find a solution to this problem.</p>
<p dir="auto">I tried multiple times to upload the firmware and it ends fine, but when it boots it crashes at <strong>EEPROM:Read from [factory] offset 0x0,length 0x400.</strong></p>
<p dir="auto">I'm using the Mini dock so there shouldn't be any power problem involved.</p>
<p dir="auto">Any thought?</p>
]]></description><link>http://community.onion.io/post/8348</link><guid isPermaLink="true">http://community.onion.io/post/8348</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Fri, 13 Jan 2017 15:09:45 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 15:11:53 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> You say you're tried to upload the firmware, but you don't mention exactly how. Did you try the USB-install yet? See <a href="http://community.onion.io/topic/1154/omega-2-usb-firmware-install-after-brick-resolved">http://community.onion.io/topic/1154/omega-2-usb-firmware-install-after-brick-resolved</a> for details.</p>
]]></description><link>http://community.onion.io/post/8350</link><guid isPermaLink="true">http://community.onion.io/post/8350</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Fri, 13 Jan 2017 15:11:53 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 15:17:34 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> yes I did that with the latest firmware and the build 143 both worked but it still freezes at the EEPROM.</p>
]]></description><link>http://community.onion.io/post/8352</link><guid isPermaLink="true">http://community.onion.io/post/8352</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Fri, 13 Jan 2017 15:17:34 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 15:22:59 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> Interesting. I guess the factory-settings partition has gotten corrupted. Is it an Omega2 or Omega2+?</p>
]]></description><link>http://community.onion.io/post/8353</link><guid isPermaLink="true">http://community.onion.io/post/8353</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Fri, 13 Jan 2017 15:22:59 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 15:29:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> Omega2+</p>
]]></description><link>http://community.onion.io/post/8354</link><guid isPermaLink="true">http://community.onion.io/post/8354</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Fri, 13 Jan 2017 15:29:22 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 16:00:36 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> Mind trying to flash my firmware-image at <a href="https://dl.dropboxusercontent.com/u/11811685/lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin" rel="nofollow">https://dl.dropboxusercontent.com/u/11811685/lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin</a> via USB and seeing if it boots up any better? If it boots, then we can proceed to try and repair the factory-partition.</p>
]]></description><link>http://community.onion.io/post/8357</link><guid isPermaLink="true">http://community.onion.io/post/8357</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Fri, 13 Jan 2017 16:00:36 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 16:54:17 GMT]]></title><description><![CDATA[<p dir="auto">I flashed the firmware. When it reboots it reaches this point:</p>
<p dir="auto"><em>Please press Enter to activate this console.<br />
[   13.819313] ntfs: driver 2.1.32 [Flags: R/O MODULE].<br />
[   13.902480] ip6_tables: (C) 2000-2006 Netfilter Core Team<br />
[   13.927068] Loading modules backported from Linux version wt-2016-10-03-1-g6fcb1a6<br />
[   13.934823] Backport generated by backports.git backports-20160324-9-g0e38f5c<br />
[   14.014416] mt76_wmac 10300000.wmac: ASIC revision: 76280001<br />
[   16.063373] mt76_wmac 10300000.wmac: Firmware Version: _e2_mp<br />
[   16.069224] mt76_wmac 10300000.wmac: Build Time: 20150211175503<br />
[   16.091005] firmware init done</em></p>
<p dir="auto">and then freezes again.</p>
]]></description><link>http://community.onion.io/post/8359</link><guid isPermaLink="true">http://community.onion.io/post/8359</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Fri, 13 Jan 2017 16:54:17 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 17:03:06 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> Well, that's poop. I guess I need to strip some stuff out and compile a new image for you -- perhaps stripping out all the networking-stuff would let you get into the OS, at which point backing up the current factory-partition and writing a new one would be easier. Alas, I've got a lot of stuff going on at the moment, so I'll have to get back to you later.</p>
]]></description><link>http://community.onion.io/post/8360</link><guid isPermaLink="true">http://community.onion.io/post/8360</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Fri, 13 Jan 2017 17:03:06 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 13 Jan 2017 17:05:18 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> Yeah no problem, thanks.</p>
]]></description><link>http://community.onion.io/post/8361</link><guid isPermaLink="true">http://community.onion.io/post/8361</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Fri, 13 Jan 2017 17:05:18 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Thu, 19 Jan 2017 18:09:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> Did you manage to work on it?</p>
]]></description><link>http://community.onion.io/post/8862</link><guid isPermaLink="true">http://community.onion.io/post/8862</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Thu, 19 Jan 2017 18:09:16 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Thu, 19 Jan 2017 18:19:44 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> I forgot about it completely, but I'm just compiling an image and I should have something in ~15 minutes or so.</p>
]]></description><link>http://community.onion.io/post/8863</link><guid isPermaLink="true">http://community.onion.io/post/8863</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Thu, 19 Jan 2017 18:19:44 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Thu, 19 Jan 2017 18:45:17 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> Okay, here is a link to the image: <a href="https://dl.dropboxusercontent.com/u/11811685/omega2-eeprom/lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin" rel="nofollow">https://dl.dropboxusercontent.com/u/11811685/omega2-eeprom/lede-ramips-mt7688-omega2p-squashfs-sysupgrade.bin</a></p>
<p dir="auto">There is <strong>no WiFi, no ethernet</strong> enabled. Take a backup of your current factory-partition with <code>dd if=/dev/mtd2 of=/whereeveryouwant.mtd2</code>and copy it to a USB-stick or microSD-card <strong>before flashing anything.</strong> You can then try to flash the contents of my Omega2's factory-partition with <code>mtd -r write /factory.mtd2 factory</code> -- the file is already included inside the image. Then you can try flashing official firmware and it'll hopefully work, though your MAC-address might have changed.</p>
]]></description><link>http://community.onion.io/post/8865</link><guid isPermaLink="true">http://community.onion.io/post/8865</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Thu, 19 Jan 2017 18:45:17 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 20 Jan 2017 19:43:22 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> I'm still having issues.<br />
I flashed that image from dropbox but it freezes after:<br />
[    7.334675] hub 1-0:1.0: USB hub found<br />
[    7.338969] hub 1-0:1.0: 1 port detected<br />
[    7.347975] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver<br />
[    7.355920] ohci-platform: OHCI generic platform driver<br />
[    7.361567] ohci-platform 101c1000.ohci: Generic Platform OHCI controller<br />
[    7.368537] ohci-platform 101c1000.ohci: new USB bus registered, assigned bus number 2<br />
[    7.376660] ohci-platform 101c1000.ohci: irq 26, io mem 0x101c1000<br />
[    7.442319] hub 2-0:1.0: USB hub found<br />
[    7.446613] hub 2-0:1.0: 1 port detected<br />
[    7.464603] MTK MSDC device init.<br />
[    7.507286] mtk-sd: MediaTek MT6575 MSDC Driver<br />
[    7.517811] sdhci: Secure Digital Host Controller Interface driver<br />
[    7.524102] sdhci: Copyright(c) Pierre Ossman<br />
[    7.530271] sdhci-pltfm: SDHCI platform and OF driver helper<br />
[    7.544508] usbcore: registered new interface driver usb-storage<br />
[    7.561326] init: - preinit -</p>
<p dir="auto">I rebooted it an then it went past the 7 seconds up to 48 but I can't reproduce it.</p>
]]></description><link>http://community.onion.io/post/8948</link><guid isPermaLink="true">http://community.onion.io/post/8948</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Fri, 20 Jan 2017 19:43:22 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 20 Jan 2017 23:31:57 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> I flashed the imaged a second time and got it working, but when I loaded the latest firmware it froze again at</p>
<p dir="auto">[   17.490148] EEPROM:Read from [factory] offset 0x0,length 0x400.</p>
]]></description><link>http://community.onion.io/post/9079</link><guid isPermaLink="true">http://community.onion.io/post/9079</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Fri, 20 Jan 2017 23:31:57 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Fri, 20 Jan 2017 23:35:21 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> Are you absolutely certain your power supply is good?</p>
]]></description><link>http://community.onion.io/post/9080</link><guid isPermaLink="true">http://community.onion.io/post/9080</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Fri, 20 Jan 2017 23:35:21 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Sat, 21 Jan 2017 09:06:47 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> how much can the omega withstand with the mini board? Can I use the power supply of the raspberry pi ? (5V 2.5A)</p>
]]></description><link>http://community.onion.io/post/9122</link><guid isPermaLink="true">http://community.onion.io/post/9122</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Sat, 21 Jan 2017 09:06:47 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Sat, 21 Jan 2017 09:08:14 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2293">@Federico-Corazza</a> Yes, you can.</p>
]]></description><link>http://community.onion.io/post/9124</link><guid isPermaLink="true">http://community.onion.io/post/9124</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Sat, 21 Jan 2017 09:08:14 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Sat, 21 Jan 2017 16:02:29 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> It works!</p>
<p dir="auto">Thank you very much!<br />
I apologize if I made a bigger problem than it really was.</p>
]]></description><link>http://community.onion.io/post/9160</link><guid isPermaLink="true">http://community.onion.io/post/9160</guid><dc:creator><![CDATA[Federico Corazza]]></dc:creator><pubDate>Sat, 21 Jan 2017 16:02:29 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Sat, 21 Jan 2017 23:28:39 GMT]]></title><description><![CDATA[<p dir="auto">Working with some similar MT7688 hardware, I've also seen that an under-rated power supply can cause unexpected reboots, particularly when the wifi subsystem starts up.</p>
<p dir="auto">Overall power consumption of these systems is low, maybe a watt and a half, but there seem to be some peak loads where a supply with poorly responding regulation can trigger a crash and reboot.</p>
]]></description><link>http://community.onion.io/post/9204</link><guid isPermaLink="true">http://community.onion.io/post/9204</guid><dc:creator><![CDATA[Chris Stratton]]></dc:creator><pubDate>Sat, 21 Jan 2017 23:28:39 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Sun, 22 Jan 2017 21:46:24 GMT]]></title><description><![CDATA[<p dir="auto">Hello,</p>
<p dir="auto">I seem to have same issues you have, I cannot get wifi working. However I dont think it is power related in my case. I have tried powering from my laptop and seperately from a phone charger rated 5V/1A on the micro usb on the docking board. But the issues presists...</p>
<p dir="auto">I've got the same thing this person posted at startup: <a href="https://community.onion.io/topic/1082/help-omega2-not-working/2" rel="nofollow">https://community.onion.io/topic/1082/help-omega2-not-working/2</a> with the stack trace.</p>
<p dir="auto">I tried setting up wifi connection over the web but it just would not work and fails every time I try. Then I tried it over serial/ssh and I get this message when i tried to restart wifi with <code>/etc/init.d/network restart</code>after I verified all settings where ok in /etc/config/wireless. Then the same "EEPROM Read from" happens and the restart seems to fail?</p>
<pre><code>[  491.395130] br-wlan: port 2(ra0) entered disabled state
[  491.400506] br-wlan: port 1(eth0.1) entered disabled state
[  491.513483] device eth0.1 left promiscuous mode
[  491.518099] device eth0 left promiscuous mode
[  491.522709] br-wlan: port 1(eth0.1) entered disabled state
[  491.541241] IPv6: ADDRCONF(NETDEV_UP): eth0.1: link is not ready
[  491.560027] device ra0 left promiscuous mode
[  491.564542] br-wlan: port 2(ra0) entered disabled state
root@Omega-AEAF:/# [  495.435051] EEPROM:Read from [factory] offset 0x0,length 0x400.
[  497.901039]  ch4 bssid=90:f6:52:3f:5b:da
[  497.905039]  ch6 bssid=62:35:3b:31:49:cb
[  497.909018]  ch6 bssid=62:35:3b:31:49:cd
[  497.913024]  ch6 bssid=5c:35:3b:31:49:ca
[  497.917003]  ch9 bssid=60:e3:27:8d:86:4c
[  497.920977] =====================================================
[  497.927176] Channel 1 : Dirty = 24, False CCA = 0, Busy Time = 3497, Skip Channel = FALSE
[  497.935481] Channel 2 : Dirty = 88, False CCA = 0, Busy Time = 469, Skip Channel = FALSE
[  497.943693] Channel 3 : Dirty = 104, False CCA = 0, Busy Time = 1087, Skip Channel = FALSE
[  497.952087] Channel 4 : Dirty = 154, False CCA = 0, Busy Time = 1396, Skip Channel = FALSE
[  497.960464] Channel 5 : Dirty = 148, False CCA = 0, Busy Time = 1642, Skip Channel = FALSE
[  497.968859] Channel 6 : Dirty = 262, False CCA = 0, Busy Time = 3503, Skip Channel = FALSE
[  497.977253] Channel 7 : Dirty = 148, False CCA = 0, Busy Time = 74, Skip Channel = FALSE
[  497.985472] Channel 8 : Dirty = 136, False CCA = 0, Busy Time = 701, Skip Channel = FALSE
[  497.993783] Channel 9 : Dirty = 142, False CCA = 0, Busy Time = 1008, Skip Channel = FALSE
[  498.002178] Channel 10 : Dirty = 92, False CCA = 0, Busy Time = 807, Skip Channel = FALSE
[  498.010467] Channel 11 : Dirty = 28, False CCA = 0, Busy Time = 35, Skip Channel = FALSE
[  498.018679] =====================================================
[  498.024874] Rule 1 CCA value : Min Dirtiness (Include extension channel) ==&gt; Select Channel 1
[  498.033608] Min Dirty = 24
[  498.036350] ExChannel = 0 , 0
[  498.039356] BW        = 20
[  498.374026] device eth0.1 entered promiscuous mode
[  498.378907] device eth0 entered promiscuous mode
[  498.394614] br-wlan: port 1(eth0.1) entered forwarding state
[  498.400419] br-wlan: port 1(eth0.1) entered forwarding state
[  500.391085] br-wlan: port 1(eth0.1) entered forwarding state
[  500.793187] device ra0 entered promiscuous mode
[  500.797878] br-wlan: port 2(ra0) entered forwarding state
[  500.803451] br-wlan: port 2(ra0) entered forwarding state
[  502.801027] br-wlan: port 2(ra0) entered forwarding state
</code></pre>
<p dir="auto">Does anyone know what the cause of this problem is or how I could get my Omega2+ connected to wifi?</p>
]]></description><link>http://community.onion.io/post/9263</link><guid isPermaLink="true">http://community.onion.io/post/9263</guid><dc:creator><![CDATA[Maarten G]]></dc:creator><pubDate>Sun, 22 Jan 2017 21:46:24 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Sun, 22 Jan 2017 22:01:48 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/2631">@Maarten-G</a> Don't try to hijack threads. Your device isn't crashing, so it's not the same issue.</p>
]]></description><link>http://community.onion.io/post/9264</link><guid isPermaLink="true">http://community.onion.io/post/9264</guid><dc:creator><![CDATA[WereCatf]]></dc:creator><pubDate>Sun, 22 Jan 2017 22:01:48 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Sun, 22 Jan 2017 22:14:29 GMT]]></title><description><![CDATA[<p dir="auto">Yes that does seem like a different issue, though the thread title is a bit unfortunate, it seems the EEPROM message is routine verbose output, not indicative of any issue.</p>
<p dir="auto">But if the message is the last thing seen before a problem, or comes up in a search result, it's easy to associate it in the mind.</p>
]]></description><link>http://community.onion.io/post/9267</link><guid isPermaLink="true">http://community.onion.io/post/9267</guid><dc:creator><![CDATA[Chris Stratton]]></dc:creator><pubDate>Sun, 22 Jan 2017 22:14:29 GMT</pubDate></item><item><title><![CDATA[Reply to EEPROM:Read from [factory] offset 0x0,length 0x400. on Mon, 23 Jan 2017 17:51:43 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://community.onion.io/uid/1850">@WereCatf</a> Apologies, not here to hijack a thread. I figured the EEPROM: Read from [factory ] error is/was an issues and since I got the same thing I thought it would be more helpful to post here, instead of making a new thread. Which was stated in the guidelines to not make a new thread and rather post in another user thread if I'm courteous and in the same situation.</p>
<p dir="auto">I'd try looking around for other issues, testing the things that I can and make a new thread.</p>
]]></description><link>http://community.onion.io/post/9346</link><guid isPermaLink="true">http://community.onion.io/post/9346</guid><dc:creator><![CDATA[Maarten G]]></dc:creator><pubDate>Mon, 23 Jan 2017 17:51:43 GMT</pubDate></item></channel></rss>