Closed qkaiser closed 3 years ago
I ended up flashing the SPI flash with SOIC clips and flashrom so implementing that feature for bcm2dump is no longer on the top of my todo list, but happy to help you with this at some point :)
Hi Quentin! R/W support is for NVRAM implemented in the current master
branch, given .write
and .erase
functions. Since this isn't exactly a safe procedure, it won't work with the -s
flag.
For this to work, you'll also have to define:
.buffer
: An address that can be used as a buffer for the NVRAM data..rwcode
: An address for the read/write code. Must be aligned to 64k..printf
, and either .scanf
or .getline
and .sscanf
Understood :) This should be sufficient so I'm closing the issue.
Hi !
I'm currently working with a Siligence TCG300. The device bootloader is unlocked but the CM console is. I worked out the right profile and have read access to both NAND via NandFlashRead and SPI with SpiFlashRead functions from the bootloader, thanks to the awesome interface definition your tool provides :fire:
I dumped dynnv from nvram, and modified the serial console settings:
What I would like to do now is write the modified dynnv back to nvram using SpiFlashWrite, but I'm getting the following output from bcm2dump:
My understanding is that this feature is something that's planned for bcm2util given the references to
.write
and.erase
in some profiles (Cisco EPC3008 and TC7200). Do you have some information on the subject ? Is it something you're working on ?I haven't looked in the code yet but I'll be happy to assist you in implementing that feature if you'd like.