LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware > Linux - Embedded & Single-board computer
User Name
Password
Linux - Embedded & Single-board computer This forum is for the discussion of Linux on both embedded devices and single-board computers (such as the Raspberry Pi, BeagleBoard and PandaBoard). Discussions involving Arduino, plug computers and other micro-controller like devices are also welcome.

Notices


Reply
 
Search this Thread
Old 07-29-2014, 11:55 PM   #16
SIG_SEGV
Member
 
Registered: Jul 2012
Location: Banglore, INDIA
Distribution: Fedora-Core
Posts: 70

Rep: Reputation: 11

write a single location first:

mw.l 0x007b0000 0xffffffff 0x01

and then check your NVRAM locn:

md 0x007b0000 0x0001


Confirm that you can successfully write to your NVRAM.
 
Old 07-30-2014, 12:03 AM   #17
SIG_SEGV
Member
 
Registered: Jul 2012
Location: Banglore, INDIA
Distribution: Fedora-Core
Posts: 70

Rep: Reputation: 11
It should work easily man ...
There's no other complex ideas here.

I gone through this back. But with write I had problem at first time.

There will be read & write enable pins in NVRAM (active low), which get low when reading/writing and this signals will be sent from processor via the lines connected to pins READ/WRITE Enable.

In my case these bits were not configured (kept inactive) in that approprite chip select mapped to NVRAM. Later, I set those flags to activate READ?WRITE bits.

This was the only effort, I had to go through..., to bring up my NVRAM device.

NVRAM is same as RAM with NON-VOLATILE functionality... It doesn't require any special actions as we do it for FLASH. Only needy things are write/read enable bits and I assume the data bus always works perfect...
 
Old 07-30-2014, 07:18 AM   #18
dorsio
Member
 
Registered: Apr 2014
Posts: 48

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by SIG_SEGV View Post
write a single location first:

mw.l 0x007b0000 0xffffffff 0x01

and then check your NVRAM locn:

md 0x007b0000 0x0001


Confirm that you can successfully write to your NVRAM.
I find the solution, the NVRAM address format should be 0x487b0000, not 0x007b0000.
So the proper syntax is:

Code:
tftp 0x80000100 nvram.bin
protect off 0x487b0000 +0x50000
erase 0x487b0000 +0x50000
cp.b 0x80000100 0x487b0000 0x50000
protect on 0x487b0000 +0x50000

Last edited by dorsio; 08-02-2014 at 12:19 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Serial terminal connected to USB Serial Port on Ubuntu 12.04 809areacode Linux - General 3 07-18-2013 10:06 PM
Is a USBtty (USB serial port) treated the same as tty (normal serial port) in C? spudgunner Programming 1 11-12-2010 01:19 PM
Boot messages to serial port fanoliv Ubuntu 7 03-10-2008 09:04 PM
Parallel Port & Serial Port device identification helpmeforlinux Linux - Hardware 3 01-02-2007 01:15 AM
Using serial port card(PCMCIA) with IPAQ running Linux, can't find ttyS0 port d2army Linux - Laptop and Netbook 0 11-12-2005 08:07 PM


All times are GMT -5. The time now is 07:59 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration