Reading File content of RAM in MSC example

RE: Reading File content of RAM in MSC example

Øyvind — Tue, 17 Dec 2019 10:50:26 GMT

Hello,

I've been discussing the issue with a colleague. Can you edit the following in sdk.config:

// <e> NRF_BLOCK_DEV_RAM_CONFIG_LOG_ENABLED - Enables logging in the module.
//==========================================================
#ifndef NRF_BLOCK_DEV_RAM_CONFIG_LOG_ENABLED
#define NRF_BLOCK_DEV_RAM_CONFIG_LOG_ENABLED 1
#endif
// <o> NRF_BLOCK_DEV_RAM_CONFIG_LOG_LEVEL  - Default Severity level
 
// <0=> Off 
// <1=> Error 
// <2=> Warning 
// <3=> Info 
// <4=> Debug 

#ifndef NRF_BLOCK_DEV_RAM_CONFIG_LOG_LEVEL
#define NRF_BLOCK_DEV_RAM_CONFIG_LOG_LEVEL 4
#endif

This should give us more information in the terminal.

Our concern is that the fatfs is not properly initialized, and that is causing the issue. Are you basing your code on the USB MSC example? Be aware that FatFS will create a FAT volume on the logical drive when button 3 is pressed. Do you have these pins in use? There may be conflicts with GPIO on your custom board and the example itself.

Kind regards,
Øyvind

RE: Reading File content of RAM in MSC example

maxxware — Mon, 16 Dec 2019 15:46:23 GMT

Thanks for your response. I had tested usb msc but issue it that in my custom board external flash and sd card is not available

RE: Reading File content of RAM in MSC example

Øyvind — Mon, 16 Dec 2019 13:34:07 GMT

Hello!

[quote user=""]i have custom board on that external flash and SD card is not available.[/quote]

I do not understand what you mean, do you have both an external flash and an SD card?

[quote user=""]but when i called disk_state = disk_initialize(0); this return fail state[/quote]

Did you test with our USB MSC example on your custom board?

Kind regards,
Øyvind