Loading ...
Sorry, an error occurred while loading the content.

Messages List

8303

Re: Using more than one AT45DBxxx chip Nice, thank you! Alexander

a.oryshchenko
10:27 AM
#8303
 

Messages List

8302

NXP/Freescale Merger Pretty big news: NXP, Freescale Plan Mega Merger | EE Times http://www.eetimes.com/document.asp?doc_id=1325871

spudarnia
8:31 AM
#8302
 

Messages List

8301

Re: Using more than one AT45DBxxx chip Then you have a precedent for doing things that way too. I added this definition to help you: diff --git a/nuttx/include/nuttx/spi/spi.h

spudarnia
8:20 AM
#8301
 

Messages List

8300

Re: NFS error ... Build works now, haven't tested NFS functionality yet. Thank you. -- SP

SP
7:23 AM
#8300
 

Messages List

8299

Re: Using more than one AT45DBxxx chip Ok, thank you btw: it looks that drivers for ad5410 and ads1255 have exectly what I meant :)

a.oryshchenko
5:53 AM
#8299
 

Messages List

8298

Re: Some entries are missing in Kconfig file for NSH application Thanks! Patch committed. Greg

spudarnia
4:16 AM
#8298
 

Messages List

8297

Some entries are missing in Kconfig file for NSH application Hi! In nsh_command.c it is possible to disable all commands with #defines like "CONFIG_NSH_DISABLE_...". However at least these two are not present in Kconfig

Freddie Chopin
1:24 AM
#8297
This message has attachments
  • 789 Bytes
    apps-nshlib-Kconfig-add-missing-entries-to-disable-d.patch

Messages List

8296

PIC32MZ Bring-up Woes Hi, Group, For the past couple of weeks, I have been working on a port to PIC32MZ starter kit. The PIC32MZ is a pretty interesting part: MIPS M14K supporting

spudarnia
Mar 1
#8296
 

Messages List

8295

Re: Mounting W25 memory as FAT in rcS Greg, There is existing code directly referencing /fs/sdcard which I would prefer not to change. It would be very convenient to fool it into using the flash

uavflightdirector
Feb 27
#8295
 

Messages List

8294

Re: Using more than one AT45DBxxx chip If I were not afraid to change more code then a better, simpler, cleaner solution would be to add an instance number to the SPI select method like: - void

spudarnia
Feb 27
#8294
 

Messages List

8293

Re: Using more than one AT45DBxxx chip Yes, there a are many SPI devices and many boards that use them so changing anything at the interface could cause a lot of dangerous code change. It would be

spudarnia
Feb 27
#8293
 

Messages List

8292

Re: Using more than one AT45DBxxx chip It looks that this problem not only for at45db :( others devices too... It looks that good way is to find better concept for chip select at all, but it could

a.oryshchenko
Feb 27
#8292
 

Messages List

8291

Re: Using more than one AT45DBxxx chip Yes, I would prefer to see some solution that modified the select() in function pointer in the instance of struct spi_ops_s passed to at45db_initialize(). If

spudarnia
Feb 27
#8291
 

Messages List

8290

Re: Using more than one AT45DBxxx chip Greg, thanks for quick answer, Yes, probably adding SPIDEV_FLASH2 and changing init-function to something like: FAR struct mtd_dev_s *at45db_initialize(FAR

a.oryshchenko
Feb 27
#8290
 

Messages List

8289

Re: Using more than one AT45DBxxx chip ... It looks to me like the driver at drivers/mtd/at45db.c is properly designed to handle multiple AT45DB devices. You would simply have to call this multiple

spudarnia
Feb 27
#8289
 
View First Topic Go to View Last Topic
Loading 1 - 15 of total 8,303 messages