JFFS2 and SQUASHFS erasing entire flash chip
I am working on an OpenWRT system for a custom board with a Flash Memory Chip. One problem is that U-Boot only works if the Flash Memory is in 3 Byte Addressing Mode while Linux needs 4 byte Addressing Mode. This switch is done in U-Boot and everything works.
The problems start when i want to reboot the board. For this i am changing the addressing mode of the Flash Memory from Linux back to 3 byte(U-Boot needs it) but then the whole system is unresponsive and what's worst is that after I power cycle the device, the entire Flash Memory is erased (0xFF everywhere). My system is using OpenWRTs SQUASHFS and JFFS2 and i see lots of messages like this:
[ 1204.490000] SQUASHFS error: Unable to read page, block 2e6c4a, size a57c
[ 1204.490000] SQUASHFS error: Unable to read fragment cache entry [2e6c4a]
Now i am trying to track down when is the whole memory erased but no luck so far. Does anyone have some idea about when this happens? is it a normal behaviour if the whole memory is "corrupted"(wrong addressing mode in my case) the whole chip gets erased? Is there anything i can do in order to stop this?
linux openwrt flash-memory squashfs
add a comment |
I am working on an OpenWRT system for a custom board with a Flash Memory Chip. One problem is that U-Boot only works if the Flash Memory is in 3 Byte Addressing Mode while Linux needs 4 byte Addressing Mode. This switch is done in U-Boot and everything works.
The problems start when i want to reboot the board. For this i am changing the addressing mode of the Flash Memory from Linux back to 3 byte(U-Boot needs it) but then the whole system is unresponsive and what's worst is that after I power cycle the device, the entire Flash Memory is erased (0xFF everywhere). My system is using OpenWRTs SQUASHFS and JFFS2 and i see lots of messages like this:
[ 1204.490000] SQUASHFS error: Unable to read page, block 2e6c4a, size a57c
[ 1204.490000] SQUASHFS error: Unable to read fragment cache entry [2e6c4a]
Now i am trying to track down when is the whole memory erased but no luck so far. Does anyone have some idea about when this happens? is it a normal behaviour if the whole memory is "corrupted"(wrong addressing mode in my case) the whole chip gets erased? Is there anything i can do in order to stop this?
linux openwrt flash-memory squashfs
add a comment |
I am working on an OpenWRT system for a custom board with a Flash Memory Chip. One problem is that U-Boot only works if the Flash Memory is in 3 Byte Addressing Mode while Linux needs 4 byte Addressing Mode. This switch is done in U-Boot and everything works.
The problems start when i want to reboot the board. For this i am changing the addressing mode of the Flash Memory from Linux back to 3 byte(U-Boot needs it) but then the whole system is unresponsive and what's worst is that after I power cycle the device, the entire Flash Memory is erased (0xFF everywhere). My system is using OpenWRTs SQUASHFS and JFFS2 and i see lots of messages like this:
[ 1204.490000] SQUASHFS error: Unable to read page, block 2e6c4a, size a57c
[ 1204.490000] SQUASHFS error: Unable to read fragment cache entry [2e6c4a]
Now i am trying to track down when is the whole memory erased but no luck so far. Does anyone have some idea about when this happens? is it a normal behaviour if the whole memory is "corrupted"(wrong addressing mode in my case) the whole chip gets erased? Is there anything i can do in order to stop this?
linux openwrt flash-memory squashfs
I am working on an OpenWRT system for a custom board with a Flash Memory Chip. One problem is that U-Boot only works if the Flash Memory is in 3 Byte Addressing Mode while Linux needs 4 byte Addressing Mode. This switch is done in U-Boot and everything works.
The problems start when i want to reboot the board. For this i am changing the addressing mode of the Flash Memory from Linux back to 3 byte(U-Boot needs it) but then the whole system is unresponsive and what's worst is that after I power cycle the device, the entire Flash Memory is erased (0xFF everywhere). My system is using OpenWRTs SQUASHFS and JFFS2 and i see lots of messages like this:
[ 1204.490000] SQUASHFS error: Unable to read page, block 2e6c4a, size a57c
[ 1204.490000] SQUASHFS error: Unable to read fragment cache entry [2e6c4a]
Now i am trying to track down when is the whole memory erased but no luck so far. Does anyone have some idea about when this happens? is it a normal behaviour if the whole memory is "corrupted"(wrong addressing mode in my case) the whole chip gets erased? Is there anything i can do in order to stop this?
linux openwrt flash-memory squashfs
linux openwrt flash-memory squashfs
asked Mar 5 at 9:41
mihaimihai
1143
1143
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f504443%2fjffs2-and-squashfs-erasing-entire-flash-chip%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f504443%2fjffs2-and-squashfs-erasing-entire-flash-chip%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown