So either the app is not reading to content from the USB correctly or maybe there's an issue with this version of software, hence the unsupported compressor errors? However, the URL requests being sent to the server contain data of zero value. I've taken a further look as this and running the app from the command line allows me to see a log from the app which shows it does find the USB device. Please can someone save my sanity and provide an answer (or at least other suggestions)? thanks I've tried doing it a number of times now using different USB Keys - each time, the first stage works fine and the USB updates from the car with current image - i can see all the folders when viewing the USB Key in file explorer every time, with a root directory of NaviSync and a synctool_log.txt file, and a number of other directories and files within the NaviSync folder I have first formatted the USB Key to FAT32 as recommended to do, and the only other thing I can think of is whether the name of the USB Key is important but have been unable to find any reference to this?
I've tried all suggestions in the forum and others i've found elsewhere but nothing seems to work and regardless of whether I start Tool Box before or after inserting USB Key or whether I run as administrator or not, the tool box doesn't seem to recognise the device. Any kind of help is appreciated.I'm having a problem with my Dacia Logan and Media Nav Evolution in trying to perform map updates as the "tool box" doesn't see to recognise my USB Key The only printf I am getting on serial console is calling spl_board_init, the other printfs inside board_init() and sunxi_board_init() are not getting printed. I enabled SPL_BOARD_INIT option and add following to my board.c file void spl_board_init()Īnd added printfs inside both board_init() as well as sunxi_board_init(). What I can think of is that uboot SPL is not initializing boards gpio properly(or through the same functions as used by uboot proper) before accessing mmc. In uboot proper I get correct state of 'cd pin' whereas in uboot SPL it is always 0. Which makes uboot SPL to ignore state of 'cd pin'. The only issue I am having is uboot SPL is not able to use card_detect pin (this is used for detecting whether MMC card is present or not), whereas in uboot proper it is able to detect correctly.Ĭurrently I am using a work around this by enabling BROKEN_CD option in config.
I was able to boot this board successfully, with mainline uboot, loading mainline kernel zImage and getting to bash prompt. I am working on porting an old Allwinner A20 board (Marsboard A20-SOM) to mainline uboot.
0 kommentar(er)
